|
[openbeosnetteam]
||
[Date Prev]
[10-2005 Date Index]
[Date Next]
||
[Thread Prev]
[10-2005 Thread Index]
[Thread Next]
[openbeosnetteam] Re: Networking and the new Build System
- From: Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx>
- To: openbeosnetteam@xxxxxxxxxxxxx
- Date: Fri, 28 Oct 2005 01:03:31 +0200
On 2005-10-28 at 00:32:58 [+0200], Axel Dörfler wrote:
> Ingo Weinhold <bonefish@xxxxxxxxxxxxxxx> wrote:
> > As you should best know, we are not 100% source compatible -- the
> > networking
> > stuff is an excellent example. But that's not even the point. BeOS
> > simply
> > isn't forward binary compatible with Haiku. Hence when compiling
> > something
> > with our headers, there's a chance that it won't work under BeOS.
>
> 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.
> 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.
CU, Ingo
|
|
