[CMake] CMake and VS Community Edition

Just playing around with Visual Studio Community Edition. I had VS 2013 Express installed and I found it best to uninstall it as the same functionality (and more) is in the community edition. The reason that I uninstalled it is that when CMake builds the solution file (if both are installed) the

Re: [CMake] CMake can't find Boost versions > 1.55

Seconded! On Wed, Nov 19, 2014 at 5:16 PM, Stephen Kelly wrote: > Robert Ramey wrote: > >> The module FindBoost is quite elaborate. Unfortunately it seems to depend >> upon searching for specific version numbers found in a list. This list >> only >> goes up to 1.55 so it can't find later versio

Re: [CMake] read imageJ ROI to matlab

On Thu, Nov 20, 2014 at 05:45:55AM +0800, WangPing wrote: > sorry list, I am not sure if I could ask a different question: does anyone > know how to read an ROI from ImageJ to matlab? Or how to save the ImageJ ROI > to a file (such as nifti format)? You might want to ask this question on the Im

Re: [CMake] CMake can't find Boost versions > 1.55

Robert Ramey wrote: > The module FindBoost is quite elaborate. Unfortunately it seems to depend > upon searching for specific version numbers found in a list. This list > only > goes up to 1.55 so it can't find later versions of Boost. Better would be > to eliminate the list so module doesn't "

[CMake] Interaction between source COMPILE_FLAGS and directory COMPILE_OPTIONS

The documentation for the source property COMPILE_FLAGS describes it as, "Additional flags to be added when compiling this source file." However, when using the Visual Studio 2013 generator (at least), it appears to replace (rather than complement) the options added via the directory property

[CMake] read imageJ ROI to matlab

sorry list, I am not sure if I could ask a different question: does anyone know how to read an ROI from ImageJ to matlab? Or how to save the ImageJ ROI to a file (such as nifti format)? -- Powered by www.kitware.com Please keep messages on-topic and c

Re: [CMake] ADD_CUSTOM_COMMAND Application dependency

Hello again, There can only be one working directory and the two lib's are located in different dirs. regards, Lars Date: Wed, 19 Nov 2014 19:21:54 +0100 Subject: Re: [CMake] ADD_CUSTOM_COMMAND Application dependency From: angeliki.chrysoc...@gmail.com To: laasu...@hotmail.com CC: cmake@cmake.org

Re: [CMake] ADD_CUSTOM_COMMAND Application dependency

Hi Angeliki, Thank you for the suggestions. I suspect your first example wont work because lib1 and lib2 are not in executable_output_path. So when the add_custom_command executes "App" it wont be able to resolve the dependencies to lib1 and lib2. If I only had one dependency I could possibly s

Re: [CMake] ADD_CUSTOM_COMMAND Application dependency

Hi Lars, I see...Why don't you set the working directory then to lib1 and lib2, and use the full path to App to call App? Not sure it will work, but maybe. Cheers! Angeliki On Wed, Nov 19, 2014 at 7:19 PM, Lars wrote: > Hi Angeliki, > > Thank you for the suggestions. > > I suspect your first

Re: [CMake] Imported targets with additional dependencies

I just received help on IRC. The solution is to use an INTERFACE target and INTERFACE_LINK_LIBRARIES (and NOT LINK_INTERFACE_LIBRARIES). Hauke On Wed Nov 19 2014 at 2:26:54 PM Hauke Heibel wrote: > Hi, > > I would like to declare an imported target which uses a header only > library and which

[CMake] Imported targets with additional dependencies

Hi, I would like to declare an imported target which uses a header only library and which has some further link dependencies. If need be, I can specify a use case for this. I thought I could simply declare this target as add_library(Foo::Foo UNKNOWN IMPORTED) and then configure its dependencies

Re: [CMake] ADD_CUSTOM_COMMAND Application dependency

Hi Lars, What if you provide the working directory to ADD_CUSTOM_COMMAND like this: add_custom_command( OUTPUT COMMAND command_to_be_executed DEPENDS ${lib1} ${lib2} WORKING_DIRECTORY ${EXECUTABLE_OUTPUT_PATH} VERBATIM) Would it work? Otherwise a trick (more like a ha

[CMake] ADD_CUSTOM_COMMAND Application dependency

The below example build "App" and copies it to EXECUTABLE_OUTPUT_PATH. ADD_EXECUTABLE(App ${source}) TARGET_LINK_LIBRARIES(App ${lib1} ${lib2}) INSTALL(TARGETS App ..) The top level CMakeLists.txt has install directives for lib1 and lib2 INSTALL(FILES ${lib1}/bin/lib1.dll DESTINATION ...) INSTA

[CMake] copying dylibs into OSX bundle

Hi, I've been searching for how to copy some dylib dependencies for quite a while and can't seem to find a definitive answer on the problem. I have a .dylib file that needs to go into my app bundle (e.g. MyApp.app/Frameworks). From what I've read, to use the FIXUP_BUNDLE command, the file already