Boost logo

Boost :

Subject: Re: [boost] [fusion] preprocess target pull request
From: Eric Niebler (eniebler_at_[hidden])
Date: 2014-01-27 14:17:22

On 01/25/2014 05:39 AM, Mathias Gaunard wrote:
> On 23/01/14 03:38, Agustín K-ballo Bergé wrote:
>> On 21/01/2014 07:56 p.m., Eric Niebler wrote:
>>> I'm not sure who gets notified of pull requests, if anybody. Sending
>>> mail for good measure.
>> I've tried to regenerate preprocessed headers, but I get the following
>> error:
>> error: Unable to find file or target named
>> error: '/boost/libs/wave/tool//wave'
>> error: referred to from project at
>> error: '.'
>> error: could not resolve project reference '/boost/libs/wave/tool'
>> From looking at the jam file, I'm not entirely sure how is it supposed
>> to find Wave. When I build wave, for some reason it ends up at
>> "/libs/dist/bin/wave.exe".
> I have the same problem. Something wrong has apparently happened to the
> build rules of wave.
> It used to be in dist/bin/wave, not libs/dist/bin/wave.

Hartmut answered this.

> Moreover it appears the RPATH is incorrect. I had to manually fix this.

You mean, to find the .so? I "fixed" this by using static linking.

> In any case, to run wave in my project I personally use the following
> CMake code:
> <>
> Example of usage here:
> <>
> It only works with GCC/Clang, but it's fully correct and has no
> hardcoded stuff that needs to be changed by whoever needs to use it.
> What it does is that it asks GCC what its system include directories are
> and what its basic predefined macros are, and also uses the include
> directories currently set up to be used for the project you're building.
> I have found all those steps to be necessary in order to be able to run
> wave on arbitrary C++ code.

Nice. I considered doing something similar myself, but I don't have the
BBv2 chops to make it happen.


Boost list run by bdawes at, gregod at, cpdaniel at, john at