[haiku-development] Re: my build environment problems

On 2007-06-15 at 13:29:06 [+0200], Michael Berg <mike@xxxxxxxxxxx> wrote:
> On 6/15/07, Axel Dörfler <axeld@xxxxxxxxxxxxxxxx> wrote:
[...]
> > From here on out R5 will mean R5 and Dano unless stated otherwise :)
> I am able to build quite a few things
> in R5.  I'm wondering if I should go back and "fix" the stuff that
> doesn't.  For
> example last night I started looking at cortex, since it doesn't compile.  I
> found that most of the problems were with missing class references.  I fixed
> them, now it is hitting me with some real errors.  Do I fix these and submit
> a patch or is it unnecessary for some apps to compile under R5.  I guess
> what it boils down to is does the project want someone to be testing and
> fixing these old targets.  If R5 binary compatibility is a goal of R1
> shouldn't these builds be maintained?

One has nothing to do with the other. R5 binary compatibility means, that 
executables built using the BeOS compatible tool chain, headers, and 
libraries can be run under Haiku. Haiku code doesn't need to build under 
BeOS. In fact it can't in cases where new or incompatible API (e.g. layout 
management) is used. Support for compiling Haiku components for BeOS will be 
phased out.

If you have a particular app that you think is a must-have under BeOS, we can 
add BeOS build support for it, but I don't see the point in systematically 
"fixing" all apps that don't build on BeOS. If you want to help, I'm certain 
we can heap other tasks upon you, which would yield more benefit for the 
project. :-)

CU, Ingo

Other related posts: