Putting a project rule in Jamroot produces errors

I'm using Boost.Build V2 (Milestone 11) Boost.Jam 03.1.15 to
build a 
project with 12 shared libraries.

The code for each library is in a separate subdirectory.
The requirements of each library are largely the same making
it 
desirable to move the project rule to the Jamroot file in
the common 
parent directory.
However, when move my project from my Jamfile to ../Jamroot,
I get:

$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:840:
in 
try-one-generator-really
*** argument error
* rule object(gcc-linking-generator)34.run ( project name ? : 
property-set : sources + )
* called with: ( object(project-target)64 canvas
: 
object(property-set)91 :  )
* missing argument sources
$BOOST_ROOT/boost/tools/build/v2/tools/gcc.jam:391:see
definition of 
rule 'run' being called
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:902:
in 
try-one-generator
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:1110:
in 
construct-really
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:1186:
in 
generators.construct
$BOOST_ROOT/boost/tools/build/v2/tools/builtin.jam:490: in 
object(lib-generator)5.run
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:840:
in 
try-one-generator-really
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:902:
in 
try-one-generator
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:1110:
in 
construct-really
$BOOST_ROOT/boost/tools/build/v2/build/generators.jam:1186:
in 
generators.construct
$BOOST_ROOT/boost/tools/build/v2/build/targets.jam:1398: in
construct
$BOOST_ROOT/boost/tools/build/v2/build/targets.jam:1242: in

object(typed-target)72.generate
$BOOST_ROOT/boost/tools/build/v2/build/targets.jam:765: in
generate-really
$BOOST_ROOT/boost/tools/build/v2/build/targets.jam:738: in 
object(main-target)78.generate
$BOOST_ROOT/boost/tools/build/v2/build/targets.jam:255: in 
object(project-target)64.generate
$BOOST_ROOT/boost/tools/build/v2/build-system.jam:402: in
load
$BOOST_ROOT/boost/tools/build/v2/kernel/modules.jam:261: in
import
$BOOST_ROOT/boost/tools/build/v2/kernel/bootstrap.jam:132:
in boost-build
$BOOST_ROOT/boost/tools/build/v2/boost-build.jam:8: in
module scope



Is it possible to do what I'm trying to do?
If so, how.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Jeff Holle wrote:

> I'm using Boost.Build V2 (Milestone 11) Boost.Jam
03.1.15 to build a
> project with 12 shared libraries.

Please try the nightly build from boost.org/boost-build2
first.
If that does not fix the problem, provide a self-contained
minimal 
example reproducing this problem, as a archive file.

> 
> The code for each library is in a separate
subdirectory.
> The requirements of each library are largely the same
making it
> desirable to move the project rule to the Jamroot file
in the common
> parent directory.
> However, when move my project from my Jamfile to
../Jamroot, I get:

Given this information, it's unexpected you got any error.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Vladimir Prus wrote:
> Please try the nightly build from
boost.org/boost-build2 first.
Did this, no joy.  Same situation.
> If that does not fix the problem, provide a
self-contained minimal 
> example reproducing this problem, as a archive file.
Attached is a tar ball containing:
   Jamroot
   editor/Jamfile
   editor/result

The Jamroot file contains the project rule that if in
editor/Jamfile 
will produce a functional build.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

On Thursday 19 July 2007 22:12:58 Jeffrey Holle wrote:
> 
> Vladimir Prus wrote:
> > Please try the nightly build from
boost.org/boost-build2 first.
> Did this, no joy.  Same situation.
> > If that does not fix the problem, provide a
self-contained minimal 
> > example reproducing this problem, as a archive
file.
> Attached is a tar ball containing:
>    Jamroot
>    editor/Jamfile
>    editor/result
> 
> The Jamroot file contains the project rule that if in
editor/Jamfile 
> will produce a functional build.

You have forgotten to attach anything.

- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

I forgot the important step!

Vladimir Prus wrote:
> On Thursday 19 July 2007 22:12:58 Jeffrey Holle wrote:
>   
>> Vladimir Prus wrote:
>>     
>>> Please try the nightly build from
boost.org/boost-build2 first.
>>>       
>> Did this, no joy.  Same situation.
>>     
>>> If that does not fix the problem, provide a
self-contained minimal 
>>> example reproducing this problem, as a archive
file.
>>>       
>> Attached is a tar ball containing:
>>    Jamroot
>>    editor/Jamfile
>>    editor/result
>>
>> The Jamroot file contains the project rule that if
in editor/Jamfile 
>> will produce a functional build.
>>     
>
> You have forgotten to attach anything.
>
> - Volodya
>
>   

_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Jeff Holle wrote:

> I forgot the important step!

I indeed get the same error. But, ehm, you
don't have any .cpp files in the 'editor' dir.
When I add empty a.cpp, everything works.

I'd agree that the 'linking-generator' should
have a nicer way to say "I've got nothing to
link",
but that will only change the wording, not
the presence of error -- I hope you'll agree that
silently doing nothing is not the best thing.

- Volodya


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build