Re: [CMake] cmake ruby bindings (or perl, or python, or ...)

Filipe Sousa wrote: I remember someone suggesting Lua as a second language http://public.kitware.com/pipermail/cmake-promote/2005-December/39.html Just to add more baking soda to that fire, one thing that the CMake language has that others don't, is an anal retentive IF(CONDITION) .

Re: [CMake] cmake ruby bindings (or perl, or python, or ...)

-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, >

Re: [CMake] cmake ruby bindings (or perl, or python, or ...)

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 drives a "back end". The back end is the stuff that a

[CMake] cmake ruby bindings (or perl, or python, or ...)

(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 compi

Re: [CMake] file depending on a target

William A. Hoffman wrote: At 05:38 PM 5/15/2006, Brandon J. Van Every wrote: So I was right, ADD_FILE_DEPENDENCIES does *not* play properly with DEPENDS in ADD_CUSTOM_COMMAND. Bug or feature? All ADD_FILE_DEPENDENCIES does is set OBJECT_DEPENDS on the source. So, it w

Re: [CMake] file depending on a target

At 05:38 PM 5/15/2006, Brandon J. Van Every wrote: >Brad King wrote: >>Brandon J. Van Every wrote: >>> >>>It seems that "DEPENDS silex" will not refer to the SILEX.EXE target. >>>Rather, it thinks it's an ordinary file level dependency. >> >>That's okay. The make process that evaluates the file-

Re: [CMake] file depending on a target

Brad King wrote: Brandon J. Van Every wrote: It seems that "DEPENDS silex" will not refer to the SILEX.EXE target. Rather, it thinks it's an ordinary file level dependency. That's okay. The make process that evaluates the file-level dependency will not be executed until it is known that t

Re: [CMake] file depending on a target

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 file-depends-on-file,

Re: [CMake] cpack problems.

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 CPack

Re: [CMake] cpack problems.

On Wednesday 10 May 2006 20:33, you wrote: > Axel Roebel wrote: > > I just tried the cpack program. It failed when executing > > a post_install_script which is configured to access the installed > > libraries and to rename them. Unfortunately this seems to be required if > > one wants to install a

[CMake] LIST command behavior changes

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 on

[CMake] Borland generator incomplete

Hi there, I was using cmake extensively since 2004 mostly with Borland compiler. In 2005 I reported a bug #2424 regarding management of resource files with borland compiler. I see that in 2.4.1 problem still persists and it is a serious limitation because I have to make scripts more complex than

Re: [CMake] creating a shared and static library of the same name

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 sources.t

Re: [CMake] creating a shared and static library of the same name

At 08:52 AM 5/15/2006, Michael Biebl wrote: >On 5/15/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: >>At 06:43 AM 5/15/2006, Michael Biebl wrote: >>>Hi everybody, >>> >>>is it possible to create a shared and static library with the same name? >>>I tried the folllowing: >>> >>>ADD_LIBRARY(foo SHA

Re: [CMake] creating a shared and static library of the same name

On 5/15/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: At 06:43 AM 5/15/2006, Michael Biebl wrote: >Hi everybody, > >is it possible to create a shared and static library with the same name? >I tried the folllowing: > >ADD_LIBRARY(foo SHARED foo.c) > >ADD_LIBRARY(foo_static STATIC foo.c) >SET_T

Re: [CMake] creating a shared and static library of the same name

At 06:43 AM 5/15/2006, Michael Biebl wrote: >Hi everybody, > >is it possible to create a shared and static library with the same name? >I tried the folllowing: > >ADD_LIBRARY(foo SHARED foo.c) > >ADD_LIBRARY(foo_static STATIC foo.c) >SET_TARGET_PROPERTIES(foo_static PROPERTIES OUTPUT_NAME foo) > >B

Re: [CMake] CMake 2.5 GENERATED true bug

At 03:03 AM 5/13/2006, Brandon J. Van Every wrote: >No I don't. You didn't tell me to RTFM and use the AddFileDependencies >module.It seems to work, knock on wood. That just does an OBJECT_DEPENDS. It will add a depend onto an object file. It does not add a depend onto a target or custom c

Re: [CMake] creating a shared and static library of the same name

Sorry, I didn't read your mail (assumed the title was enough!) - Don't you want the BUILD_SHARED_LIBS option really? I think the last time someone asked this the answer was to use different names for the internal build and add a post build rule to rename one. JB Michael Biebl wrote: Hi ever

Re: [CMake] creating a shared and static library of the same name

I think the last time someone asked this the answer was to use different names for the internal build and add a post build rule to rename one. JB Michael Biebl wrote: Hi everybody, is it possible to create a shared and static library with the same name? I tried the folllowing: ADD_LIBRARY(fo

[CMake] creating a shared and static library of the same name

Hi everybody, is it possible to create a shared and static library with the same name? I tried the folllowing: ADD_LIBRARY(foo SHARED foo.c) ADD_LIBRARY(foo_static STATIC foo.c) SET_TARGET_PROPERTIES(foo_static PROPERTIES OUTPUT_NAME foo) But if I then add ADD_EXECUTABLE(bar bar.c) TARGET_LIN

[CMake] test files generated by CheckIncludeFile are not ansi conform

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