| Re: [AD] cross compile helper script. |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
Tom Fjellstrom <tfjellstrom@xxxxxxxxxx> wrote:
> If you know how to do it, fixing the configure script would
> be best. I have no clue how... :(
we don't _need_ a configure script for this i think. if i have understood
the configure scripts properly, what it does it to check how your system is
set up if you have the needed libraries etc. and compose a makefile with the
functionality you have specified (--with-x --enable-dga etc...). since we
already have a makefile for mingw32 which works 100% with the
cross-compiler, i don't think adding an entirely new configure script will
be a good idea. dead meat... and i don't really know how to write a
configure.in source either. i've just hacked it once to add
a --enable-pentiumopts option.
> or maybe just make the build process the same across all platforms,
> i.e.: have a fixming.sh and a fixdj.sh that setup the correct variables
> in the makefile then 'include' the regular makefile.mgw or makefile.dj
that was certainly not a bad idea. if it works then it will be better than
having a sepparate xmake.sh script.
> or I could have no idea what i'm talking about :)
hardly... ;o)
Eric Botcazou <ebotcazou@xxxxxxxxxx> wrote:
> You're the specialist on this topic, I would follow your mind.
I'm just an intermediate Unix user. George or Shawn are the true experts...
> Btw, wouldn't it be feasible to get rid of these annoying warnings
> (MAKEFOURCC redefined) issued during the compilation with Mingw32 ?
i think the warnings are due to multiple definition in the directx header
files. some of the allegro source files includes more than one DX header.
the obvious solution would be to create wrappers so that we sepparate
directx from allegro code or otherwise just make it so that no src/win/*.c
files includes more than one directx header. Any takers?
-henrik