This is not exactly a bug on the Boost scripts, but related to the way biicode works.
When biicode searches for dependencies based on include directives, it searches following block patterns since originally all sourcecode was supposed to live inside a block.
Since that's not the case for Boost, its sources are located on a biicode environment folder shared by all biicode projects on your computer, bii is not able to find that headers even if Boost works fine.
Boost works perfectly, but I don't like the deps viewing tool printing all Boost includes as unresolved. We are working on a solution for this little issue.
This is not exactly a bug on the Boost scripts, but related to the way biicode works.
When biicode searches for dependencies based on include directives, it searches following block patterns since originally all sourcecode was supposed to live inside a block. Since that's not the case for Boost, its sources are located on a biicode environment folder shared by all biicode projects on your computer, bii is not able to find that headers even if Boost works fine.
Boost works perfectly, but I don't like the deps viewing tool printing all Boost includes as unresolved. We are working on a solution for this little issue.