[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] Re: OSX x86 patch
- From: "Miguel A. Gavidia" <juvinious@xxxxxxxxxx>
- Date: Sat, 8 Apr 2006 13:05:47 +0800
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:from:to:subject:date:user-agent:references:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:message-id; b=Mpm03ok1ovUJB2WBxRrGOoylVwYsKPs5+dEx1f2sdjNRSB+4X/PfKVp4suyApAZ2tfHxQdNON7aybI8d692GXzVBHSYqWEWN8fGGRNIYEtTUZXJXjv8YBTLLfAXmXq23sAMW9vsoVU8jrXv8R36/TpNE1VkrkDfdxqhQTHymBSQ=
Ugh disregard that patch I just ran into an issue. I guess there still needs
to be stuff resolved with ALLEGRO_USE_C and ALLEGRO_NO_ASM. :(
Also I noticed that #define ALLEGRO_I386 was added to alosxcfg.h which still
makes the lib include the asm routines.
Even after removing the line the lib still includes the asm routines..
*sigh
I'll have to comb through it some more and see if I can trace the issues down.
On Saturday 08 April 2006 11:50, Miguel A. Gavidia wrote:
> I went through and added some changes to get allegro to build on OSX x86,
> which after the changes compiles and installs soundly.
> I also reviewed the thread concerning ALLEGRO_USE_C and took into
> consideration that if ALLEGRO_USE_C is explicitly declared the assumption
> is that no ASM is desired. With the OSX build of allegro that it is
> statically set so there should be no qualms regarding usage of ASM.
> The patch otherwise shouldn't effect the usage of ASM if ALLEGRO_USE_C is
> never set on other platforms.
> Look over the patch and see if it is feasible.
> Thanks. :)
--
-juvinious
<a href="http://chasm.hopto.org">The Chasm</a> - My Site.