From: Vladimir Prus (ghost_at_[hidden])
Date: 2002-04-11 10:29:42
David Abrahams wrote:
> ----- Original Message -----
> From: "Vladimir Prus" <ghost_at_[hidden]>
> > I meant that we should assume that jam has been already built in the
> > current working copy and invoke that binary. This way we'll be sure that
> > we test against the version of jam that is in CVS.
> That sounds fair to me. Anybody so perverse as to want to test without
> building Jam first can put a copy in the appropriate place.
> However, note that the appropriate place may change from host platform
> to host platform, and various bin.<platform> directories may be present
> in any given jam_src directory.
I've committed changes that make the test system look for jam binary in the
same working copy. Now
1) You can't invoke tests from anywhere except tools/build/test
2) You can invoke from tools/build/test and it will find jam build in
../jam_src. No need to specify absolute path in BoostBuild.py.
> > Okay... I'll apply it and then will write a wrap project-test1.jam in
> > a test which will just check the output.
Writing the first reasonable test is delayed till tomorrow's morning.
> > > shutil.copytree(tree_location, self.workdir)
> > > File "c:\tools\Python-2.2\lib\shutil.py", line 91, in copytree
> > > names = os.listdir(src)
> > > WindowsError: [Errno 3] The system cannot find the path specified:
> > > 'c:\\boost\\tools\\build\\test\\test2/*.*'
> > Strange! Are you sure that the "test2" directory really exists?
> No, it doesn't! was something supposed to be checked in there?
> If I add that directory manually, I get:
Actually, the zip file link to which I've posted contains test2 dir with some
content. I just don't want to check in an example test to cvs. When we'll
start writing actual test, it would be easy to resolve the issues.
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