The template files for CheckIncludeFile are not ansi conform, this
means running with CFLAGS=-Werror -Wstrict-prototypes produces
failing tests.
The template file CheckIncludeFile.c.in and the one for cxx should
correctly read
#include ${CHECK_INCLUDE_FILE_VAR}
int main(int argc, char *argv[])
it's possible with CMake greater to 2.3.4. I used two diferent destination
directories for the static and shared libs.
assuming you're working in the 'libfoo' directory :
libfoo/sources.txt
/CMakeLists.txt
/static/CMakeLists.txt
/shared/CMakeLists/txt
*.c
cat
Hello,
After comments received from several people on the list, I modified LIST
command. This breaks the behavior from the CMake beta's, so make sure to
modify your code once Bill releases 2.4.2.
A side comment, since LIST command was not in any release yet, this
should only affect people
Hi Axel,
Axel Roebel wrote:
However, I would like to come back to my main questions
related to the cpack command. Does anybody know
1.) how to prevent cpack from creating a binary distribution
and to have it create a source distribution, only.
When including CPack, it will create
Brandon J. Van Every wrote:
How can I make a file depend on a target? I have a lexer SILEX.EXE that
I generate. I need other files to depend on the existence of SILEX.EXE,
so that I can lex and create new output. It seems like
target-depends-on-target is dealt with, and
(probably off topic)
The more and more I work with cmake, the more it feels like there are two
(or more) distinct tools rolled into one...
the front end is a piece of software that interprets CMakeLists.txt files,
and drives a back end. The back end is the stuff that actually generates
compiler
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Lloyd Hilaiel wrote:
(probably off topic)
The more and more I work with cmake, the more it feels like there are two
(or more) distinct tools rolled into one...
the front end is a piece of software that interprets CMakeLists.txt files,
and
