[haiku-development] Re: To __BEOS__ or not to __BEOS__?
- From: Ingo Weinhold <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Tue, 06 May 2008 23:33:42 +0200
On 2008-05-06 at 23:10:25 [+0200], Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>
wrote:
> Ingo Weinhold <ingo_weinhold@xxxxxx> wrote:
> > 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__?
>
> As Stefano mentioned, it might be a drawback for some ports like SDL
> (or UAE, ...), but I wouldn't really mind getting rid of it.
> If it is really helpful for an existing port, one can still define
> __BEOS__ in the build system of that project for Haiku (to help with
> porting).
Yep, that would always remain as option. Also, I would strongly recommend
to review an old BeOS port instead of just compiling it for Haiku. A "grep
-ri beos" and a closer look at the matching locations is the least one
should do.
CU, Ingo
Other related posts:
