Re: [Boost-build] prototyping alternative Boost.Build syntax

Subject: Re: [Boost-build] prototyping alternative Boost.Build syntax
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2016-10-29 15:45:42

AMDG

On 10/28/2016 10:04 PM, Stefan Seefeld wrote:
> 
>    ...
>    bjam_interface = __import__('bjam')
>    bjam_interface.define_action("gcc.compile", "g++ -c -o $(<) $(>)", [], 0)
>    bjam_interface.call("gcc.compile", "hello.o", "hello.cpp")
>   #return b2.build_system.main()
> 
> (I assume the invocation of 'b2.build_system.main()' is responsible for
> locating Jamfiles and doing all the other stuff that I'd like to skip
> when interfacing with the low-level API, yes ?)
> 
> This doesn't seem to do anything at all. At least it doesn't generate
> "hello.o", and doesn't print any (error) message either. Is there any
> command-line option I can use to cause the execution to be traced (I
> tried "-d+2" and "--debug-building" with no visible effect).
> 

I'm guessing that the problem is that hello.o is
not in the update list.  Try adding
bjam_interface.call("UPDATE", ["hello.o"])

In Christ,
Steven Watanabe