Our case is pretty simplified in that almost every executable uses the
dependent DLLs/SOs I need copied. For C# apps it is log4net, NDesk.Options,
etc. For native apps it’s fmpeg shared libraries.
So when I create the list at configure time, I immediately just use CMake
to copy the files the
On 2018-7-12 15:16, J. Caleb Wherry wrote:
in one of our projects, we use copy_if_different to copy some DLLs
required by the runtime. It's called as post-build action. The problem
is that several targets want to copy the same DLLs, and when using
parallelized builds, the different "cmake -E
Had the same problem and went with #2
-Caleb
On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette
wrote:
> Hello,
>
> in one of our projects, we use copy_if_different to copy some DLLs
> required by the runtime. It's called as post-build action. The problem
> is that several targets want to copy
Personally would go with option number 2
On Thu, Jul 12, 2018 at 1:58 AM Olivier Croquette
wrote:
> Hello,
>
> in one of our projects, we use copy_if_different to copy some DLLs
> required by the runtime. It's called as post-build action. The problem
> is that several targets want to copy the
Hello,
in one of our projects, we use copy_if_different to copy some DLLs
required by the runtime. It's called as post-build action. The problem
is that several targets want to copy the same DLLs, and when using
parallelized builds, the different "cmake -E copy_if_different" can
conflict,
