in a header if it was included from assembler or not (if anybody knows a better
way how to solve this, feel free to speak, I haven't found anything :).
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@2367 a95241bf-73f2-0310-859d-f6bbb57e9c96
`-nostdinc' flag from the CCFLAGS and C++FLAGS in R5Objects. The R5 tests
must be compiled with the system header.
* Introduced SetupR5Includes which simply clears HDRS.
* Fixed rule Filter.
* Removed some unnecessary `""' in CCFLAGS and C++FLAGS assignments.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@1948 a95241bf-73f2-0310-859d-f6bbb57e9c96
needed to be gristed, but actually all invocations supplied ungristed
files. The rule does add grist itself now.
* Added SharedLibraryFromObjects rule.
* Fixed a serious bug in ObjectReference.
* Added rules and variables needed for building the FreeType2 library.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@1489 a95241bf-73f2-0310-859d-f6bbb57e9c96
done to fix some build issues (BeBuild.h).
If you have a better idea on how to solve this - or a different idea how things
should work, please go on :-)
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@1117 a95241bf-73f2-0310-859d-f6bbb57e9c96
that build the tests NOT override the global optimization and debug
settings.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@1065 a95241bf-73f2-0310-859d-f6bbb57e9c96
with obos libs and r5 tests are run with r5 libs, two separate
unit testing programs in different directories would be needed.
Thus UnitTester is now just a shell program that calls the
appropriate unittester/UnitTester or unittester_r5/UnitTester_r5
program.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@703 a95241bf-73f2-0310-859d-f6bbb57e9c96
- Verbosity is now honored globally
- Added BTestCase::Outputf()
- Migrated BNode, BStatable, BDirectory, and BPath tests
- Added CommonTestLib, TestLib, and R5TestLib rules to Jamrules
- Updated Jamfiles for unit testing stuff
- Probably a few other things I've forgotten
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@269 a95241bf-73f2-0310-859d-f6bbb57e9c96
* Added section for compatibility with original Jam.
* Replaced Clean/Depends with LocalClean/LocalDepends where necessary.
* Added checking of the variable DEBUG. If set compile and link flags are
adjusted to generate info for source level debugger.
* Fixed problem with object specific variable setting: VAR on target += value ;
is equivalent with VAR on target = value ; if VAR has not been set on this
target before, even if the global VAR is set. We need to be careful with
CCFLAGS, LINKFLAGS, LINKLIBS and the like.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@259 a95241bf-73f2-0310-859d-f6bbb57e9c96
BuildKernel and KernelFloppyImage. Now the kernel and the floppy image
depend correctly on there generating tools.
* New InstallFloppy rule to simplify the process of building and writing
the floppy image.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@225 a95241bf-73f2-0310-859d-f6bbb57e9c96
* Added rules ObjectReference and ObjectReferences which allow for using
another identifier referring to an object. In particular useful in
combination with...
* Added *.o case in UserObject rule. It does simply nothing. This lets
you add objects to the list of sources for Objects or Main rules. Very
nice, if you want to (re-)use an object built in another directory.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@178 a95241bf-73f2-0310-859d-f6bbb57e9c96
* Added Chmod1 to wrap the filename in "".
* Added rule RelSymLink that makes it easier to create a relative symlink
between two targets.
git-svn-id: file:///srv/svn/repos/haiku/trunk/current@143 a95241bf-73f2-0310-859d-f6bbb57e9c96
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
