Subject: Re: [Boost-build] Unit tests and DLL hell
From: Matthew Chambers (matt.chambers42_at_[hidden])
Date: 2011-04-25 11:29:49
I use a hacked msvc.jam for supporting C++/CLI projects and targets that require side-by-side DLLs
(assemblies, assembly dependencies, registry-free COM via SxS manifests). It works for the most part
but there are some rough edges:
I didn't look at your Jamfiles, but in your case I think you should specify the DLLs as
Hope this helps,
On 4/24/2011 10:04 AM, Joshua Boyce wrote:
> I'm currently using Boost.Build as my library's build system, and I'm using Boost.Test for the unit
> testing, however I've run into a problem with one of my tests. The library I'm trying to test has
> two binary dependencies, which I just 'install' (using the Boost.Build install rule) when I build my
> application, however I can't work out how to drop the DLLs alongside the unit tests binaries.
> I have tried adding them as dependencies using the 'project' rule, but that doesn't cause the files
> to be copied as part of the unit test build phase (it works for the install rule however when my
> application is built).
> Is there any way I can have Boost.Build copy over my dependencies to the unit test's binary dir
> before it is run? If I can't do this is renders a large portion of my library untestable using this
> system, as the DLLs are critical to its operation.
> In case it matters, the DLLs I'm referring to are the DbgHelp and SymSrv DLLs from the redist dir of
> the latest "Debugging Tools for Windows" package.
> My library can be found here:
> Direct link to relevant files:
> Thanks in advance.
> P.S. Feel free to point out any problems you see with how I'm using the build system, including ways
> I could simplify or improve my usage.
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