[CMake] setting and unsetting already existing enviroment varibale at the time of testing

Hi all, It seems that there is problem existing with setting and unsetting already existing environment variable like LD_LIBRARY_PATH for a particular test. If somebody knows any improvement in that regard please let me know. Actually i want to unset and set the LD_LIBRARY_PATh varibale for my

Re: [CMake] enable_testing() disables add_executable(test ...)

2009/3/8 Bill Hoffman : > Silvio Frischknecht wrote: >> >> If I enable_testing() executables or libraries called test don't build >> anymore. >> >> here's a simple example: >> >> CMakeLists.txt: >> >> cmake_minimum_required(VERSION 2.6) >> project(FooBar) >> enable_testing() >> add_executable(test

Re: [CMake] Cross Compilang and NSIS

On Sunday 08 March 2009 18:01:41 Hendrik Sattler wrote: > nsis can run natively on linux, there is no need for any wrappers. E.g. on I know that that there is a native version cause I'm using it. I'm not stupid :) > Debian: > $ makensis -VERSION > v2.37-3 Latest release: nsis-2.44-src/SConstru

Re: [CMake] enable_testing() disables add_executable(test ...)

Silvio Frischknecht wrote: If I enable_testing() executables or libraries called test don't build anymore. here's a simple example: CMakeLists.txt: cmake_minimum_required(VERSION 2.6) project(FooBar) enable_testing() add_executable(test test.c) add_test(baz test) If this is not going to be c

Re: [CMake] Cross Compilang and NSIS

Am Sonntag 08 März 2009 17:22:48 schrieb Andreas Schneider: > I've cross compiled libssh with mingw for windows today using the openSUSE > Build Service. > > http://download.opensuse.org/repositories/home:/gladiac:/win32/win32/i586/ > > I'm currently trying to create a NSIS installer on Linux for l

[CMake] Cross Compilang and NSIS

Hi, I've cross compiled libssh with mingw for windows today using the openSUSE Build Service. http://download.opensuse.org/repositories/home:/gladiac:/win32/win32/i586/ I'm currently trying to create a NSIS installer on Linux for libssh but it gives me some bad errors. The first error was tha

[CMake] enable_testing() disables add_executable(test ...)

If I enable_testing() executables or libraries called test don't build anymore. here's a simple example: CMakeLists.txt: cmake_minimum_required(VERSION 2.6) project(FooBar) enable_testing() add_executable(test test.c) add_test(baz test) If this is not going to be changed please at least write

[CMake] Joining multiple directories into one

Hi all I'm looking into compiling OpenOffice.org with CMake. Currently it uses dmake and a custom build tool. The basic structure is that every logical component (Writer, widget toolkit etc) has its own subdirectory. These are well separated. The problem comes from the internal structure of these

Re: [CMake] Common binary dir and failed local headers dependencies

Bill Hoffman pisze: > Wojciech Migda wrote: > >> Hi again, >> >> this workaround seems to do a trick: >> >> in cmDependsC::WriteDependencies I've added a local variable to store >> path to the source file being scanned for dependencies: >> >> std::string root_dir = >> cmSystemTools::GetFilenam