Re: [Boost-build] Reporting include paths for a project

Subject: Re: [Boost-build] Reporting include paths for a project
From: Mateusz Loskot (mateusz_at_[hidden])
Date: 2013-12-06 12:35:05

On 6 December 2013 01:06, Steven Watanabe <watanabesj_at_[hidden]> wrote:
> On 11/15/2013 01:50 AM, Mateusz Loskot wrote:
>>
>> That could serve as a little prosthesis for a solution I'm looking for.
>>
>> I don't want to actually build, just inspect some build setup.
>> So, I'd have to do sort of a dry-run, I guess, with:
>>
>> b2 -d2 -n
>>
>> However, I'd have to implement compiler-specific parsing, meaning,
>> I'd have to do the job Boost.Build already does, doesn't it?
>>
>> Alternative solution is to create Jamfile parser on my own,
>> but that's scary overkill that would repeat the job already done.
>>
>> Shortly, if Boost.Build knows what to pass to compiler, why it couldn't
>> echo it out in an easily consumable form.
>>
>
> The biggest problem with that is what should it echo?

b2 --list-include-paths
/a/b/c
/a/b/c/d
/usr/include

> There's a lot of information, and what's convenient
> for your use case isn't necessarily what anyone else needs.

This particular idea is very simple, and I believe concesus
would be easy to achieve: get accumulated list of include directories
inferred by Boost.Build for my project.

> What you can do is write a Jamfile that prints
> out this information.
>[...]
> It would look something like this (untested):
> [...]

That looks interesting, thank you!
I will experiment with this approach.

Best regards,
-- 
Mateusz  Łoskot, http://mateusz.loskot.net