Dusan Zatkovsky <[EMAIL PROTECTED]> writes:
> Hi all.
>
> I have a question about library dependencies in cmake projects on linux.
>
> Let's see an example:
>
> PROJECT ( foo )
> ADD_EXECUTABLE ( foo_bin foo.cpp )
> TARGET_LINK_LIBRARIES ( foo_bin ssl )
>
> When I am building a project by "make" c
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/18/07, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>> "Brandon Van Every" <[EMAIL PROTECTED]> writes:
>> >
>> > I just got done telling all you guys how to reuse objects in
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/16/07, Juan Sanchez <[EMAIL PROTECTED]> wrote:
>> Hello,
>>
>> The ar command can be used to extract the .o files from a .a file.
>> Extracting them all into the same directory, perhaps you can use some
>> file globbing to find all the objects
"Juan Sanchez" <[EMAIL PROTECTED]> writes:
> Hello,
>
> The ar command can be used to extract the .o files from a .a file.
> Extracting them all into the same directory, perhaps you can use some
> file globbing to find all the objects and add them to another archive.
>
> Juan
I tried that. It fai
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/15/07, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>>
>> But how do I link libutil.a and libconsole.a into a combined
>> libcore.a? I tried setting
>
> FAQ. (I'm tired.)
>
> Che
Hi,
another problem. I have the following structure in my source (trimmed
down):
core/
core/console/
core/console/console.c
core/util/
core/util.c
core/other-stuff.c
Now I'm building
core/console/libconsole.a
core/util/libutil.a
But how do I link libutil.a and libconsole.a into a combined
lib
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> Am Freitag 14 September 2007 schrieb Goswin von Brederlow:
>> Something inbetween is to ask the gcc. But then you are gcc
>> specific (Good enough for me).
>
> But isn't that exactly what you want? You want to k
Jack Kelly <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow wrote:
>> 'add_executable (mini-os.elf )' at least should work. The target
>> is a normal elf binary. The x86_64.o object file just doesn't tell
>> cmake enough to know how to link it. I fi
Hendrik Sattler <[EMAIL PROTECTED]> writes:
> Am Freitag 14 September 2007 schrieb Goswin von Brederlow:
>> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
>> > On a Unix-like OS, you can execute "uname -m" to get the machine
>> >
Dizzy <[EMAIL PROTECTED]> writes:
> On Friday 14 September 2007 20:08:13 Goswin von Brederlow wrote:
>> "wim van hoydonck" <[EMAIL PROTECTED]> writes:
>> > On a Unix-like OS, you can execute "uname -m" to get the machine
>> >
"Mathieu Malaterre" <[EMAIL PROTECTED]> writes:
> How about:
>
> CMAKE_SYSTEM_PROCESSOR
What does that say on i686? i486 or i686? What I want is the
architecture, not the specific cpu we currently run on.
MfG
Goswin
___
CMake mailing list
CMak
"wim van hoydonck" <[EMAIL PROTECTED]> writes:
> On a Unix-like OS, you can execute "uname -m" to get the machine
> architecture (but this is probably not really portable to M$...):
Not even portable across systems of the same architecture nor
accurate. On IA32 (x86) you want to compile for i486
Jack Kelly <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow wrote:
>> Jack Kelly <[EMAIL PROTECTED]> writes:
>> What happens when CFLAGS is already set in the environment or when I
>> need to just extend it. I guess what I'm looking for is the Makefi
"Sanchez, Juan" <[EMAIL PROTECTED]> writes:
> Hi,
> I was aware that fPIC induces a performance penalty, but I didn't realize it
> was bad as you mention (30% degradation). My preference is not reusing the
Some people claim 30% penaltiy. This number is obviously highly
dependant on the code and
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/13/07, Goswin von Brederlow <[EMAIL PROTECTED]> wrote:
>>
>> For dynamic code (in C/C++/obj-c/fortran/anythign with C linkage) you
>> must use -fPIC or variant thereof because otherwise your jump l
Jack Kelly <[EMAIL PROTECTED]> writes:
> Goswin von Brederlow wrote:
>> Hi everyone.
>>
>> A friend of mine keeps cursing about autotools and suggests cmake
>> instead. So I looked into it for a small project. Like all newbies I
>> run into a lot of unknow
"Brandon Van Every" <[EMAIL PROTECTED]> writes:
> On 9/13/07, Juan Sanchez <[EMAIL PROTECTED]> wrote:
>> The statement in the FAQ is untrue:
>>
>> >> That means I have to build all my library objects twice, once for shared
>> >> and once for static. I don't like that!
>>
>> This statement may also
Hi everyone.
A friend of mine keeps cursing about autotools and suggests cmake
instead. So I looked into it for a small project. Like all newbies I
run into a lot of unknowns and I'm somewhat stuck now.
My CMakeLists.txt looks like below. My questions are in the comments.
---
18 matches
Mail list logo
