Jacob Carlborg wrote:

>>> I included the patch and a binary in the package meanwhile.
>>
>> It would be really nice with a D integration that works with Xcode 3.1
> 
> And that has support for DSSS and Tango

My packages for DSSS and Tango can both be found upstream:

http://svn.dsource.org/projects/dsss/downloads/0.78/dsss-0.78-mac-10.4.dmg

http://downloads.dsource.org/projects/tango/0.99.6/tango-0.99.6-mac-10.4.dmg

They were built with the GDC revision matching DMD 1.0.24:

http://downloads.sourceforge.net/gdcmac/gdc-trunk-r206-mac-10.4.dmg

The packages for Tango 0.99.7 and GDC r229 were delayed...
But would be find at addresses similar to the ones above.

--anders

On 2008-09-21 13:52:19 -0400, Anders F Björklund <afb@algonet.se> said:

>> Anything that runs out of the box with no show stopper is an improvement from what we have now.
> 
> I'm not aware of any showstoppers on Mac OS X Tiger or
> Windows XP, just that Mac OS X Leopard of Windows Vista
> hasn't been "supported" with the current package releases.

Well, I meant that the latest gdcmac wouldn't run out of the box on Mac OS X Leopard. You have to include manually the standard library path and the linker doesn't work very well for PowerPC (Apple's fault, I know, but still one more thing to figure out and fix). Perhaps showstopper was a little harsh; basically, it doesn't "just work" as it should, there are still a couple of problems to figure out and solve before it works.

>> 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?
> 
> I used the Apple version of GCC and built it the Apple way.
> And it's actually 4 output targets, including the 64-bit...
> Similarly I used the MinGW version of GCC and their script.

Yeah, I know now. I think I've been following the wrong instructions. ylixir made me realize that.

-- 
Michel Fortin
michel.fortin@michelf.com
http://michelf.com/

Anders F Björklund wrote:
> Jacob Carlborg wrote:
> 
>>>> I included the patch and a binary in the package meanwhile.
>>>
>>> It would be really nice with a D integration that works with Xcode 3.1
>>
>> And that has support for DSSS and Tango
> 
> My packages for DSSS and Tango can both be found upstream:
> 
> http://svn.dsource.org/projects/dsss/downloads/0.78/dsss-0.78-mac-10.4.dmg
> 
> http://downloads.dsource.org/projects/tango/0.99.6/tango-0.99.6-mac-10.4.dmg 
> 
> 
> They were built with the GDC revision matching DMD 1.0.24:
> 
> http://downloads.sourceforge.net/gdcmac/gdc-trunk-r206-mac-10.4.dmg
> 
> The packages for Tango 0.99.7 and GDC r229 were delayed...
> But would be find at addresses similar to the ones above.
> 
> --anders
those are for xcode 2.4/2.5 though, aren't they? not 3.x?

Michel Fortin wrote:

> Well, I meant that the latest gdcmac wouldn't run out of the box on Mac OS X Leopard. You have to include manually the standard library path

I  didn't mess with the paths at all, everything just works on my system. Is that an issue still for some leopard systems?

On 2008-09-21 22:18:03 -0400, ylixir <ylixir@gmail.com> said:

> Michel Fortin wrote:
> 
>> Well, I meant that the latest gdcmac wouldn't run out of the box on Mac OS X Leopard. You have to include manually the standard library path
> 
> I  didn't mess with the paths at all, everything just works on my system. Is that an issue still for some leopard systems?

No indeed, not if you build it yourself.

I was talking about problems with the gdcmac build for Tiger available on gdcmac.sourceforge.net when it runs on Leopard. Basically the problem is that there is currently no installer for a gdc build working correctly on Leopard, the current one being for Tiger. It's not really a problem for me as I compiled my own version, but it surely is not very encouraging for someone who wants to try a new language and the only available builds don't work.

-- 
Michel Fortin
michel.fortin@michelf.com
http://michelf.com/

Michel Fortin wrote:
> On 2008-09-21 22:18:03 -0400, ylixir <ylixir@gmail.com> said:
> 
>> Michel Fortin wrote:
>>
>>> Well, I meant that the latest gdcmac wouldn't run out of the box on Mac OS X Leopard. You have to include manually the standard library path
>>
>> I  didn't mess with the paths at all, everything just works on my system. Is that an issue still for some leopard systems?
> 
> No indeed, not if you build it yourself.
> 
> I was talking about problems with the gdcmac build for Tiger available on gdcmac.sourceforge.net when it runs on Leopard. Basically the problem is that there is currently no installer for a gdc build working correctly on Leopard, the current one being for Tiger. It's not really a problem for me as I compiled my own version, but it surely is not very encouraging for someone who wants to try a new language and the only available builds don't work.
> 

oh yeah, true for sure. trying to get gdc working on my ibook was like ramming my head against a wall. it's frustrating when each failed attempt takes an entire day. that's why i made the step by step. if i ever have time to read up on how to make a package i'll probably do that, and upload it too unless someone beats me to it. no reason for people to roll their own compilers imho, especially since some of those people are just learning how to write hello world and doing a custom build would be basically impossible.

also, i don't feel that xcode 2.5 is really a choice.  ever try to compile from the command line with that toolchain?  annoying doesn't even begin to describe...

</rant>

ylixir wrote:

> those are for xcode 2.4/2.5 though, aren't they? not 3.x?

Correct.
I tired of fighting the bugs and downgraded back to Tiger.

Rumors has it that Mac OS X 10.5.5 and Xcode 3.1 is better,
so maybe I will give it another try some day in the future.

--anders

Michel Fortin wrote:

> Well, I meant that the latest gdcmac wouldn't run out of the box on Mac OS X Leopard. You have to include manually the standard library path and the linker doesn't work very well for PowerPC (Apple's fault, I know, but still one more thing to figure out and fix). Perhaps showstopper was a little harsh; basically, it doesn't "just work" as it should, there are still a couple of problems to figure out and solve before it works.

There are packages for those, in the "Leopard" directory of the image...

It'll still use Xcode 2.5 rather than Xcode 3.0, but should limp along.

--anders