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

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

[CMake] Source path default update Problem

Hi all,I am trying to change my source path to point to where my source files are located (the first line when using cmake). Upon Configuration, the path is changed back to default and i receive an error regarding the absence of a CMakeLists.txt file (which of course is not there since this defaul

Re: [CMake] Borland generator incomplete

Darko Miletic wrote: 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 c

Re: [CMake] Source path default update Problem

shawn mckenziie wrote: Hi all, I am trying to change my source path to point to where my source files are located (the first line when using cmake). Upon Configuration, the path is changed back to default and i receive an error regarding the absence of a CMakeLists.txt file (which of course is

[CMake] Possible bug: _OUTPUT_NAME not used as target property LOCATION

Hi cmake hackers, My project requires the generation of DLLs and executables with different postfixes for different configurations. Therefore I am setting the _OUTPUT_NAME options, the LOCATION property becomes rather useless, because it points to something that may not be there any more. CMakeLi

Re: [CMake] Source path default update Problem

thanks i removed the cmakecache and rebuilt the tree.On 5/16/06, Brad King <[EMAIL PROTECTED]> wrote: shawn mckenziie wrote:> Hi all,> I am trying to change my source path to point to where my source files > are located (the first line when using cmake).> Upon Configuration, the path is changed bac

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

To clarify, I'm not proposing the existing cmake language be disbanded or thrown away. I think cmake is a compelling and complete piece of software as it is, and perhaps a majority of the (existing) users would not be interested in writing build scripts in another language. All I'm suggesting is

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

Lloyd Hilaiel wrote: All I'm suggesting is that if a library were built as part of the cmake build that drew a nice line between language parsing and makefile generation, then people like me who constantly want to hack stuff up and try stuff out would be able to do so at a level higher than cmak

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

On 5/15/06, Xavier Delannoy <[EMAIL PROTECTED]> wrote: it's possible with CMake greater to 2.3.4. I used two diferent destination directories for the static and shared libs. Thanks Xavier for this detailed (and lengthy) instructions. But they are way too complicated and cumbersome imho. Under

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

step 0. use/advocate cmake for a year step 1. read code, hack on code, get idea me -> step 2. see if folks are interested/viable idea/makes sense step 3. read code and make a concretish proposition you -> step 4. get work done. > Are you personally offering to do a goo

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

Michael Biebl wrote: 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 mai

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

Michael Biebl wrote: On 5/15/06, Xavier Delannoy <[EMAIL PROTECTED]> wrote: it's possible with CMake greater to 2.3.4. I used two diferent destination directories for the static and shared libs. Thanks Xavier for this detailed (and lengthy) instructions. But they are way too complicated and

[CMake] CMake and it's invocation from MS VC7

Hi. I used CMake to create an MS VC7 solution configuration in order to import a multi-directory project into the Visual Studio IDE, where I want to build it to take advantage of the debugger, and DLL capabilities. I was very pleased to generate all the solution and project files using CMake

Re: [CMake] Possible bug: _OUTPUT_NAME not used as target property LOCATION

Laurentiu Nicolae wrote: My project requires the generation of DLLs and executables with different postfixes for different configurations. Therefore I am setting the _OUTPUT_NAME options, the LOCATION property becomes rather useless, because it points to something that may not be there any more.

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

Lloyd Hilaiel wrote: step 0. use/advocate cmake for a year step 1. read code, hack on code, get idea me -> step 2. see if folks are interested/viable idea/makes sense step 3. read code and make a concretish proposition you -> step 4. get work done. Are

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: I think I don't understand something about CMake, though. When I build any of the 5 projects that were created (the 3 file directories, ALL_BUILD, and INSTALL), the first thing that happens, according to the build log, is that CMake is invoked. Could someone kindly tell me

Re: [CMake] CMake and it's invocation from MS VC7

You also get this behavior if you are used to using VC's "Rebuild Solution"... With CMake, you never want to use "Rebuild Solution" - always "Build Solution"... David Brad King wrote: Steve Johns wrote: I think I don't understand something about CMake, though. When I build any of the 5 p

Re: [CMake] CMake and it's invocation from MS VC7

At 03:39 PM 5/16/2006, David Cole wrote: >You also get this behavior if you are used to using VC's "Rebuild Solution"... >With CMake, you never want to use "Rebuild Solution" - always "Build >Solution"... Which is why CMake adds the ALL_BUILD target. You want to build the ALL_BUILD target to bu

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: CMake takes responsibility both for generating projects and for keeping them up to date as sources (CMakeLists.txt code) change. The rules are attached to CMakeLists.txt as custom-build rules. If you right-click on one and say "Build" it will re-run CMake. Is this right-c

Re: [CMake] CMake and it's invocation from MS VC7

I hope this formats OK for the list... I'm starting to get the feeling that I've not correctly created my CMakeLists.txt files, and that my problems are propagating from there. My goal is simply to operate in the MS VC++ IDE (.NET 2003), so that I can use intellisense, the debugger etc. Thus

Re: [CMake] CMake and it's invocation from MS VC7

You also get this behavior if you are used to using VC's "Rebuild Solution"... With CMake, you never want to use "Rebuild Solution" - always "Build Solution"... Which is why CMake adds the ALL_BUILD target. You want to build the ALL_BUILD target to build everything else. David and Willi

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: In NRC206: ADD_LIBRARY(NRC206 ADDINT.C ...) CMake considers upper-case "C" to be a C++ extension by default because is a common convention on UNIX, and Windows is case-insensitive. Try adding the files like this: ADD_LIBRARY(NRC206 addint.c ...) -Brad

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: Steve Johns wrote: CMake takes responsibility both for generating projects and for keeping them up to date as sources (CMakeLists.txt code) change. The rules are attached to CMakeLists.txt as custom-build rules. If you right-click on one and say "Build" it will re-run CMa

Re: [CMake] CMake and it's invocation from MS VC7

Is this right-click procedure available in MS VS .NET 2003, do you know? If so, I'm not clear on where to find it. Yes, it is. If you look at the Solution tab and select any target, such as ALL_BUILD, use the "+" to open the target. There is a "CMakeLists.txt" file listed. Right-clikc on th

Re: [CMake] CMake and it's invocation from MS VC7

CMake considers upper-case "C" to be a C++ extension by default because is a common convention on UNIX, and Windows is case-insensitive. Try adding the files like this: ADD_LIBRARY(NRC206 addint.c ...) Thanks for the suggestion. I tried this, but the result was still: AdditionalOption

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: Is this right-click procedure available in MS VS .NET 2003, do you know? If so, I'm not clear on where to find it. Yes, it is. If you look at the Solution tab and select any target, such as ALL_BUILD, use the "+" to open the target. There is a "CMakeLists.txt" file liste

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: CMake considers upper-case "C" to be a C++ extension by default because is a common convention on UNIX, and Windows is case-insensitive. Try adding the files like this: ADD_LIBRARY(NRC206 addint.c ...) Thanks for the suggestion. I tried this, but the result was still:

Re: [CMake] CMake and it's invocation from MS VC7

On 5/16/06, William A. Hoffman <[EMAIL PROTECTED]> wrote: At 03:39 PM 5/16/2006, David Cole wrote:>You also get this behavior if you are used to using VC's "Rebuild Solution"... With CMake, you never want to use "Rebuild Solution" - always "Build Solution"... Which is why CMake adds the ALL_BUILD t

Re: [CMake] CMake and it's invocation from MS VC7

CMake converts file names it is given to be the case they are actually found on disk (for case-preserving filesystems like Windows). Rename the files on disk to be lower case also. If that is not an option there may be something else to do but I'll have to investigate. Ah, more interesting i

Re: [CMake] CMake and it's invocation from MS VC7

Steve Johns wrote: I can rename the files, but as it happens I tried this experiement for a single file and it did no good. Is there a reason why the experiment would fail on a single file, but be expected to work if they were all renamed to lowercase? I think this may have been a bug in CMa