[CMake] Copying of 3rd party DLLs in a POST-BUILD step

[Ben Medina]

I'd guess the performance of fixup_bundle will be a big pitfall if
you're planning on doing this after every build.

An entirely different approach is to configure a Visual Studio .user
file to set the PATH environment variable (not setting it globally;
just for debugging your app from within VS). You still have to track
which directories to add to the PATH, but this approach has worked
flawlessly for us (across multiple versions of VS, as well as 32- and
64-bit configs).

On Mon, Jan 9, 2012 at 8:41 AM, David Cole <david.cole at kitware.com> wrote:
> 2012/1/9 Hauke Heibel <hauke.heibel at googlemail.com>:
>> 2012/1/9 Michael Stürmer <m.stuermer at pmdtec.com>:
>>> Awesome! Sometimes you just need to know what's already available to solve your problems in a very elegant way. I'll have a look at these bundles and probably switch to them instead of maintaining my own stuff!
>>
>> When looking at the initial problem, I am pretty much convinced that
>> you need a combination of your own script and GetPrerequisites since
>> you want to copy to your run-time output directory - and there to
>> specific sub-directories depending on the build type.
>>
>> It may well be that I have overseen some functionality in those new modules ...
>>
>> - Hauke
>
> BundleUtilities, on Windows, should copy dlls to be in the same
> directory as the executable being analyzed... So, as long as the exe
> is in the right directory when fixup_bundle is called on it, then the
> dlls will get copied into that same directory.
>
>
> Cheers,
> David
> --
>
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the CMake FAQ at: http://www.cmake.org/Wiki/CMake_FAQ
>
> Follow this link to subscribe/unsubscribe:
> http://www.cmake.org/mailman/listinfo/cmake