| Re: [AD] extra note for Mac OS X build doc |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: Re: [AD] extra note for Mac OS X build doc
- From: Matthew Leverton <meffer@xxxxxxxxxx>
- Date: Tue, 17 May 2005 07:22:54 -0500
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=FVakKwO4NauCd6Cc9/cyikLdw8Fl0XfeV5Pig8Aw/lQz02mlCVJ5aM7y6ntUclJhl6hFIrLJpcLA/YLAOlimFATfPN9WOkoKCZzIiBvXaQYOcrncEFn+dA67Qj96aXTrkCpVApY7uz+fC+XqaDVfbQynbewKWyQ6xIOH6tZxrHk=
> I've read about Macs supporting something called bundles, which
> allows them to create multi version binaries. Is there any chance
> for Allegro to create bundles which work for older versions?
>
I'm not very familiar with OS X, so I don't know how that works. It
would seem kind of pointless to double the archive size (a new copy of
Allegro and the application) just to fix a linking bug that need not
exist.
The problem here is due to some bug with gcc 4. See my test thread:
http://www.allegro.cc/forums/view_thread.php?_id=490191
And another thread from someone else:
http://www.cocoabuilder.com/archive/message/cocoa/2005/5/1/134410
Essentially gcc 4 creates a bogus dependency on "libmx" that prevents
it from working. As it is now, any programmer that uses OS X 10.4
(with the default gcc 4) will be under the false impression that the
binary built will work on previous versions of the OS.
--
Matthew Leverton
http://www.allegro.cc