[interfacekit] Re: BString

> >>Yeah, tests. I really need to write unit tests for BString. The 
> > > problem
> >>is that I really can't understand why support tests don't compile 
> > > for me
> >>(or is it a known problem?). If those tests compiled, I could just 
> > > add
> >>mine and test if they work.
> > 
> > Mmh, strange, I haven't tried to compile the support tests for a 
> > while,
> > but IIRC I had no problems last time I did. I will have a look at 
> > it in
> > the evening.
> 
> I will also look into this.  Let's keep this dialog running until the 
> issue is solved for everybody.

Compiles fine for me (latest version from CVS). The only problem I can 
image is a jam/build system user error. The vanilla version of jam (the 
one available on DevCentral or BeBits) won't work when invoked in the 
`src/tests/kits/support' directory -- it must be called from the root 
of the source (`current') or at least the `src' directory. To build 
only the Support Kit tests, one can run `jam libsupporttests.so' for 
the OBOS tests or `jam libsupporttests_r5.so' for the R5 tests. The 
hacked jam version (the one in src/tools/jam) can also be called from 
subdirectories.

To use the test add-ons the unit tester executables have to be built 
before (`jam UnitTester UnitTesterHelper UnitTesterHelper_r5'). Or just 
run `jam alltests', which makes all test suites and everything needed 
to run them -- this will take a while though.

However, if the problem is not just a user error, please provide some 
output from jam or the tool that fails.

CU, Ingo

PS: A lot of BArchivable tests fail. Some with errors like 
B_LAUNCH_FAILED_APP_NOT_FOUND. Sounds like some external application 
can't be found. Maybe some problem caused by the relocation of the unit 
tester executables. Haven't had a closer look yet, though.

Other related posts: