[CMake] Rename unspecified component - how?

2011-09-16 Thread Kishore Jonnalagadda
In my project I am using the default component for all binaries and a "dev" component for headers. But when I create packages, it creates one called "Unspecified" and another called dev. How do I rename the unspecified component to be nameless? Something like myproj.deb and myproj-dev.deb? -- Che

Re: [CMake] Getting the source file list for an executable fails

2011-09-16 Thread Michael Hertling
On 09/16/2011 03:24 AM, Campbell Barton wrote: > On Fri, Sep 16, 2011 at 11:11 AM, Michael Hertling > wrote: >> On 09/16/2011 02:59 AM, Campbell Barton wrote: >>> Hi, I would expect this would work from reading the docs but it gives >>> >>> add_executable(mytarget ${SRC}) >>> get_prop

Re: [CMake] Correct way to link with libstdc++ from non-C++ project?

2011-09-16 Thread Michael Hertling
On 09/15/2011 06:39 PM, Jed Brown wrote: > Suppose project Foo depends on a library Bar that uses C++ internally, but > was not properly linked, so foo would need to be linked with > > 1. $CC -shared -o libfoo.so *.o -lbar -lstdc++ > > or > > 2. $CXX -shared -o libfoo.so *.o -lbar > > > Note t

[CMake] Tutorial for new-style ctest scripting

2011-09-16 Thread Eric Noulard
Hi there, I want to setup a ctest + cdash submission for one of my open source project: https://savannah.nongnu.org/projects/certi/ I did open a free dashboard: http://my.cdash.org/index.php?project=CERTI I did write my script: http://cvs.savannah.gnu.org/viewvc/certi/scripts/certi-ctest.cmake?r

Re: [CMake] Dependencies when using macro as include filename

2011-09-16 Thread Michael Wild
On 09/16/2011 01:29 PM, Max Vasin wrote: > Hello, > I have a number of headers (say A.h, B.h, C.h) that define some kind > of hardware abstraction layer, which header to use is determined > by the CMakeLists.txt and specified by the macro in config.h: > > config.h: > #cmakedefine HAL_H ${HAL_H} >

[CMake] Dependencies when using macro as include filename

2011-09-16 Thread Max Vasin
Hello, I have a number of headers (say A.h, B.h, C.h) that define some kind of hardware abstraction layer, which header to use is determined by the CMakeLists.txt and specified by the macro in config.h: config.h: #cmakedefine HAL_H ${HAL_H} The config.h and the HAL_H are included by the header (s

Re: [CMake] Proper way to build static binaries

2011-09-16 Thread Simon Sasburg
For MSVC I use something like this to allow linking statically to the C/C++ runtime: IF(MSVC) SET(LINK_STATIC_RUNTIME OFF CACHE BOOL "Link statically against C/C++ runtime") IF(LINK_STATIC_RUNTIME) foreach(cfgtype ${CMAKE_CONFIGURATION_TYPES} ${CMAKE_BUILD_TYPE})

Re: [CMake] Proper way to build static binaries

2011-09-16 Thread Florian Reinhard
Hi! For GNU/MinGW gcc i do use this: # MinGW / GNU Compiler IF( ${CMAKE_COMPILER_IS_GNUCXX} ) # link libstdc++ and others statically SET (CMAKE_EXE_LINKER_FLAGS"-static-libstdc++ -static-libgcc --disable-shared --enable-static --static") ENDIF( ${CMAKE_COMPILER_IS_GNUCXX} ) Regards, Flori