Error with Boost scope

[M. Dodson]

>> 
>> Specifically, my waf has:
>> 
>> includes = [
>> ...
>> '/Users/michaeldodson/projects/rtems_root/boost_1_72_0',
>> '/usr/local/include’]
>> 
>> It seems to be finding the header files just fine, as the errors are associated with a declaration within the header that isn’t in scope.
> 
> You should not use standard installation paths of your host system for header files of the RTEMS target. This may accidentally pull in undesired header files.

I’m possibly misunderstanding your statement:

I was only including '/Users/michaeldodson/projects/rtems_root/boost_1_72_0’ (the location of the Boost libraries built with the RTEMS cross-compilation tools.  The errors I reported were based on a build only using that include path.

Then, in response to your previous email (which I clearly misunderstood), I added ‘/usr/local/include’, just to see if it changed the output.  It didn’t.

> 
> I would look at the pre-processed files (-save-temps -Wp,--dD) to figure out what happens.
> 

I’m new to waf.  Where’s the right place to add compiler flags?

I tried adding them to the existing bld.env.CFLAGS += ['-O2','-g’] line in the top-level wscript, but it didn’t produce any .i or .s files.