|
Boost Testing : |
From: Vladimir Prus (ghost_at_[hidden])
Date: 2005-08-03 08:58:47
Voronkov Konstantin wrote:
> Vladimir,
>
> I'm tried this
> >H:\tmp\Boost\Tutorials\sample1\test>process_jam_log.exe --v2
> H:\tmp\Boost\Tutorials\sample1\ 0<runAndPause.log
> boost_root:
>
H:/tmp/Boost/Tutorials/sample1/test/../../../../../../../../../../../../../../../../../../../../../../.
> ./../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../../..
> /../../../../../../../../../../../../..
> locate_root: H:/tmp/Boost/Tutorials/sample1
> no errors detected
>
> What is "../../../"? How to correct boost_root? I think
> the subproject rule is to fix this. How can I fix mine
> configuration that boost_root is in so strange location?
Here's the code:
boost_root = fs::initial_path();
while ( !boost_root.empty()
&& !fs::exists( boost_root / "libs" ) )
{
boost_root /= "..";
}
So no, you can't fix this in any way. The good news is that if you provide
locate_root explicitly, then the value of boost_root should not matter.
Do you get .xml files correctly created?
- Volodya