Re: [CMake] Multiple folder depths in VS projects

2007-06-28 Thread Sylvain Benner
Jon W a écrit : Is there a way to have more than one level of folders in Visual Studio projects? Try this : For your foo project SOURCE_GROUP(Source Files/Dir1 FILES source1.h source1.cpp ...) or SOURCE_GROUP(Source Files\\Dir1 FILES source1.h source1.cpp ...) -Sylvain

RE: [CMake] Progress above 100% when making chicken-2.6

2007-06-28 Thread Ken Martin
CMake can get above 100% (or other screwy situations) in a couple odd cases, such as killing an install done as root half way through, and then doing a build as non-root. Basically it uses some files for tracking progress and if they get written by root and left there (like in an aborted install)

Re: [CMake] Progress above 100% when making chicken-2.6

2007-06-28 Thread Brandon Van Every
On 6/28/07, Ken Martin [EMAIL PROTECTED] wrote: CMake can get above 100% (or other screwy situations) in a couple odd cases, such as killing an install done as root half way through, and then doing a build as non-root. Basically it uses some files for tracking progress and if they get

[CMake] custom target (kernel modules)

2007-06-28 Thread Alexandru Ciobanu
Hi! I am trying to build kernel modules with CMake. To do that I use the command below: add_custom_target ( manager.ko ${kbuild_cmd} WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/linux DEPENDS ${src} linux/Kbuild ) The problem is that nobody depends on this custom target and so

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Alan W. Irwin
On 2007-06-28 10:08-0400 Alexandru Ciobanu wrote: Hi! I am trying to build kernel modules with CMake. To do that I use the command below: add_custom_target ( manager.ko ${kbuild_cmd} WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/linux DEPENDS ${src} linux/Kbuild ) The problem is

Re: [CMake] Multiple folder depths in VS projects

2007-06-28 Thread Jon W
On 6/28/07, Sylvain Benner [EMAIL PROTECTED] wrote: Jon W a écrit : Is there a way to have more than one level of folders in Visual Studio projects? Try this : For your foo project SOURCE_GROUP(Source Files/Dir1 FILES source1.h source1.cpp ...) or SOURCE_GROUP(Source Files\\Dir1 FILES

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Alexandru Ciobanu
Thanks Alan, it works. =) Alan W. Irwin wrote: On 2007-06-28 10:08-0400 Alexandru Ciobanu wrote: Hi! I am trying to build kernel modules with CMake. To do that I use the command below: add_custom_target ( manager.ko ${kbuild_cmd} WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}/linux

[CMake] Finding Parent Directory for a Library

2007-06-28 Thread Mike Jackson
I need to get the Parent Directory for a library so I can add that directory to the LINK_DIRECTORIES(). I have this so far: FIND_LIBRARY(MXADataModel_LIBRARY MXADataModel /usr/local/lib /usr/lib ${MXA_DIR}/lib CACHE ) Which will put the path to libMXADataModel.dylib into the

Re: [CMake] Finding Parent Directory for a Library

2007-06-28 Thread David Cole
GET_FILENAME_COMPONENT(dir ${MXADataModel_LIBRARY} PATH) will put the PATH into the variable 'dir' HTH, David On 6/28/07, Mike Jackson [EMAIL PROTECTED] wrote: I need to get the Parent Directory for a library so I can add that directory to the LINK_DIRECTORIES(). I have this so far:

[CMake] Getting an RPath set in a Library

2007-06-28 Thread Mike Jackson
I have a project where I am building a shared library. How do I get cmake to add an rpath to the built library? I would like the rpath to reflect my installed location? I am on OS X 10.4.10 Intel. Thanks -- Mike Jackson imikejackson gmail * com

Re: [CMake] Getting an RPath set in a Library

2007-06-28 Thread Alan W. Irwin
On 2007-06-28 16:33-0400 Mike Jackson wrote: I have a project where I am building a shared library. How do I get cmake to add an rpath to the built library? I would like the rpath to reflect my installed location? I am on OS X 10.4.10 Intel. From the documentation of SET_TARGET_PROPERTIES I

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Peter Visser
Hi, could you post the working example? I'm doing something similar but I'm doing it wrong, the add_custom_command is always being build in my case. Thanks in advance, Peter. On 6/28/07, Alexandru Ciobanu [EMAIL PROTECTED] wrote: Thanks Alan, it works. =) Alan W. Irwin wrote: On

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Alexandru Ciobanu
Hi, Peter! Sure, I can show you how I've used it exactly. Here it is: set ( kofile ${CMAKE_CURRENT_SOURCE_DIR}/manager.ko ) add_custom_command ( OUTPUT ${kofile} COMMAND ${kbuild_cmd} WORKING_DIRECTORY ${CMAKE_CURRENT_SOURCE_DIR}

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Clark J. Wang
On 6/28/07, Alan W. Irwin [EMAIL PROTECTED] wrote: On 2007-06-28 10:08-0400 Alexandru Ciobanu wrote: Hi! I am trying to build kernel modules with CMake. To do that I use the command below: add_custom_target ( manager.ko ${kbuild_cmd} WORKING_DIRECTORY

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Alan W. Irwin
On 2007-06-29 09:04+0800 Clark J. Wang wrote: On 6/28/07, Alan W. Irwin [EMAIL PROTECTED] wrote: On 2007-06-28 10:08-0400 Alexandru Ciobanu wrote: If I use the ALL parameter in add_custom_target() it will always rebuild it, even if none of source files has changes.

Re: [CMake] custom target (kernel modules)

2007-06-28 Thread Clark J. Wang
On 6/29/07, Alan W. Irwin [EMAIL PROTECTED] wrote: On 2007-06-29 09:04+0800 Clark J. Wang wrote: On 6/28/07, Alan W. Irwin [EMAIL PROTECTED] wrote: On 2007-06-28 10:08-0400 Alexandru Ciobanu wrote: If I use the ALL parameter in add_custom_target() it will always rebuild it, even if