| [AD] Re: Build Errors on Mac OSX (x86) |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: alleg-developers@xxxxxxxxxx
- Subject: [AD] Re: Build Errors on Mac OSX (x86)
- From: "Peter Hull" <peterhull90@xxxxxxxxxx>
- Date: Sat, 25 Mar 2006 10:00:46 +0000
- Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ui98nbeTxJTg1TWU8PV1jxzymwywRyPl2ITmGvTweis+LbKBfxmxNIME1WOvO+/osa/RdCF1oelz7MGRZWMaCwWn2P/f7WAq0tsFtnjh5qmIopHrygq+vS01OI/t01rYoQd2cBtq3YUTSgUaHLeI8IuGdbBtAek+3JOGPRQTgOM=
It should, but I'd like to be sure.
A bit more background about what I'm thinking:
There are 2 options now possible for Intel Macs - a pure C build or a
mixed C/asm one. I'm going for the former as I think it will be the
easiest to get up and running.
To get the mixed one to work, we would have to add the src/i386 stuff
to makefile.osx, undefine ALLEGRO_USE_C, and define ALLEGRO_I386. This
is more complicated, especially as there seem to be some differences
in the assembly dialect (that .balign stuff mentioned above). I'd rather go for a pure C build.
Pete
On 25/03/06, Evert Glebbeek <eglebbk@xxxxxxxxxx> wrote:
> > > Nope still getting them as undefined after removing that line.
> > > This is with and without ALLEGRO_USE_C=1
> > > There are several files that use these two items. :-/
> >
> >
> > Did you do a make clean first?
>
> Shouldn't make depend be enough?
>
> Evert
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by xPML, a groundbreaking scripting language
> that extends applications into web and mobile media. Attend the live webcast
> and join the prime developer group breaking into this new coding territory!
> http://sel.as-us.falkag.net/sel?cmdlnk&kid0944&bid$1720&dat1642
> --
> https://lists.sourceforge.net/lists/listinfo/alleg-developers
>