|
[haiku-development]
||
[Date Prev]
[05-2008 Date Index]
[Date Next]
||
[Thread Prev]
[05-2008 Thread Index]
[Thread Next]
[haiku-development] Re: To __BEOS__ or not to __BEOS__?
- From: Andreas Färber <andreas.faerber@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 7 May 2008 10:52:12 +0200
Am 07.05.2008 um 09:40 schrieb François Revol:
from my experience with porting stuff to Haiku so far, I've come to
see the
fact that our gcc also defines __BEOS__ as quite a mixed blessing. In
a lot
of cases one has to (respectively it makes sense to) disable BeOS
work-arounds in software that had been ported to BeOS before. What do
you
think about dropping __BEOS__?
I thought we wanted to be source and binary compatible with BeOS for
R1...
doing so before R1 would break source level compatibility, so I would
avoid doing that.
We've already broken source compatibility by removing the libnetwork
symlinks then. Might it be an option to make this configurable in Jam?
That is, if some variable or parameter is specified, create a strict
development package (without libsocket, __BEOS__ etc.), and by default
keep it source-compatible?
Andreas
|
|
