Re: [CMake] Simple truth question

On 2007-04-11 19:48-0700 E. Wing wrote: Okay, here's a silly question. Why doesn't this work as I think it should? SET(IS_TRUE TRUE) IF(${IS_TRUE}) MESSAGE("IS_TRUE Is true") ELSE(${IS_TRUE}) MESSAGE("IS_TRUE Is false") ENDIF(${IS_TRUE}) Replace ${IS_TRUE} by IS_TRUE, and it

[CMake] Simple truth question

Okay, here's a silly question. Why doesn't this work as I think it should? SET(IS_TRUE TRUE) IF(${IS_TRUE}) MESSAGE("IS_TRUE Is true") ELSE(${IS_TRUE}) MESSAGE("IS_TRUE Is false") ENDIF(${IS_TRUE}) I get "IS_TRUE Is false" when I run this. The same thing for SET(IS_TRUE YES) and

Re: [CMake] Several questions/problems on FIND_* search behavior

FIND_FILE does not search in /usr/lib only FIND_LIBRARY search in the library directories. FIND_FILE only looks in PATH. You're right. I got confused by the framework stuff. That should work, please give a specific example, note that CMAKE_LIBRARY_PATH is only searched by FIND_LIBRARY and CMA

Re: [CMake] Several questions/problems on FIND_* search behavior

E. Wing wrote: Several questions/problems on FIND_* search behavior: 1) Somebody complained to me that FIND_FILE was not finding things in the paths that the documentation say they should be in. I confirmed on OS X. I don't know about other platforms. I think it follows the docs So if I d

[CMake] module variable naming conventions

hi, i've been using cmake for a while now, and am writing some of my own modules to find packages, in particular. i was using my own naming convention for return INCLUDE and LIB paths, something like FOO_INCLUDE_DIR and FOO_LIBRARY_DIR, until i read the module readme: /usr/share/cmake-2.4/

[CMake] Several questions/problems on FIND_* search behavior

Several questions/problems on FIND_* search behavior: 1) Somebody complained to me that FIND_FILE was not finding things in the paths that the documentation say they should be in. I confirmed on OS X. I don't know about other platforms. So if I do: FIND_FILE(FOO libm.dylib) I'm expecting it to f

Re: [CMake] Multiple generators on the same library

OK, I will do that. Thank you for your help calin On 4/11/07, Filipe Sousa <[EMAIL PROTECTED]> wrote: Teodor Calin Hanchevici wrote: > This is the problem, > I want to be able to generate both Nmake and visual project files > without removing any files. > what I want is to be able to run somet

Re: [CMake] Multiple generators on the same library

Teodor Calin Hanchevici wrote: > This is the problem, > I want to be able to generate both Nmake and visual project files > without removing any files. > what I want is to be able to run something like > cmake -G"Nmake makefiles" -D > cmake -G"Visual Studio 8 2005" -D > > calin You can't use diff

[CMake] Re: Cmake and Subversion

Dave Feustel wrote: Are there any interactions between CMake and Subversion to be aware of when using those two tools? If you do out-of-source builds, CMake will only look at (but not touch) files in your subversion tree. Subversion will do its usual thing (i.e. complain about unversioned and

[CMake] Cmake and Subversion

Are there any interactions between CMake and Subversion to be aware of when using those two tools? Thanks, Dave Feustel http://RepublicBroadcasting.org - Because You CAN Handle The Truth! http://iceagenow.com - Because Global Warming Is A Scam! ___ CM

Re: [CMake] Multiple generators on the same library

This is the problem, I want to be able to generate both Nmake and visual project files without removing any files. what I want is to be able to run something like cmake -G"Nmake makefiles" -D cmake -G"Visual Studio 8 2005" -D calin On 4/11/07, Filipe Sousa <[EMAIL PROTECTED]> wrote: Teodor Cal

Re: [CMake] Multiple generators on the same library

On 2007-04-11 15:35-0400 Teodor Calin Hanchevici wrote: Thanks, I tried this and it does not work It generates in the same directory where CMakeLists.txt is located. See the "I run an out-of-source build but CMake generates in-source anyway. Why?" question in the FAQ at http://www.cmake.org/Wi

Re: [CMake] Multiple generators on the same library

Teodor Calin Hanchevici wrote: > > Thanks, > I tried this and it does not work > It generates in the same directory where CMakeLists.txt is located. You have to remove all generated files by cmake in the same directory where CMakeLists.txt is located. Filipe Sousa signature.asc Description: O

Re: [CMake] Multiple generators on the same library

Thanks, I tried this and it does not work It generates in the same directory where CMakeLists.txt is located. calin On 4/11/07, Filipe Sousa <[EMAIL PROTECTED]> wrote: Yes Use different directories for each generator: mkdir nmake_gen cd nmake_gen cmake -G"NMake Makefiles" /path/to/the/project

Re: [CMake] Multiple generators on the same library

Teodor Calin Hanchevici wrote: > Hi all, > I want to generate both nmake files and visual studio project files for > the same libraries. When I try to do this I get this error: > > CMake Error: Error: generator : NMake Makefiles > Does not match the generator used previously: Visual Studio 7 .NET

[CMake] Multiple generators on the same library

Hi all, I want to generate both nmake files and visual studio project files for the same libraries. When I try to do this I get this error: CMake Error: Error: generator : NMake Makefiles Does not match the generator used previously: Visual Studio 7 .NET 2003 Either remove the CMakeCache.txt file

[CMake] validation with DOMBuilder

Hello everyone, i have got a problem with the validation with a schema. I am using the DOMBuilder, which has a DOMErrorHandler. When I try parsing a invalid document, it is only parsed up to the wrong element, value, etc without any error message / exception. How can I handle a schema error?

Re: [CMake] [CPack] Creating .deb package

Hello, Option 1 is the best one but if you are in a hurry and need to go with option 2, you may want to take a look at CheckInstall: http://asic-linux.com.mx/~izto/checkinstall/ -- Pau Garcia i Quiles http://www.elpauer.org (Due to the amount of work, I usually need 10 days to answer) Quoti

Re: [CMake] [CPack] Creating .deb package

On Wednesday 11 April 2007 15:31:44 Mathieu Malaterre wrote: > Hello there, > > I am currently looking to create .deb (debian package) for a project > using CMake. As far as I understand I have two options: > > 1. Use dh_make and follow a couple of steps so that dh_make(*) will > drive the build

Re: [CMake] [CPack] Creating .deb package

2007/4/11, Mathieu Malaterre <[EMAIL PROTECTED]>: Hello there, I am currently looking to create .deb (debian package) for a project using CMake. As far as I understand I have two options: 1. Use dh_make and follow a couple of steps so that dh_make(*) will drive the build of the package, or 2

Re: [CMake] Xcode and Header Files

Mike Jackson wrote: Well that was simple. One last idea. Is there a CMake Variable that tells what generator is being used? I would like to test for Xcode and then conditionally include the headers. Also what are the side effects of adding headers to the ADD_LIBRARY or ADD_EXECUTABLE? Does c

Re: [CMake] Xcode and Header Files

I don't know of any side effects other than including them in IDE project files... :-) You can tell what generator is being used by the CMake variable CMAKE_GENERATOR. HTH, David On 4/11/07, Mike Jackson <[EMAIL PROTECTED]> wrote: Well that was simple. One last idea. Is there a CMake Variable

Re: [CMake] Xcode and Header Files

Well that was simple. One last idea. Is there a CMake Variable that tells what generator is being used? I would like to test for Xcode and then conditionally include the headers. Also what are the side effects of adding headers to the ADD_LIBRARY or ADD_EXECUTABLE? Does cmake just skip the

Re: [CMake] Xcode and Header Files

Isn't it similar to Visual Studio on Windows where they show up in the project when you add the as source files of your ADD_EXECUTABLE or ADD_LIBRARY statements...? On 4/11/07, Mike Jackson <[EMAIL PROTECTED]> wrote: When I use the Xcode Generator to generate an Xcode project none of the Headers

[CMake] Re: a problem about cmake and kde 4 on opensuse 10.2

Hi, Bill, On 11/04/07, Bill Hoffman <[EMAIL PROTECTED]> wrote: Liang Qi wrote: > Hi, all, > [100%] Building CXX object CMakeFiles/tutorial1.dir/main.o > /usr/bin/c++ -Wnon-virtual-dtor -Wno-long-long -ansi -Wundef > -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith > -Wformat-security -f

Re: [CMake] a problem about cmake and kde 4 on opensuse 10.2

Liang Qi wrote: Hi, all, Could you give me some hints on this topic? Thanks a lot. Following is the build log: In gcc way, I used, gcc main.cpp -o tutorial1 -I/usr/include -I/usr/include/Qt -I/usr/include/QtCore -I/usr/include/KDE -L/usr/lib -lQtCore -lQtGui -lkdeui -lkdecore It's ok. In cm

[CMake] Xcode and Header Files

When I use the Xcode Generator to generate an Xcode project none of the Headers show up. Which makes sense based on how cmake works. So is there something that I can put into the CMake file that will add my headers into the Xcode Project? I vaguely remember something about this but am comin

[CMake] a problem about cmake and kde 4 on opensuse 10.2

Hi, all, I used opensuse 10.2 and installed some package from here: http://software.opensuse.org/download/KDE:/KDE4/openSUSE_10.2/ I had installed cmake, libqt4, strigi, kdelibs, kdepimlibs, kdebase and devel packages for them. And I had followed the article to create my first kde4 app, http://t

Re: [CMake] TARGET_LINK_LIBRARIES question

Thomas Christian Chust wrote: [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: [...] When I TARGET_LINK_LIBRARIES( test /path/to/libA.lib) I get the equivalent of -L /path/to -l libA.lib. I'd like to get -l /path/to/libA.lib. Is that possible? Currently this is not possible.

[CMake] [CPack] Creating .deb package

Hello there, I am currently looking to create .deb (debian package) for a project using CMake. As far as I understand I have two options: 1. Use dh_make and follow a couple of steps so that dh_make(*) will drive the build of the package, or 2. The structure of a .deb package is fairly simple (

Re: [CMake] TARGET_LINK_LIBRARIES question

[EMAIL PROTECTED] wrote: > [EMAIL PROTECTED] wrote: > >> [...] >> When I TARGET_LINK_LIBRARIES( test /path/to/libA.lib) I get the equivalent >> of -L /path/to -l libA.lib. I'd like to get -l /path/to/libA.lib. Is >> that possible? > > Currently this is not possible. You also shouldn't need it.