Subject: Re: [Boost-build] Using pre-built shared libraries with unit-test
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2009-01-26 22:49:41
Johan Nilsson wrote:
> when using shared library targets as a dependency to a unit-test
> target, their path(s) are automatically set in the environment before
> actually running the unit-test target (under Windows, at least).
> # NOTE: These library definitions actually refer to "import"
> libraries. Dlls are located in the same directory.
> lib foo
> : <file>$(ROOT)/deps/lib/foo-mt-gd.lib <link>shared <variant>debug
> However, the path of the "foo" library doesn't seem to be used by the
> unit test. Is there a simple way to have unit-test set up the
> additional path component before running the "bar" unit-test?
You'll want to add the search directory to the usage requirements.
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