Re: [CMake] still having rpath problems on osx

On Wed, 23 Dec 2015, Michael Jackson wrote: Hm... Okay -- so, since I all my dependencies myself as cmake external projects, I guess I want all of them set to rpath. I guess that for boost, with its own build system, I'll need to add a separate fix-up step to my cmake externals project for b

Re: [CMake] Tests with assert and Release build type

Not only is it possible ... it WILL happen if you use the Microsoft C++ compiler and try to mix and match Release and Debug compilation units. The MS compiler has some very nice memory tracking facilities built into the Debug runtime libraries, but it is accomplished via different structs for Debu

Re: [CMake] still having rpath problems on osx

> On Dec 23, 2015, at 12:02 PM, Boudewijn Rempt wrote: > > On Tue, 22 Dec 2015, clin...@elemtech.com wrote: > >> >> On Dec 21, 2015 12:26 PM, Boudewijn Rempt wrote: >>> >>> All libraries I link to are built. Some come with a cmake build system, >>> some with an automake build system, boost

Re: [CMake] still having rpath problems on osx

On Tue, 22 Dec 2015, clin...@elemtech.com wrote: On Dec 21, 2015 12:26 PM, Boudewijn Rempt wrote: All libraries I link to are built. Some come with a cmake build system, some with an automake build system, boost with something else altogether... But I wouldn't have expected the way a library

[CMake] cmake 3.4.1 bootstrap compile error

I tried to download and compile 3.4.1 on Apple 10.10.5. I did ./configure prefix=blah && make here is the error: g++ -I/Users/bloring/apps/cmake/builds/cmake-3.4.1/Bootstrap.cmk -I/Users/bloring/apps/cmake/builds/cmake-3.4.1/Source -I/Users/bloring/apps/cmake/builds/cmake-3.4.1/Boot

[CMake] PythonInterp and PythonLibs find different versions on Apple

Hi, I'm having this issue that cmake using version 3.3.0. Python detection is finding different versions of interpreter and libraries. There are two version of Python installed, system one and homebrew one. cmake finds Interpreter from homebrew while libs are from system install. Here's my C

Re: [CMake] change add_executable to add_library leads to an error

Hi Petr! Yes, it helps me a lot! I have tried to apply your approach and this is exactly what I want. Thank you! :) Cédric - Mail original - > De: "Petr Kmoch" > À: "Cedric Doucet" > Cc: cmake@cmake.org > Envoyé: Mercredi 23 Décembre 2015 14:41:55 > Objet: Re: [CMake] change add

Re: [CMake] change add_executable to add_library leads to an error

Hi Cedric. add_custom_target() does not work the way you think it does. The arguments given after the target name are commands which the custom target will execute. So what your custom target `statphys` does is execute a program named `simol-statphys`. When `simol-statphys` was the name of an exec

Re: [CMake] Tests with assert and Release build type

On 22-Dec-15 04:07, Magnus Therning wrote: Ruslan Baratov writes: On 20-Dec-15 01:31, Magnus Therning wrote: Ruslan Baratov writes: How about using RelWithDebInfo? See: http://stackoverflow.com/a/28124715/2288008 Hmm, I'm probably missing something but how does that solve the issue with som

[CMake] change add_executable to add_library leads to an error

Hello, I have the following script: = file(GLOB_RECURSE statphys "*.cpp") #add_library(simol-statphys SHARED ${statphys}) add_executable(simol-statphys ${statphys}) add_dependencies(simol-statphys simol-core) add_custom_target(statphys simol-stat

[CMake] Modify command in RUN_TESTS

Hi, Is there a way to add options to ctest invocation used in RUN_TESTS target? I'm just trying to pass -jX and -output-on-failure... Regards, J ** This e-mail and any attachments thereto may contain confidentia

Re: [CMake] Correct usage of add_library

Thank you very much! :) Managing modules is indeed the very next step for me! I will try that right now! Cédric - Mail original - > De: "Sergei Nikulov" > À: "Cedric Doucet" > Cc: cmake@cmake.org > Envoyé: Mercredi 23 Décembre 2015 13:18:33 > Objet: Re: [CMake] Correct usage of add_

Re: [CMake] Correct usage of add_library

2015-12-23 15:08 GMT+03:00 Cedric Doucet : > > Sorry, it was a mistake! > Everything works fine! > Nice to hear that. And another update to my previous answer. If your module depends on kernel library (as I understand now it should be linked to module) you'd better use target_link_libraries(mod

Re: [CMake] Correct usage of add_library

Sorry, it was a mistake! Everything works fine! Best, Cédric - Mail original - > De: "Cedric Doucet" > À: "Sergei Nikulov" > Cc: cmake@cmake.org > Envoyé: Mercredi 23 Décembre 2015 12:59:48 > Objet: Re: [CMake] Correct usage of add_library > > > Hello, > > thank you very much, it

Re: [CMake] Correct usage of add_library

Hello, thank you very much, it works fine! Do you know how to create a target so that make mykernel creates a library libkernel.so? For the moment, I create a library with the command add_library(kernel SHARED ${src}) and I build libkernel.so by typing make. I have found there exist

Re: [CMake] Correct usage of add_library

Hello, 2015-12-23 13:32 GMT+03:00 Cedric Doucet : > > Hello, > > I have a code which consist in a kernel and several independent modules > which depend on this kernel. > I would like to let users build the module they want by typing, for example, > > make module1 > > to build the first module.

[CMake] Correct usage of add_library

Hello, I have a code which consist in a kernel and several independent modules which depend on this kernel. I would like to let users build the module they want by typing, for example, make module1 to build the first module. But, as this first module depends on the kernel, I need this ker