Getting gdc working with xcode 3.1

ylixir ylixir at gmail.com
Fri Sep 19 09:39:05 PDT 2008


just a quick correction of my previous post, actually i checked, and i 
have three sets of binaries, all universal, one that targets intel, one 
that targets ppc, and one that targets either, depending on the -arch 
switch, so i'm guessing that is exactly what you need.

Michel Fortin wrote:
> On 2008-09-18 04:38:49 -0400, Anders F Björklund <afb at algonet.se> said:
> 
>> Thanks for the update, I'm still planning to make a
>> release of "gdcmac" for Leopard and might as well aim
>> for Xcode 3.1 and gcc-5484 instead of 3.0 and gcc-5465.
>>
>> Or maybe stick with the original "plan" and go straight
>> for gcc_42 instead, for the fictional GDC 0.25 release ?
>> Along with upgrading MinGW's GCC to 4.2.1, for "gdcwin"...
> 
> Anything that runs out of the box with no show stopper is an improvement 
> from what we have now.
> 
> I've been trying too to build a working GDC with the intent of creating 
> a D for Xcode package including the compiler, debugger, linker and my D 
> for Xcode plugin with some project and file templates all together for 
> easy installation. I want to distribute a universal binary compiler 
> capable of PowerPC and Intel output, but I haven't had much success in 
> compiling it up to now.
> 
> My current approach is to compile four compilers (PowerPC to PowerPC, 
> PowerPC to Intel, Intel to Intel, and Intel to PowerPC) and merge 
> executables into universal binaries using lipo. But I haven't been able 
> to compile anything but the first variant (PowerPC to PowerPC). Do you 
> have any tip for doing the rest, as you seem to have acheived it somehow 
> for gdcmac?
> 


More information about the D.gnu mailing list