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 command, it
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 and add them to
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 figure it wants to know whether
this is C or C
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 labels
will be too small and linking will fail sometimes
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.
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 be a dealbreaker for
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 unknowns and I'm somewhat stuck now.
My CMakeLists.txt
