On Wed, Feb 25, 2009 at 8:54 AM, Brad King wrote:
>
> What works for me (CMake-CVS, Mac OS X 10.5, Makefile generator) is the
>> following:
>> - add an empty custom target "untar" with no dependencies to
>> CMakeLists.txt BEFORE any of the add_subdirectory calls
>> - in the test/CMakeLists.txt a
Hi,
I want to generate a shell script which should be executable through three
files.
first file has some macros with other functions and other code.
Second and third file haev definitions fot he macro the functions.
Can i generate a shell script from all this.
Ankit
___
scott mc wrote:
I've compiled CMake for Haiku but it's insisting on putting some
things into /usr/local which Haiku does not have and does not even
allow. Haiku uses /boot/common instead, so for most ports I've done
with autotools we simply use ./configure --prefix=/boot/common, how is
this done
I'm working on replacing a autoconf/automake build with Cmake. One
thing I'm stuck on is replacing AC_SEARCH_LIBS. For example:
AC_SEARCH_LIBS(dlopen, [dl],
[test "$ac_cv_search_dlopen" = "none required" ||
LIB_DLOPEN=$ac_cv_search_dlopen])
AC_SUBST([LIB_DLOP
On Wednesday 25 February 2009, scott mc wrote:
> I've compiled CMake for Haiku but it's insisting on putting some
> things into /usr/local which Haiku does not have and does not even
> allow. Haiku uses /boot/common instead, so for most ports I've done
> with autotools we simply use ./configure --
I've compiled CMake for Haiku but it's insisting on putting some
things into /usr/local which Haiku does not have and does not even
allow. Haiku uses /boot/common instead, so for most ports I've done
with autotools we simply use ./configure --prefix=/boot/common, how is
this done in CMake?
-scottm
There is a FindCuda.cmake here, that I have looked at:
http://www.sci.utah.edu/~abe/FindCuda.html
I am thinking of adding it to CMake, he uses custom_commands for Cuda.
-Bill
___
Powered by www.kitware.com
Visit other Kitware open-source projects at
On Wednesday 25 February 2009, Alex Flint wrote:
> Hi there,
>
> I'm trying to compile different parts of my application with different
> compilers and I'm wondering how to do this within cmake. (The reason I
> need this is that I'm using nvidia's cuda but the specifics of cuda
> don't matter.) If
On Wednesday 25 February 2009, eblo...@free.fr wrote:
> - Mail Original -
> De: "Brad King"
> À: eblo...@free.fr
> Cc: cmake@cmake.org
> Objet: Re: [CMake] Help with cmake_policy
>
> Hi Brad,
>
> First of all, thanks for your help.
>
> >> I've tried to use CMAKE_POLICY (SET CMP0011 OLD), b
On Wednesday 25 February 2009, Jesse Perla wrote:
> I am using cmake 2.6.3 on vista.
>
> I am having trouble with the target_link_libraries appearing to not picking
> up the right libraries in visual studio and nmake when I use "debug" and
> "optimized"It appears to add both sets of libraries in ma
On Wednesday 25 February 2009, Jesse Perla wrote:
> I am running cmake 2.6.3 on vista32 1. Is there any way to add a path for
> cmake to permanently look for modules/packages in?
No...
> I am writing a package,
> which I have in SVN, and I really don't want to copy it back and forth to
> the cma
I found a bug in my FindGSL.cmake module and I'm having trouble finding
an acceptable way to resolve it. Some installations of GSL (GNU
Scientific Library) do not have libgsl.so linked against libgslcblas.so
in which case our project should link with -lgsl -lgslcblas even though
we only call funct
To include VXL, I do this:
FIND_PACKAGE(VXL REQUIRED)
INCLUDE(${VXL_CMAKE_DIR}/UseVXL.cmake)
How can I make my projects work like that? Say I have a /Projects/Images
folder that has a project including a CMakeLists.txt file. Then I start a
project /Projects/NewProject and I want to use some stuff
Hi there,
I'm trying to compile different parts of my application with different
compilers and I'm wondering how to do this within cmake. (The reason I
need this is that I'm using nvidia's cuda but the specifics of cuda
don't matter.) If I was to compile manually then my basic workflow
looks like
On Fri, Feb 20, 2009 at 2:36 AM, Andrea Tagliasacchi wrote:
> Thanks Philip,
>
> that worked flawlessly!
>
> I would say that this is the most compact CMake specification to compile
> a Glut/OpenGL application then:
>
> find_package(GLUT)
> find_package(OpenGL)
> INCLUDE_DIRECTORIES(${OPENGL_INCLU
- Mail Original -
De: "Brad King"
À: eblo...@free.fr
Cc: cmake@cmake.org
Objet: Re: [CMake] Help with cmake_policy
Hi Brad,
First of all, thanks for your help.
>> I've tried to use CMAKE_POLICY (SET CMP0011 OLD), but this breaks CMake
>> 2.6.2 as it seems CMake does not ignore policie
dlib_httpclient and dlib are both static libraries.
So yes, that's what I did :-). I just thought it was worth mentioning it
because it wasn't a logical result of the command.
Grtz,
Steven
2009/2/25 Michael Wild
> Why, then, don't you simply list the libraries in the correct order in the
> ta
Why, then, don't you simply list the libraries in the correct order in
the target_link_libraries command? The add_dependencies command only
has an effect on targets, not external libraries. If indeed, they are
targets (which doesn't become clear from your code) you should do:
target_link_li
Yes, it has to do something with it...
Because at least when linking under Linux, if I added dlib BEFORE
dlib_httpclient (as is now the case), dlib_httpclient will complain about
undefined symbols.
That's where the add_dependencies would come into play in my honest opinion.
CMake should calculate
eblo...@free.fr wrote:
I'm having trouble to understand how to use the cmake_policy the easy way:
My CMakeLists.txt files are written for CMake 2.6.2
I've upgraded to CMake 2.6.3, and I got some warnings about CMP0011.
How can I tell CMake 2.6.3 to work the way CMake 2.6.2 used to work, without
I think you misunderstand add_dependencies. The command adds a
dependency of dlib_httpclient on dlib, i.e. dlib_httplclient DEPENDS
ON dlib. It has nothing to do with the order the libraries appear on
the command line when you link ${PROJECT_NAME}.
HTH
Michael
On 25. Feb, 2009, at 14:15,
Michael Wild wrote:
On 25. Feb, 2009, at 7:25, Philip Lowman wrote:
When I invoke add_custom_target() in the
parent directory it causes an error in the makefiles.
To me this appears to be a bug in the Makefile generator. I also tried
to make a "untarFoo" custom target in test/CMakeLists.txt, wh
I have:
add_dependencies(dlib_httpclient dlib)
But in my cmakelists I have:
TARGET_LINK_LIBRARIES(${PROJECT_NAME} dlib dlib_httpclient)
Conclusion: it will change itself to "bin/libdlib.a
bin/libdlib_httpclient.a"
instead I would expect "bin/libdlib_httpclient.a bin/libdlib.a" as I told it
to add
On Wed, Feb 25, 2009 at 1:38 AM, Hendrik Sattler
wrote:
debug and optimized keywords are followed by _one_ library. The help entry
defines this correctly.
Thanks and sorry I missed that in the help. cmake really is amazing, but I
also find it massive. The "Mastering Cmake" book is excellent,
Hello,
I have another problem with CPack and NSIS package generator:
I currently create a CMake component for each sub-project/component of
my software.
The sub-project CMakeLists.txt use cpack_add_component(...) to define
display name, description and especially dependencies.
Now, appA might d
Hi,
I'm having trouble to understand how to use the cmake_policy the easy way:
My CMakeLists.txt files are written for CMake 2.6.2
I've upgraded to CMake 2.6.3, and I got some warnings about CMP0011.
How can I tell CMake 2.6.3 to work the way CMake 2.6.2 used to work, without
receiving warnings
On 25. Feb, 2009, at 7:25, Philip Lowman wrote:
I'm trying to come up with a way to have a custom target defined in
the
top-level directory execute a collection of custom commands previously
defined in subdirectories throughout the code (to untar many
tarballs).
Unfortunately, the approach
27 matches
Mail list logo
