[openbeosnetteam] Re: Networking and the new Build System

Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > But we can only compile applications with Be's headers - that won't
> > work for anything "below". We are not compatible when it comes to
> > private methods and member variables. How is this solved, then?
> > (I'd guess that stuff is just not compiled for R5?)
> Good question. The old build system simply always used our headers. 
> The 
> COMPILE_FOR_R5 macro kludge in our headers made it possible to keep 
> them R5 
> compatible. I don't like that very much, though.

Indeed, that's not very nice. Well, we'll eventually see if there are 
any problems.
I mostly expect problems in the test/ directory.

> > But that also complicates things like libopenbeos.so, doesn't it?
> For libopenbeos we naturally use our headers/public/os headers. 
> Unfortunately I also had to throw in our POSIX headers for some 
> reasons -- 
> that could probably be remedied by adding a compatibility header that 
> is 
> autoincluded by all source files (via -include). But I postpone that 
> for 
> the moment; such things usually turn out to be more work than 
> expected.

It doesn't look that urgent either - as long as the resulting 
libopenbeos.so works as expected, that is :)

Bye,
   Axel.

Other related posts: