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

Subject: Re: [Boost-build] prototyping alternative Boost.Build syntax
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-10-29 15:31:51

On 29.10.2016 15:24, Vladimir Prus wrote:
> Stefan,
>
> On 29-Oct-16 5:45 AM, Stefan Seefeld wrote:
>> Now I'm getting this error when invoking `.../b2 --python` in
>> example/hello:
>>
>> $ ../../src/engine/bin.linuxx86_64/b2 --python
>> Boost.Build V2 Python port (experimental)
>> error: unexpected exception
>>     descriptor 'difference' requires a 'set' object but received a
>> 'list'
>>
>>     error context (most recent first):
>>     - Generating target ./hello
>>         declared at:
>>         - jamroot.jam:1
>>
>>     use the '--stacktrace' option to get Python stacktrace
>
>
> It sound like you might be using old codebase. I have this commit on
> top:
>
>     commit 710428b6387940727a4a7ad72e28238a71a3840a
>     Author: Aaron Boman <aaron_at_[hidden]>
>     Date:   Thu Oct 27 20:00:27 2016 -0500
>
>         Fix unintentional masking of ImportErrors. Closes #121
>
> And example/hello builds for me.

Indeed it does; thanks !

> Even with the current codebase, you might encounter errors if your
> user-config.jam or project-config.jam use modules that are not yet
> ported, you can solve that by removing project-config.jam,
> and pointing to an empty user-config.jam, like so:
>
>    b2 --python --user-config=/path-to-empty/user-config.jam

Right, I noticed that and used an empty user-config.jam file.

Any ideas about what I'm missing when interfacing with the "bjam" Python
module in bootstrap.py, or how to enable logging / tracing / debugging
to see what my calls to "bjam.define_action()" and "bjam.call()" are
doing (if anything) ?

Thanks,
        Stefan

-- 
      ...ich hab' noch einen Koffer in Berlin...