[haiku-development] Re: A modest (FatELF) proposal
- From: François Revol <revol@xxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Thu, 29 Nov 2012 18:46:12 +0100
On 29/11/2012 18:02, pulkomandy wrote:
> On Thu, Nov 29, 2012 at 01:06:32PM +0100, Ingo Weinhold wrote:
> This needs a support in the toolchain (-l has to look at the libs for
> the target binary, not the one for the gcc that's running), but then it
> will be about as trasnparent to users and devs as it is right now:
>
> setgcc arm
> make
> setgcc x86_gcc2
> make
> setgcc x86_gcc4
> make
>
> And you'd get a set of 3 binaries (or 3 packages) ready for testing.
>
The setgcc approach is unclean.
We shouldn't need to switch compilers this way.
They should be both available with prefixes, and only use setgcc to
change the aliases for buildsystems that can't handle passing compiler
names.
This would allow compiling something with gcc4 and another one with gcc2
at the same time without caring about synchronization, or (but that's
not really clean) compiling C99 C files with gcc4 and the GUI C++ files
with gcc2 to make apps usable as replicants (thinking about NetSurf
there, I've been told to do this several times).
François.
Other related posts:
