| Re: [AD] Typo in RLE docs |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
> I just thought that the problem with mingw and an installed msys
> could be simply avoided if we add another target, say msys, which
> could be pretty close to the unix target.
On the configure side, possibly, but it will always be a Windows port anyway.
And I'd like to avoid mixing Windows and Unix stuff at the configure level.
As I said elsewhere, the Unix-like configure method is too big a hammer for
the minor portability problems we can run into on the Windows side.
> If this is too much work, the msys target could use the mingw32-make
> instead, and then the normal mingw build process.
Could you point me to threads which describe problems with MSYS? I have been
systematically testing Allegro with MinGW+mingw32-make and MSYS+msys-make
for some months now and never run into a problem. Allegro 4.0.3 and 4.1.9
build out of the box on my system (Win98SE) for both platforms.
--
Eric Botcazou