From: Hugo Duncan (hugo_duncan_at_[hidden])
Date: 2003-10-22 09:41:54
--- In jamboost_at_[hidden], Vladimir Prus <ghost_at_c...> wrote:
> David Abrahams wrote:
> > > Or hash the directory name and only have something like:
> > >
> > > gcc/1234567/...
> The only problem with this is that target path stops being
extremely long and
> starts being expremely cryptic. I sometimes go to bin dir to look
> generated files, for example, and it would be nice to know which
dir to look
Could you generate a hashed path by default, but allow the user
to overide the generated name for a specific build?
Also, at least for me, the default usage is just to build a debug,
release or profile version - so what are the issues with names like
I can see that might cause problems if you change the definition
of the options used in a specific build.
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