Thanks, this is exactly what I need.
Unfortunately constructing the path expansion involves some gymnastics.
If Find* exposes a list of directories it's just a simple list join (->
boost) but if it does not it is more involved..
list(JOIN Boost_LIBRARY_DIRS ";" BOOST_PATH)
set(ZLIB_PATH "")
Can also add install rules so you get an INSTALL target, and then you can
just build that, and everything will end up in the right place.
On Thu, Nov 21, 2019 at 3:56 AM Fred Baksik wrote:
> Adding the relevant directories to PATH in the debugger or build
> environment should allow them to be
Adding the relevant directories to PATH in the debugger or build environment
should allow them to be found.
On Wed, Nov 20, 2019, at 3:32 AM, Petr Kmoch wrote:
> Hi.
>
> I haven't used it yet, but I believe the target property
>
:mike.jack...@bluequartz.net
Voice: 937-790-1601 Web: http://www.bluequartz.net/
Fax: 937-746-0783
From: CMake on behalf of Petr Kmoch
Date: Wednesday, November 20, 2019 at 3:32 AM
To: cen
Cc: CMake
Subject: Re: [CMake] Missing dll on program startup - a way automate it?
Hi.
I haven't u
Hi.
I haven't used it yet, but I believe the target property
https://cmake.org/cmake/help/latest/prop_tgt/VS_DEBUGGER_ENVIRONMENT.html
might help you.
Petr
On Wed, 20 Nov 2019 at 01:02, cen wrote:
> Hi
>
> Perhaps not really a cmake problem but here we go. An exe depends on a
> few DLLs which
Hi
Perhaps not really a cmake problem but here we go. An exe depends on a
few DLLs which I ship in the repo so the rest of the devs don't have to
build them or fetch them somewhere else. Cmake finds the libraries and
project builds just fine, until you run it from VS.. you are welcomed by
