On 09/28/2011 07:47 AM, Clifford Yapp wrote:
On Wed, Sep 28, 2011 at 12:13 AM, Michael Wild them...@gmail.com
mailto:them...@gmail.com wrote:
On 09/28/2011 02:44 AM, Clifford Yapp wrote:
I've run into a situation where find_library is returning a symlink:
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)
Thanks in Advance
Best Regards
NoRulez
--
Powered by www.kitware.com
Visit
2011/9/28 Michael Wild them...@gmail.com:
On 09/28/2011 07:47 AM, Clifford Yapp wrote:
On Wed, Sep 28, 2011 at 12:13 AM, Michael Wild them...@gmail.com
mailto:them...@gmail.com wrote:
On 09/28/2011 02:44 AM, Clifford Yapp wrote:
I've run into a situation where find_library is
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
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
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 for a
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
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
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 )
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
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
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, prog2 are
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}
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
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
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
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)
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 the project
On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild them...@gmail.com 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
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_target(
On 09/29/2011 01:30 AM, Clifford Yapp wrote:
On Wed, Sep 28, 2011 at 2:47 AM, Michael Wild them...@gmail.com 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
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
CMAKE_C_COMPILER
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 them...@gmail.com wrote:
Only if your installation is broken ;-) If the symlink is broken, I
consider this to be a user-error. Period. OTOH, CMake
On Wed, Sep 28, 2011 at 8:52 PM, Michael Hertling mhertl...@online.dewrote:
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
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, master has been updated
via 8a3bca50fa55b82f134c8a763bc837f0d5a17afa (commit)
from
25 matches
Mail list logo