Is there anyway to use boost headers without setting any include path or system variables? The problem is that the headers include each other and they do so using
#include "boost/..."
so the root boost folder has to be in the include path for it to find anything. Unfortunately, I'm trying to enter the AI Challenge, which doesn't allow any control over the build process, so it is impossible to set an include path. I suppose it's possible to modify all the headers so they use relative paths, but that is complicated to do and I was hoping there was a better way.
use boost without include path?
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?
Or if you only use several boost headers, how about change them manually, just spending half an hour?
Is this for the ai challenge at aichallenge.org? If so, they do allow you to modify the default makefile.
If you submit your bot with the Makefile included, the server will attempt to use this when compiling your bot, otherwise it will revert back to the auto compile script that is available on the contests github site.[/quote]
Oh really? I thought they specifically said that they didn't allow makefiles. I guess I'll give that a try then.
Edit: Here it is, from the contest organizer himself.
[quote="amstan"]You can alter any part of the zip package. Makefiles will be ignored, they're not used, the code is compiled with a different script.
About function documentation for the starter package, idk. Checking the source would be your best bet, that way you actually know what's going on.[/quote]
Edit: Here it is, from the contest organizer himself.
[quote="amstan"]You can alter any part of the zip package. Makefiles will be ignored, they're not used, the code is compiled with a different script.
About function documentation for the starter package, idk. Checking the source would be your best bet, that way you actually know what's going on.[/quote]
Google tells me that was in response to a post from last year. Even if it was true then, there's no reason to expect it to be true this year when the website directly contradicts it. It's pretty fundamental. You can presumably submit more than once, so why not just try it with a custom makefile? It'll be less effort than untangling the headers.
(Also, couldn't you just put the root 'boost' directory into the zip? Or am I being daft...)
(Also, couldn't you just put the root 'boost' directory into the zip? Or am I being daft...)
You could put the boost directory in the zip but it wouldn't compile because the headers include themselves with an absolute path.
You could put the boost directory in the zip but it wouldn't compile because the headers include themselves with an absolute path.
Important distinction between #include <boost/ and #include "boost/ in your first post, then!
This topic is closed to new replies.
Advertisement
Popular Topics
Advertisement