Thanks man, I&#39;ll give it a try. Pretty frustrating though that there seems to be no way to do this without modifying Boost.Build.<br><br><div class="gmail_quote">On Tue, Apr 26, 2011 at 1:29 AM, Matthew Chambers <span dir="ltr">&lt;<a href="mailto:matt.chambers42@gmail.com">matt.chambers42@gmail.com</a>&gt;</span> wrote:<br>

<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">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:<br>


<a href="http://proteowizard.svn.sourceforge.net/viewvc/proteowizard/trunk/pwiz/libraries/boost-build/tools/msvc.jam" target="_blank">http://proteowizard.svn.sourceforge.net/viewvc/proteowizard/trunk/pwiz/libraries/boost-build/tools/msvc.jam</a><br>


<br>
I didn&#39;t look at your Jamfiles, but in your case I think you should specify the DLLs as &lt;assembly-dependency&gt;.<br>
<br>
Hope this helps,<br>
-Matt<div><div></div><div class="h5"><br>
<br>
<br>
On 4/24/2011 10:04 AM, Joshua Boyce wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I&#39;m currently using Boost.Build as my library&#39;s build system, and I&#39;m using Boost.Test for the unit<br>
testing, however I&#39;ve run into a problem with one of my tests. The library I&#39;m trying to test has<br>
two binary dependencies, which I just &#39;install&#39; (using the Boost.Build install rule) when I build my<br>
application, however I can&#39;t work out how to drop the DLLs alongside the unit tests binaries.<br>
<br>
I have tried adding them as dependencies using the &#39;project&#39; rule, but that doesn&#39;t cause the files<br>
to be copied as part of the unit test build phase (it works for the install rule however when my<br>
application is built).<br>
<br>
Is there any way I can have Boost.Build copy over my dependencies to the unit test&#39;s binary dir<br>
before it is run? If I can&#39;t do this is renders a large portion of my library untestable using this<br>
system, as the DLLs are critical to its operation.<br>
<br>
In case it matters, the DLLs I&#39;m referring to are the DbgHelp and SymSrv DLLs from the redist dir of<br>
the latest &quot;Debugging Tools for Windows&quot; package.<br>
<br>
My library can be found here:<br>
<a href="https://code.google.com/p/hadesmem/" target="_blank">https://code.google.com/p/hadesmem/</a><br>
Direct link to relevant files:<br>
<a href="https://code.google.com/p/hadesmem/source/browse/trunk/Jamroot" target="_blank">https://code.google.com/p/hadesmem/source/browse/trunk/Jamroot</a><br>
<a href="https://code.google.com/p/hadesmem/source/browse/trunk/Src/Memory/Jamfile.v2" target="_blank">https://code.google.com/p/hadesmem/source/browse/trunk/Src/Memory/Jamfile.v2</a><br>
<a href="https://code.google.com/p/hadesmem/source/browse/trunk/Tests/Jamfile.v2" target="_blank">https://code.google.com/p/hadesmem/source/browse/trunk/Tests/Jamfile.v2</a><br>
<br>
Thanks in advance.<br>
<br>
P.S. Feel free to point out any problems you see with how I&#39;m using the build system, including ways<br>
I could simplify or improve my usage.<br>
</blockquote></div></div>
_______________________________________________<br>
Unsubscribe &amp; other changes: <a href="http://lists.boost.org/mailman/listinfo.cgi/boost-build" target="_blank">http://lists.boost.org/mailman/listinfo.cgi/boost-build</a><br>
</blockquote></div><br>