[haiku-development] Re: GCC 2 x GCC 4.
- From: PulkoMandy <pulkomandy@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 13 Aug 2008 16:23:03 +0200
What about a GGC2 build including GCC4 libs for compatibility and
experimentation ?
That would give a full binary-compatible (and well-tested) system, but
still allow to work on projects such as Webkit and other apps and
ported things (it's likely that more and more apps will need gcc4 in
the future ...).
... is that even possible, anyways ?
2008/8/13 Axel Dörfler <axeld@xxxxxxxxxxxxxxxx>:
> Bruno Albuquerque <bga@xxxxxxxxxxxxx> wrote:
>> Now that we are able to have a dual system for running applications
>> compiled with both GCC versions, I wonder if it would not be a good
>> idea
>> to compile Haiku with GCC 4 by default and provide the GCC 2
>> libraries.
>> The reason being that this would be a clear signal to people that
>> they
>> should use GCC 4 from now on and considering we will have to do this
>> at
>> some point, now is probably a good time to do it.
>>
>> We can even provide both tool chains and a way for developers to
>> switch
>> between the two if they wanted. WHat do you guys think?
>
> I don't think this is a good idea.
> By keeping the emphasis on GCC2 for Haiku R1 we can do a clean break
> with R2 - that means full backwards compatibility, and still have all
> the great API changes for GCC 4 compiled apps.
> If we switched to GCC4 now, we would just break compatibility for no
> better reason than the choice of the default compiler. Projects that
> really need it can use it, but they know that their software will no
> longer run without a recompilation on future Haiku releases.
> IOW as long as no one forces you to use GCC4, you should use GCC2 for
> now.
>
> Of course, this is pretty much independent from having Haiku compiled
> with GCC4, but since it's much better tested with GCC2, and our GCC4
> version is not really up-to-date, but has some known problems, as well
> as some pending bugs (like the Radeon driver Rene mentioned), I don't
> see good reason to do so shortly before a release.
>
> Bye,
> Axel.
>
>
>
Other related posts:
