Boost logo

Boost-Build :

Subject: Re: [Boost-build] Current directory in unit tests
From: Ian Emmons (iemmons_at_[hidden])
Date: 2009-02-01 17:19:46


After some time away from this project, I've had a chance to try this
out, and indeed, using <testing.launcher> this way does not work. It
seems to me that a <working-directory> property would be a very useful
addition to Many programs (including bjam itself) rely
on the working directory, and so testing them requires setting that
directory properly. Every debugging tool I've ever used allows
setting this, and so it would be natural for the unit testing rules to
support it as well. Could you add this to your list of feature



On Jan 28, 2009, at 10:23 PM, Steven Watanabe wrote:


Juraj Ivančić wrote:
> run
> [ glob *.cpp ]
> /site-config//BoostUnitTest
> : # args
> : # input files
> : <include>.
> <threading>multi
> <testing.launcher>"cd $(testDir) && "
> : ParliamentTest
> : # default build
> ;

It seems a bit doubtful that this will work because the
path to the executable is probably relative to the current
working directory.

In Christ,
Steven Watanabe

Boost-Build list run by bdawes at, david.abrahams at, gregod at, cpdaniel at, john at