Subject: Re: [Boost-build] Copy previous build target into current unit test directory
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2017-08-01 16:53:13
On 08/01/2017 09:55 AM, Chambers, Matthew via Boost-build wrote:
> I am in a similar situation as the OP. I have a unit-test but don't see
> an obvious way to copy my lib target's output to the unit-test
> directory. I dug back through the archives and found this post as the
> closest explanation of how to do what I want without making deeper
> modifications to Boost.Build.
> The lib is a SQLite extension (shared object or DLL), so the unit test
> needs to know the path to it to load it (and I'd rather avoid the
> complexity of changing to a run target and passing the lib target as an
> input file). This would apply to dynamic plugin systems in general, too.
> Where do I put the @common.copy to get the lib copied? Do I have to
> convert the lib target to a make target, or is the `make mylib.dll`
> below supposed to be in addition to an implied `lib mylib` target?
If you're using unit-test, then as long as
the lib is in the same project and uses the
same properties as the unit-test, it will be
built in the same directory.
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk