[openbeos] Re: [haiku-development] Coordinating ports (#2) (was: Re: Distributed Version Control Tools)
- From: "François Revol" <revol@xxxxxxx>
- To: openbeos@xxxxxxxxxxxxx
- Date: Tue, 22 Apr 2008 01:02:23 +0200 CEST
>
> Am 22.04.2008 um 00:16 schrieb Urias McCullough:
>
> > On 21/04/2008, Jorge G. Mare (aka Koki) <koki@xxxxxxxxxxxxxx>
> > wrote:
> >> François,
> >>
> >> This looks like a great summary.
> >>
> >> May I suggest that you put it into a document on the website, so
> >> that we
> >> can link to it from the development page? ;)
> >
> > I was going to suggest something similar... Perhaps the beginnings
> > of
> > a "Porting software to Haiku" document that starts with some
> > initial
> > advice and eventually can be fleshed out to include other tips and
> > suggestions.
>
> Well, I did ask about a place for porting information some weeks ago
> and the only real suggestion that came up was BePorts iirc. I'd
> welcome such "official" information on the website.
>
> But somehow contrary to what François has listed, Ingo (or was it
> Axel?) has specifically asked not to base Haiku ports on BeOS ports
> because some workarounds may no longer be necessary. Thus, searching
> for BONE or R5 ports on BeBits should not be a high priority on the
> checklist.
Some of them aren't needed, but others are still required (like
stripping out -lm from makefiles...).
That doesn't mean you should get the patch and replace beos with haiku
blindly.
But read it, and try to understand why things are here, and if they are
still needed might save you some time.
>
> IM Kit btw seemed to be native BeOS software, not a port.
Yes but as I had some local fixes around I included it in the list.
François.
Other related posts:
