From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-01-15 08:40:51
----- Original Message -----
From: "Joerg Walter" <jhr.walter_at_[hidden]>
> How do you like the idea of unifying the signatures of the duplicated
> That could IMO mean something like unifying
> - boost-test and boost-unit-test to accept target : sources : requirements
> local-build : target-type
> - run-test and run-unit-test to accept target : sources : requirements
> - run etc and unit-test to accept target : sources : requirements :
> local-build : command-line
Well, sure: do we need separate rules in these cases? What is the difference
> I'd currently prefer to include tests.jam in boost-base.jam.
> > Removing the setting of RUN_LD_LIBRARY_PATH from Link-EXE looks like a
> > mistake. What if you build an EXE that depends on some built shared
> > I think transmission of RUN_PATH and LD_LIBRARY_PATH ought to happen
> > unconditionally, regardless of platform, and LD_LIBRARY_PATH should
> > contain only library path dependencies, while RUN_PATH contains only
> > executable path dependencies. When these things reach a point where they
> > must be interpreted (e.g. a testing rule), they should be combined on NT
> > appropriate. That will make the code lots cleaner, don't you think?
> > plus the build actions become smaller and more readable. On Unix it
> > contain the string "$PATH", on NT "%PATH%". Just a short string.
> I understand. I'll check that again. BTW, SHELL_SET and SHELL_EXPORT are
> currently not defined in allyourbase.jam for at least VMS and MacOS.
Do we have any VMS users? It seems like a mistake to try to code something
we can't test.
MacOS 9 isn't really supported for by the build system; IOW I've been
ignoring it purposefully ;-). I assume the UNIX sections will handle OS X.
Maybe shortsighted: I have a couple Macs here but no time to program them,
except when I boot one in Linux ;^). Anyway, if you want to help with
Mac/VMS support, I'm sure someone will appreciate it!
P.S. You didn't send any attachments. At this point I'd be happy if you'd
just update the CVS once you're satisfied that we have the issues clear.
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