Hi,
I want to pass a variable to CMakeLists.txt's in sub directories:
Top directory CMakeLists.txt:
set( VAR1 "" )
add_subdirectory (subdir1)
add_subdirectory (subdir2)
Each subdir CMakeLists.txt:
...
set( VAR1 "${VAR1} extend_var1" )
...
I use VAR1 later on in the linker.
How can I make this
Really we need to implement
set_property(TEST testname ENVIRONMENT "bah=foo;fu=bar;display=:0.0")
and have ctest honor it which really should be pretty easy just a matter of
coding it up. The property stuff is already there and gets passed to the
test in ctest. CTest just has to look for that pro
David Cole wrote:
As I wrote in my first mail, I'm failed using CTEST_ENVIRONMENT inside a
CMakeLists.txt. I have not tried this in a special ctest script
because I'm
searching for lean solution. Which means write a 'CMakeList.txt' once,
run 'cmake' once and be able to run 'm
To retrieve a variable from a subdirectory (added via
ADD_SUBDIRECTORY), you have to do something like:
GET_DIRECTORY_PROPERTY (MYVAR DIRECTORY subdirectory DEFINITION INCL_DIRS)
Have a look at cmake documentation for more info about GET_DIRECTORY_PROPERTY.
Thanks Olivier, that was what I was lo
On Wednesday 20 February 2008, pepone.onrez wrote:
> On Wed, Feb 20, 2008 at 7:42 PM, Alexander Neundorf
> <[EMAIL PROTECTED]>
>
> wrote:
> >Do you mean you have to install xmlrpc ?
>
> At least using the gentoo ebuild you need to have xmlrpc with curl or
> libwww enabled before you can emerge cmak
On Wed, Feb 20, 2008 at 7:42 PM, Alexander Neundorf <[EMAIL PROTECTED]>
wrote:
>Do you mean you have to install xmlrpc ?
At least using the gentoo ebuild you need to have xmlrpc with curl or libwww
enabled before you can emerge cmake 2.4.8 in cmake-2.4.6 this isn't
necessary.
maybe the error is o
On Wednesday 20 February 2008, pepone.onrez wrote:
> Force us to depend in xml-rpc is a bad thing tm. I think most users never
> needs this feature. But in the way that is used i'm force to install it in
> any way.
Do you mean you have to install xmlrpc ?
Alex
Force us to depend in xml-rpc is a bad thing tm. I think most users never
needs this feature. But in the way that is used i'm force to install it in
any way. In a better design i don't need to pay for features i wan to use.
I think this kind of things must be added as extra modules for not bload t
On Tue, Feb 19, 2008 at 9:49 PM, Alexander Neundorf <[EMAIL PROTECTED]>
wrote:
>Yes, crashes with 2.4.6, works with cvs.
>Can you please check with 2.4.8 ?
I updated to 2.4.8 crash still reproducible here is the output
[EMAIL PROTECTED] ~/kk/cmake-glob-bug/build $ cmake --version
cmake version 2.
It's possible to have ctest submit dashboard data files using the xml-rpc
protocol. That's why the dependency is there. Not sure how often used that
feature is.
On 2/20/08, pepone. onrez <[EMAIL PROTECTED]> wrote:
>
> Hi
>
> Why CMake-2.4.8 requires xml-rpc package?
>
> Can any body explains why
Am Mittwoch 20 Februar 2008 schrieb Alexander Neundorf:
> On Wednesday 20 February 2008, Jörg Becker wrote:
> > Hi,
>
> ...
>
> > I used make and automake. Both allowed me to set relative rpaths. I
> > really want to leave the automake hell and use cmake, but I have to use
> > 'rpath .'.
>
> Use:
>
Hi
Why CMake-2.4.8 requires xml-rpc package?
Can any body explains why this package is needed to build CMake.
I can view the reason for this depency inside CMake, but when installing
CMake from gentoo portage it require xml-rpc to be instaled with curl or
libwww enabled.
Thanks
__
On Wednesday 20 February 2008, Jörg Becker wrote:
> Hi,
...
> I used make and automake. Both allowed me to set relative rpaths. I really
> want to leave the automake hell and use cmake, but I have to use 'rpath .'.
Use:
set_target_properties(hello PROPERTIES INSTALL_RPATH . )
(I think usually th
You could detect that your desired env vars are empty in your
CMakeLists.txtand have CMake emit an error.
IF("$ENV{my_env_var}" STREQUAL "")
MESSAGE(FATAL_ERROR "error: required env var not set - please set
my_env_var in your environment before running cmake/make/make test")
ENDIF("$ENV{my_env_v
On Wednesday, 20. February 2008 16:48:39 Bill Lorensen wrote:
> You can set the CTEST_ENVIRONMENT as it does:
As I wrote in my first mail, I'm failed using CTEST_ENVIRONMENT inside a
CMakeLists.txt. I have not tried this in a special ctest script because I'm
searching for lean solution. Which me
This is what I do:
Inside the top level of your Project directory create a "Resources" folder.
Then in your top level CMakeLists.txt file add the following:
# Look in our Resources FIRST for FindXXX modules
SET (CMAKE_MODULE_PATH ${CMAKE_CURRENT_SOURCE_DIR}/Resources
${CMAKE_MODULE_PATH} )
Works
Hi,
I'm wondering if there is a possibility to set relative rpaths with cmake. For
our windows people I have to deliver everything with rpath '.', so they can
copy all shared objects into the bin directory and everything works (like on
windows) without changing any path or environment variable.
If you use ctest scripts (http://www.cmake.org/Wiki/CMake_Scripting_Of_CTest )
like this one from vtk:
http://www.vtk.org/Testing/Sites/hythloth.kitware/Linux-gcc41/20080220-0300-Nightly/Notes.html
You can set the CTEST_ENVIRONMENT as it does:
# set any extra envionment variables here
SET
Hi all,
I sometimes have to define my own Findxxx.cmake, or update the ones
coming with the package. I leave them or put them in the Modules
directory. However, when I want to update my CMake version, I guess the
files in the Modules directory are deleted or replace by the ones in the
new dis
On Tuesday, 19. February 2008 19:20:46 Philip Lowman wrote:
> What you're looking for to the best of my knowledge doesn't exist in
> CMake. I would file a feature request on the bugtracker for it. There
> probably should be a way for declaring custom environment variables and
> associating them w
Hello,
On 2/20/08, Robert Bielik <[EMAIL PROTECTED]> wrote:
> I have a structure where I include all subdirs via FILE(GLOB.. and FOREACH
> and within each subdir CMakeLists.txt I want to add a path to be used with
> INCLUDE_DIRECTORIES in the main CMakeLists.txt
>
> I tried SET(INCL_DIRS ${INCL_DI
I have a structure where I include all subdirs via FILE(GLOB.. and FOREACH
and within each subdir CMakeLists.txt I want to add a path to be used with
INCLUDE_DIRECTORIES in the main CMakeLists.txt
I tried SET(INCL_DIRS ${INCL_DIRS} ${CMAKE_CURRENT_SOURCE_DIR}/include) but the
INCL_DIRS variable i
22 matches
Mail list logo