Subject: Re: [Boost-build] Jamfiles for unit tests
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-10-15 15:07:35
Boris Schaeling wrote:
> It doesn't help. As far as I can tell it's not a problem with
> auto-linking really. If I add a few more references to other Boost
> libraries and run 'bjam -n' I see that the linker is looking for these
> files (for example):
> All the files exist except libboost_test-vc90-mt-gd-1_39.lib. The file
> is actually called libboost_unit_test_framework-vc90-mt-gd-1_39.lib.
> It doesn't matter either if I create debug or release versions or link
> statically or dynamically. Everytime a file boost_test... is looked up
> while it should be boost_unit_test_framework...
> If I remove <library>/boost//test and add
> <linkflags>libboost_unit_test_framework-vc90-mt-gd-1_39.lib it all
> works again. But I would prefer a toolset-independent Jamfile.
> This looks like a bug in the Jamfiles of Boost.Test to me. Can I
> overwrite the basename of a library in my Jamfile to make Boost.Build
> look up boost_unit_test_framework... and not boost_test...?
I see. This looks like a bug in the boost module. Can you
apply the attached patch and use /boost//unit_test_framework?
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