Boost logo

Boost-Build :

From: Jürgen Hunold (hunold_at_[hidden])
Date: 2005-03-24 02:35:13

Hi Volodya !

On Wednesday 23 March 2005 08:50, Vladimir Prus wrote:

> > Yes. These warnings should only appear when the stated libraries
> > are actually _build_.
> > Now, they are issued when these libraries are onle _referenced_ by
> > some Jamfile which happens to have "use-project /boost $BOOT_ROOT"
> > in it...
> This is probably possible to fix, but them you'll get the warning
> whenever you use Boost.Regex, even though library is usable without
> ICU.

Yes, this would be the consequence.

> Probably the right approach is either:
> 1. Boost has a top-level config.jam file that is included from
> Jamfile. When Boost.Regex is first built, it produces the big warning
> and appends some line to config.jam, indicating that the warning was
> emitted once. On subsequent invocations, the warning is not emitted.

-1 on this one.

> 2. Same as above, but user must manually edit config.jam to disable
> the warning.

-1 on this one. This would be sufficient for the experienced user, but
not for new users.

> 3. Some initial "configure" step, which emits many warnings and
> disables the targets that can't be built. The configure step should
> be run once, of course.

+1 on this. Remember that many people have been complaining that bjam
has no "autoconf/automake" features. So there should be some
"configure" and "re-configure" system ;-)
And during this step one could issue even _more_ information, e.g. an
URL _about_ ICU or Boost.Python Doumentation.



* Dipl.-Math. Jürgen Hunold ! Institut für Verkehrswesen, Eisenbahnbau
* voice: ++49 511 762-2529 ! und -betrieb, Universität Hannover  
* fax : ++49 511 762-3001 ! Appelstrasse 9a, D-30167 Hannover
* hunold_at_[hidden] !

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