Re: [CMake] Does find_library check that a found library does in fact link?

On 09/29/2011 07:15 AM, Clifford Yapp wrote: > On Wed, Sep 28, 2011 at 8:52 PM, Michael Hertling > mailto:mhertl...@online.de>> wrote: > > What do you do on systems which have no idea of symbolic links, e.g. > previous Windows versions? Adding more platform-specific code to the > sources of the

Re: [CMake] Does find_library check that a found library does in fact link?

On Wed, Sep 28, 2011 at 8:52 PM, Michael Hertling wrote: What do you do on systems which have no idea of symbolic links, e.g. > previous Windows versions? Adding more platform-specific code to the > sources of the FIND_LIBRARY() function? If the problem isn't solved (or readily solvable) on some

Re: [CMake] Does find_library check that a found library does in fact link?

On 09/29/2011 02:52 AM, Michael Hertling wrote: > On 09/29/2011 01:30 AM, Clifford Yapp wrote: >> On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild wrote: >> >>> >>> Only if your installation is broken ;-) If the symlink is broken, I >>> consider this to be a user-error. Period. OTOH, CMake /could/ ch

Re: [CMake] Fwd: Save stripped debugging information

When I was investigating similar problem, I found alternative approach at http://code.google.com/p/dynamorio/source/browse/trunk/CMakeLists.txt. The thing is to change linker rules, to something like this: set(CMAKE_C_CREATE_SHARED_LIBRARY # standard rule " -o "

Re: [CMake] Does find_library check that a found library does in fact link?

On 09/29/2011 01:30 AM, Clifford Yapp wrote: > On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild wrote: > >> >> Only if your installation is broken ;-) If the symlink is broken, I >> consider this to be a user-error. Period. OTOH, CMake /could/ check >> whether the library is a symlink, and if it is,

Re: [CMake] How to use add_custom_command correctly

On 09/28/2011 01:45 PM, Martin Kupke wrote: > Now it seems to be solved, the generator is called and the generated > sources / headers are then compiled and linked into a library. > > My changes are in the > > D:/project/Discovery/Generated/Driver/CMakeLists.txt > > just adding a add_custom_tar

Re: [CMake] Does find_library check that a found library does in fact link?

On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild wrote: > > Only if your installation is broken ;-) If the symlink is broken, I > consider this to be a user-error. Period. OTOH, CMake /could/ check > whether the library is a symlink, and if it is, check that it is valid. > Oh, no question the insta

Re: [CMake] overriding ${PROJECTNAME}_BINARY_DIR before call to project()

On 09/28/2011 06:36 PM, Thomas Wolf wrote: > On 28.09.2011 17:58, Jean-Christophe Fillion-Robin wrote: >> Hi Thomas, >> >> You will find below few points that should help you to address your issues: >> >> 1) CTK build system can be build with the option CTK_SUPERBUILD set to >> OFF, in that case th

Re: [CMake] overriding ${PROJECTNAME}_BINARY_DIR before call to project()

On 28.09.2011 17:58, Jean-Christophe Fillion-Robin wrote: Hi Thomas, You will find below few points that should help you to address your issues: 1) CTK build system can be build with the option CTK_SUPERBUILD set to OFF, in that case the project will be built as a "regular" cmake project. 2) Y

Re: [CMake] overriding ${PROJECTNAME}_BINARY_DIR before call to project()

Hi Thomas, You will find below few points that should help you to address your issues: 1) CTK build system can be build with the option CTK_SUPERBUILD set to OFF, in that case the project will be built as a "regular" cmake project. 2) You could also build CTK normally (default option) providing

[CMake] overriding ${PROJECTNAME}_BINARY_DIR before call to project()

Hi there, I have some serious trouble to get a makefile running, comprising of MITK, VTK, ITK, CTK, Log4Qt, DCMTK, GDCM, etc... Because most of the makefiles have some imperfections regarding being built under windows and x64 with the project environment of Visual Studio 2008, we use direct

Re: [CMake] multiple source directories - solved

thanks for the hints and your help, guys. Indeed, There was one '..\' too much in my source files path. Eric Andreas Pakulat a écrit : On 28.09.11 12:51:53, pellegrini wrote: Hi all, I have a project with the following structure: root/ CMakeLists.txt prog1/ CMakeLists.txt

Re: [CMake] How to use add_custom_command correctly

Now it seems to be solved, the generator is called and the generated sources / headers are then compiled and linked into a library. My changes are in the D:/project/Discovery/Generated/Driver/CMakeLists.txt just adding a add_custom_target( MyGeneratedSources ALL DEPENDS ${all_generated_srcs}

Re: [CMake] multiple source directories

On 28.09.11 12:51:53, pellegrini wrote: > Hi all, > > I have a project with the following structure: > > root/ >CMakeLists.txt >prog1/ >CMakeLists.txt >Src/ >file1.f90 >prog2/ >CMakeLists.txt >Src/ >file2.f90 > > where prog1, pr

Re: [CMake] How to use add_custom_command correctly

> > > On 27.09.11 18:24, Michael Wild wrote: >> On 09/27/2011 05:59 PM, Martin Kupke wrote: >>> Hi, >>> >>> in my project there is a subfolder which SHALL contain sources to >>> generate a library. The problem is that at startup of the project there >>> are no source files existing, because they wi

Re: [CMake] multiple source directories

> Hi all, > > I have a project with the following structure: > > root/ > CMakeLists.txt > prog1/ > CMakeLists.txt > Src/ > file1.f90 > prog2/ > CMakeLists.txt > Src/ > file2.f90 > > where prog1, prog2 are individual projects. > > I

Re: [CMake] multiple source directories

I have a same problem (even relative paths should not be used, as I understood from documentation) and I fixed my problem by setting a variable in the /root/CMakeLists.txt e.g. set( MY_PROJECT_PROG1 ${CMAKE_CURRENT_SOURCE_DIR}/prog1 ) set( MY_PROJECT_PROG2 ${CMAKE_CURRENT_SOURCE_DIR}/prog2 ) The

Re: [CMake] How to use add_custom_command correctly

On 27.09.11 18:24, Michael Wild wrote: On 09/27/2011 05:59 PM, Martin Kupke wrote: Hi, in my project there is a subfolder which SHALL contain sources to generate a library. The problem is that at startup of the project there are no source files existing, because they will be generated by a co

[CMake] multiple source directories

Hi all, I have a project with the following structure: root/ CMakeLists.txt prog1/ CMakeLists.txt Src/ file1.f90 prog2/ CMakeLists.txt Src/ file2.f90 where prog1, prog2 are individual projects. I would like to add file1.90 to the build

Re: [CMake] Converting QMake project to CMake

NoRulez wrote: > Hi, > > i'm trying to convert a qmake project to CMake. > How can i translate "CONFIG" to CMake or what is the CMake's way of using > the CONFIG variable? > > e.g. CONFIG += mylib > > Is this the CMake equivalent: SET(mylib TRUE) No, probably not. What does CONFIG += mylib do

Re: [CMake] (no subject)

> > Hello, > I'm having trouble getting FIND_PATH to work in a certain case. I have it > working in other Find*.cmake files, but in one of my files I cannot seem > to get it to cooperate and cmake --trace/--debug-output don't seem to > provide any useful information for debugging FIND_PATH. > The p

[CMake] (no subject)

Hello, I'm having trouble getting FIND_PATH to work in a certain case. I have it working in other Find*.cmake files, but in one of my files I cannot seem to get it to cooperate and cmake --trace/--debug-output don't seem to provide any useful information for debugging FIND_PATH. The problem is

Re: [CMake] Does find_library check that a found library does in fact link?

2011/9/28 Michael Wild : > On 09/28/2011 07:47 AM, Clifford Yapp wrote: >> >> >> On Wed, Sep 28, 2011 at 12:13 AM, Michael Wild > > wrote: >> >>     On 09/28/2011 02:44 AM, Clifford Yapp wrote: >>     > I've run into a situation where find_library is returning a symlink: >