I'm not sure if this is added in the correct way, please fix it.
As many files generate warnigs, it's inactive by default.
To compile with enabled warnings, execute jam like this:
$ WARNINGS=true jam
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@141 a95241bf-73f2-0310-859d-f6bbb57e9c96
easiest way to fix it was to use <Errors.h> and simply include the
header path in our build line.
Can someone on the buidl team please try and tell us what path's
are/aren't being used? No doubt it'll take about 100 messages and
a lot of violent arguing, but then maybe sanity will prevail? :)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@106 a95241bf-73f2-0310-859d-f6bbb57e9c96
* Reintroduced Axel's fix to the public header dirs.
* Pulled the functionality to set the headers on object files out of
Use*Headers and put it into new rules Use*ObjectHeaders. The usage differed
too much.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@42 a95241bf-73f2-0310-859d-f6bbb57e9c96
BTW the last change of this file requires updating your OBOS_TOP variable
to the current tree.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@40 a95241bf-73f2-0310-859d-f6bbb57e9c96
amok...
* Added rules SplitPath and SymLink used in the Storage Kit tests Jamfile.
* Removed the setting of CCFLAGS and C++FLAGS on the SystemMain target.
This really doesn't made sense.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@23 a95241bf-73f2-0310-859d-f6bbb57e9c96