Boost logo

Boost-Build :

Subject: [Boost-build] [git] genrating forward headers
From: Bjørn Roald (bjorn_at_[hidden])
Date: 2013-07-16 08:58:25


I am trying the patches for b2 support of generating forward headers.
Latest post on this I found was:

http://lists.boost.org/boost-build/2013/06/26812.php

As conversion to git is up and running again, this need some care and I
intended to do some testing to attempt to get the
https://svn.boost.org/trac/boost/wiki/TryModBoost process steps working
smoothly.

The patches I have is derived from Jürgen's patches here:

http://lists.boost.org/boost-build/2013/05/26798.php

However as it looked to me most of the changes in tools/build except
from addition of try-build and changes to build-raw in config.jam has
been applied to trunk and thus is part of what git clone provide.

Nevertheless, I am more lost than Jürgen I guess as I get an error in
configure.jam executing this new code:

+# Attempts to build a set of virtual targets
+rule try-build ( targets * : ps : what : retry ? )
+{
+ local cache-name = $(what) [ $(ps).raw ] ;
+ cache-name = $(cache-name:J=-) ;
+ local value = [ config-cache.get $(cache-name) ] ;

build-raw was changed to call try-build like this:
+ result = [ try-build $(targets[2-]) : $(ps) : $(what) :
$(retry) ] ;
+ .$(what)-supported.$(ps) = $(result) ;

however in link.jam we have
if [ configure.try-build $(target) : "symlinks supported" ]

I can not figure out what to put as the missing "ps" or "what" required
parameter here, if anything. Are there some additional changes or later
patches I need?

Call stack is:

-*- mode: compilation; default-directory:
"/dsk1/ws/boost/modular-boost/" -*-
Compilation started at Tue Jul 16 14:42:07

./b2 headers
/dsk1/ws/boost/modular-boost/tools/build/v2/tools/link.jam:47: in
link.can-symlink
*** argument error
* rule configure.try-build ( targets * : ps : what : retry ? )
* called with: ( object(file-target)@1663 : symlinks supported )
* missing argument what
/dsk1/ws/boost/modular-boost/tools/build/v2/build/configure.jam:129:see
definition of rule 'configure.try-build' being called
/dsk1/ws/boost/modular-boost/tools/build/v2/tools/link.jam:146: in construct
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:1332: in
class_at_basic-target.generate
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:757: in
generate-really
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:729: in
class_at_main-target.generate
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:874: in
targets.generate-from-reference
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:1245: in
generate-dependencies
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:1302: in
class_at_basic-target.generate
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:757: in
generate-really
/dsk1/ws/boost/modular-boost/tools/build/v2/build/targets.jam:729: in
class_at_main-target.generate
/dsk1/ws/boost/modular-boost/tools/build/v2/build-system.jam:707: in load
/dsk1/ws/boost/modular-boost/tools/build/v2/kernel/modules.jam:289: in
import
/dsk1/ws/boost/modular-boost/tools/build/v2/kernel/bootstrap.jam:139: in
boost-build
/dsk1/ws/boost/modular-boost/boost-build.jam:17: in module scope

Compilation exited abnormally with code 1 at Tue Jul 16 14:42:07

--
Bjørn

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