[openbeos-build-team] OBOS Headers, Unit Tests
- From: "Ingo Weinhold" <bonefish@xxxxxxxxxxxxxxx>
- To: "Build Team" <openbeos-build-team@xxxxxxxxxxxxx>
- Date: Sat, 06 Jul 2002 15:52:10 CEST (+0200)
Hi,
yesterday I fixed some issues concerning the usage of OBOS headers. I
believe no CVS mail had been sent -- cvs reported not being able to get
the user name for the UID -- therefore I want to outline the problem
here.
High level rules like Preference, Server, UnitTest,... Static/
SharedLibrary invoke SetupIncludes which adds all public OBOS include
directories to the list of header search directories. This makes our
header files "shadow" equally named Be headers and will be highly
desirable when more or less everything has been implemented. But
currently we need certain Be headers, since the ours are not complete
or differ in some respects. OS.h is a good example for this, as it
caused that neither libopenbeos.so nor the unit test(s) did compile
anymore. Therefore I commented out SetupIncludes in SharedLibrary and
UnitTest and added the public include directories in the concerned
Jamfiles explicitly via UsePublicHeaders. I think, for the time being
it would be a good idea to do the same for the other high level rules
as well.
Apropos unit tests. When writing tests it is very desirable to have the
possibility to run them against the libbe implementation. Therefore it
would be nice to build two versions of the tests -- one using Be's
implementation and one using ours. I think of a rule similar to
UnitTest that may apply UnitTest to build both versions. Additional
parameters would be the public include directories and the libraries.
BTW, it is not that simple to implement, because the Objects rule adds
the same grist on both sets of files -- cf. my other mail. I had to
find a solution for the Storage Kit tests...
CU, Ingo
Other related posts:
- » [openbeos-build-team] OBOS Headers, Unit Tests
