Since I did not get any response, I'll try to shorten the problem
description: I try to build a static convenience lib holding all my
.o-files and then to link statically against it and all other libs.
In my CMakeLists.txt, I have
SET(CMAKE_EXE_LINKER_FLAGS -static)
ADD_LIBRARY(baselib STATIC
Joachim Ziegler wrote:
I suppose the problem is in the link line, which says:
/usr/bin/X11/c++ -fPIC -static
CMakeFiles/startCompletionServer.dir/StartCompletionServer.o -o
startCompletionServer -rdynamic -L/KM/home-0/ziegler/tmp/build
-Wl,-Bstatic -lbaselib -Wl,-Bdynamic -lpthread
Brad King wrote:
It looks like you're using CMake 2.4. In CMake 2.6 your example builds
correctly for me.
Yes, you're right. Thank you very much.
I've used version 2.4.8 as installed on Debian 4.0.
Upgrading to 2.6 solves the problem.
Thanks and kind regards,
Joachim Ziegler
Hello list,
I've tried to put all my .o-files into some kind of convenience lib so
that not every object file is rebuilt for every target that I have. A
problem arises when I try to create a static lib and a static
binary that is linked against this lib.
I have in my CMakeLists.txt (here only
Hello list,
am I correct in the following use of the CMake cache:
Suppose that in your source code, a preprocessor macro
#if defined(USE_MEMSET)
...
#elif defined(USE_BZERO)
...
#endif
decides on whether you want to use the function memset() or bzero() to
set the first n bytes of a byte area
Hello!
Maybe this has been asked here 100 times before, but I've searched
through the archives and could not find a solution to my problem:
I have a program that I want to link statically agains tthe NSPR libs,
and, if this is possible, against the Winsock2 libs.
So far, I have in
Hendrik Sattler wrote:
Ok, I have the files
libnspr4.dll
libnspr4.lib
libnspr4_s.dll
where the last one should be the static library (_s).
No. A DLL is a dynamic link library. It may be linked statically
itself but that doesn't mean that you can link statically against it.
OK, then
Werner Smekal wrote:
reason why it works in the first case. But your .lib seems to be the
import library for the dll, so I don't think you have a static library
anyways.
OK.
Now how can I tell CMake to include the (external) file
D:\nspr-4.6\lib\libnspr4.dll
(which is not created by the
Joachim Ziegler wrote:
Now how can I tell CMake to include the (external) file
D:\nspr-4.6\lib\libnspr4.dll
I've got it:
INSTALL(FILES D:/nspr-4.6/lib/libnspr4.dll DESTINATION bin)
Thnaks,
Joachim
___
CMake mailing list
CMake@cmake.org
http
Hello list,
I wonder what the difference is between making the target
$ make rebuild_cache
and a run of
$ cmake /path/to/CMakeLists.txt
Joachim
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Dizzy wrote:
So, do you have the target file
/KM/usr/ziegler/ExGen/cmake/build/src/CMakeFiles/CMakeRelink.dir/startCompletionServer
?
In src/, I have the target
ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES})
If yes do you have write privileges in
Dizzy wrote:
In what way it is not used correctly? Do you set it from within
CMakeLists.txt? Because that doesn't work. You can set it externally with -D
Yes, in CMakeLists.txt.
to cmake command line tho (similar to how you could give --prefix to
configure of autoconf).
OK, that works.
Hello,
I have two targets that have nearly the same sources:
ADD_EXECUTABLE(startCompletionServer StartCompletionServer.cpp ${BASEFILES})
ADD_EXECUTABLE(test-adler32 test-adler32.cpp ${BASEFILES})
I wonder why every object file belonging to the BASEFILES is built
twice, once for the first
Hello list,
I am new to cmake and I have just read the FAQ
http://www.cmake.org/Wiki/CMake_FAQ#Distribution_questions
I have also studied the CPack documentation, but I am still wondering
the following:
CMake doesn't create a make dist target.
Does this simply mean that there is no target
Hello Eric,
thank you very much for your very quick response. Yes, I am willing to
write some documentation on the Wiki as soon as I have understood the
basic principles of how to make a package.
Eric Noulard wrote:
Write you CMakeLists.txt
make it work for:
1 - compiling your project
Hello Dizzy,
Dizzy wrote:
So you said you want some package made of some files, but a package means some
files that eventually will be on the system in some locations (when the
package is installed) so with cmake INSTALL() commands you specify how are
those files to be installed (if the user
16 matches
Mail list logo
