[fusion] preprocess target pull request
https://github.com/boostorg/fusion/pull/1 I'm not sure who gets notified of pull requests, if anybody. Sending mail for good measure. -- Eric Niebler Boost.org http://www.boost.org
On 1/22/14, 6:56 AM, Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
I'm not sure who gets notified of pull requests, if anybody. Sending mail for good measure.
I got notified. Merged. Thank you very much Eric! Much appreciated! Cheers, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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". It seems I'm missing something obvious, but I know nothing about jam files. Which steps do I need to take to regenerate the preprocessed headers? Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com
On 1/23/14, 10:38 AM, Agustín K-ballo Bergé wrote:
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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".
It seems I'm missing something obvious, but I know nothing about jam files. Which steps do I need to take to regenerate the preprocessed headers?
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors: https://gist.github.com/djowel/8572818 Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss? Regards, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/
On 1/22/2014 8:34 PM, Joel de Guzman wrote:
On 1/23/14, 10:38 AM, Agustín K-ballo Bergé wrote:
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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".
It seems I'm missing something obvious, but I know nothing about jam files. Which steps do I need to take to regenerate the preprocessed headers?
You need to sync the super-project. The /boost/libs/wave/tool project is defined in Jamroot. See: https://github.com/boostorg/boost/blob/master/Jamroot#L251
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors:
https://gist.github.com/djowel/8572818
Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss?
I don't know. :-( Eric
On 1/23/14, 2:23 PM, Eric Niebler wrote:
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors:
https://gist.github.com/djowel/8572818
Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss?
I don't know. :-(
I got it. I failed to notice the wave.cfg: -S..\include -S..\..\.. The reversed-slash does not work. So changing it to: -S../include -S../../.. Now I have to figure out the right includes. Hmmm... There must be a better way to do this. I guess we can issue different configs depending on (tested) platform in the jamfile. Regards, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/
On 1/22/2014 11:52 PM, Joel de Guzman wrote:
On 1/23/14, 2:23 PM, Eric Niebler wrote:
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors:
https://gist.github.com/djowel/8572818
Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss?
I don't know. :-(
I got it. I failed to notice the wave.cfg:
-S..\include -S..\..\..
The reversed-slash does not work. So changing it to:
-S../include -S../../..
Now I have to figure out the right includes. Hmmm... There must be a better way to do this. I guess we can issue different configs depending on (tested) platform in the jamfile.
Right, this wave.cfg is for when your toolset is msvc-12.0. I should probably rename the file to make that more obvious. You can grab a gcc-ish wave.cfg files from libs/phoenix/preprocess and hack it appropriately. Eric
On 1/23/14, 2:23 PM, Eric Niebler wrote:
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors:
https://gist.github.com/djowel/8572818
Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss?
I don't know. :-(
I got it. I failed to notice the wave.cfg:
-S..\include -S..\..\..
These are real C-strings, iirc. Thus you'd have to write: -S..\\include -S..\\..\\.. HTH Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
The reversed-slash does not work. So changing it to:
-S../include -S../../..
Now I have to figure out the right includes. Hmmm... There must be a better way to do this. I guess we can issue different configs depending on (tested) platform in the jamfile.
Regards, -- Joel de Guzman http://www.ciere.com http://boost-spirit.com http://www.cycfi.com/
_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
On 1/23/2014 4:35 AM, Hartmut Kaiser wrote:
On 1/23/14, 2:23 PM, Eric Niebler wrote:
In my case, I am able to run wave (Clang on Mac OS). However, I am getting some errors:
https://gist.github.com/djowel/8572818
Should I do some config to get the includes working? I looked at the wave.cfg file and it seems sufficient. What did I miss?
I don't know. :-(
I got it. I failed to notice the wave.cfg:
-S..\include -S..\..\..
These are real C-strings, iirc. Thus you'd have to write:
-S..\\include -S..\\..\\..
Why? wave.cfg isn't a C file. The phases of translation aren't done when wave reads it, are they? \e
I got it. I failed to notice the wave.cfg:
-S..\include -S..\..\..
These are real C-strings, iirc. Thus you'd have to write:
-S..\\include -S..\\..\\..
Why? wave.cfg isn't a C file. The phases of translation aren't done when wave reads it, are they?
It's just the way it is :-P Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
On 23/01/2014 03:23 a.m., Eric Niebler wrote:
On 1/22/2014 8:34 PM, Joel de Guzman wrote:
On 1/23/14, 10:38 AM, Agustín K-ballo Bergé wrote:
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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".
It seems I'm missing something obvious, but I know nothing about jam files. Which steps do I need to take to regenerate the preprocessed headers?
You need to sync the super-project. The /boost/libs/wave/tool project is defined in Jamroot. See:
Indeed, I tend to forget the super project has content too... After that it's working fine, thank you! Regards, -- Agustín K-ballo Bergé.- http://talesofcpp.fusionfenix.com
On 23/01/14 03:38, Agustín K-ballo Bergé wrote:
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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. Moreover it appears the RPATH is incorrect. I had to manually fix this. In any case, to run wave in my project I personally use the following CMake code: https://github.com/MetaScale/nt2/blob/master/cmake/nt2.preprocess.cmake Example of usage here: https://github.com/MetaScale/nt2/blob/master/modules/boost/simd/base/src/CMa... 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.
On 23/01/14 03:38, Agustín K-ballo Bergé wrote:
On 21/01/2014 07:56 p.m., Eric Niebler wrote:
https://github.com/boostorg/fusion/pull/1
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. Moreover it appears the RPATH is incorrect. I had to manually fix this.
In any case, to run wave in my project I personally use the following CMake code: https://github.com/MetaScale/nt2/blob/master/cmake/nt2.preprocess.cmake Example of usage here: <https://github.com/MetaScale/nt2/blob/master/modules/boost/simd/base/src/ CMakeLists.txt> 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.
During the transition to git somebody decided to move the wave tool from the tools directory to the libs/wave directory without properly fixing the build system. However I don't know enough about this to fix it. I'd appreciate any help I could get on this. Regards Hartmut --------------- http://boost-spirit.com http://stellar.cct.lsu.edu
On Sat, Jan 25, 2014 at 8:59 AM, Hartmut Kaiser
tools directory to the libs/wave directory without properly fixing the build system. However I don't know enough about this to fix it. I'd appreciate any help I could get on this.
Hartmut, if this is still a problem you might want to repost the above request on the boost-build mailing list. Thanks, --Beman
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:
https://github.com/boostorg/fusion/pull/1
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: https://github.com/MetaScale/nt2/blob/master/cmake/nt2.preprocess.cmake Example of usage here: https://github.com/MetaScale/nt2/blob/master/modules/boost/simd/base/src/CMa...
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. Eric
participants (6)
-
Agustín K-ballo Bergé -
Beman Dawes -
Eric Niebler -
Hartmut Kaiser -
Joel de Guzman -
Mathias Gaunard