"the headers include themselves with an absolute path. "
I don't know what platform you're on, but on my Linux system, they all say "#include <boost/WHATEVER>"
use boost without include path?
You could always just pre-process all files locally. Most of relevant boost stuff is header only.
Author
"the headers include themselves with an absolute path. "
I don't know what platform you're on, but on my Linux system, they all say "#include <boost/WHATEVER>"
I meant absolute in terms of the boost directory. If boost isn't in your include path, then #include <boost/WHATEVER> won't work. As opposed to just #include "WHATEVER", which would work since it's in the same directory.
Author
I tried that and it doesn't work. You'd have to nest a new copy of the boost directory for every level of inclusion.
I tried that and it doesn't work. You'd have to nest a new copy of the boost directory for every level of inclusion.
That implies something is pretty screwed up in your build system - it should always start from the top-level directory where your makefile resides.
Author
If you know regular expression and a decent script, such as Perl or Python, or you are a master of Unix commands, it's easy to change all headers to remove "boost/".
Or if you only use several boost headers, how about change them manually, just spending half an hour?
I actually tried writing a Python script to fix all the include paths. It's harder than it sounds because they use macros to define some of the includes, and filenames of headers also appear in the comments. However, I managed it eventually.
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement
