Re: [CMake] best practice for bundling 3rdparty dependencies in, windows

Since I have wrestled with this on a recurring basis let me offer the following. We package Qt. OpenSceneGraph and other libraries as 3rdParty content to the application we build/deploy. Because the 3rd party libraries have their own plugins and dependencies, we end up doing a number of thing

Re: [CMake] gathering directory names in cmake

list to remove file names, remove doubles from the result, etc. On 6/22/2016 10:52 AM, cmake-requ...@cmake.org wrote: On Mon, Jun 20, 2016 at 8:47 PM, Lee Butler wrote: >I have a source tree which contains multiple directories each of which has >a subdirectory called "xyz". I

[CMake] gathering directory names in cmake

I have a source tree which contains multiple directories each of which has a subdirectory called "xyz". I want to create a target that creates a zip file with each of the xyz directories. So if the source tree looks like src src/xyz src/application src/application/xyz src/plugins/one/xyz

[CMake] Is there a better way to retrieve content from a remote zip file?

I am looking for a better way to do something than having a sequence of "if (NOT EXISTS)" statements. My package being built depends on some external libraries and headers, that are available in a zip file on an external website. So for example: zlib.h,zlib.dll and zlib.lib are (along with o

Re: [CMake] Release and Debug build linking

So if this is the case, how does one "write correctly" the find/config module so that both debug and release libraries are found? I've got a library I depend on whose maintainer may not have built the best Find module in the world. I've looked at https://cmake.org/Wiki/CMake/Tutorials/How_to

[CMake] Release and Debug build linking

I am looking for a way to tell my project to link against external debug libraries with a debug build and external release libraries with a release build with Visual Studio. I sort of want to be able to say something like if (BuildingReleaseConfig) find_package(OtherPackage REQUIRED COMPONENTS

[CMake] Thoughts on infrastructure for fixup_bundle

I've started using fixup_bundle(). One of the things that occurs to me is that much of the information that needs to go into fixup_bundle() arguments (executables and library directories) can be gleaned from arguments to add_executable() and target_link_libraries(). It might be nice to extend

[CMake] Setting default install prefix?

Is there a way to override CMAKE_INSTALL_PREFIX in a multi-level CMake project? Since my package has a long history of being installed in a location other than /usr/local, I really want to have the default match previous practice. For example, I have a source tree that looks like this: ro