[AD] Building Allegro for MSVC using the latest Cygwin is broken |
[ Thread Index |
Date Index
| More lists.liballeg.org/allegro-developers Archives
]
- To: "Allegro Conductors [AD]" <Alleg-developers@xxxxxxxxxx>
- Subject: [AD] Building Allegro for MSVC using the latest Cygwin is broken
- From: Andrei Ellman <ae-a-alleg@xxxxxxxxxx>
- Date: Sat, 05 Mar 2005 14:07:33 +0100
- Organization: Wacko Software
Hi,
The latest version of Cygwin comes with a 'coreutils' package that
contains a program called 'link'. This clashes with MSVC's link.exe, so
that whenever the 4.1.18 WIP build-process is linking something, it
calls the wrong program.
For example...
obj/msvc/runner.exe link @ -nologo -release -subsystem:windows
-out:tests/win/dibgrab.exe obj/msvc/alleg/dibgrab.obj lib/msvc/alleg.lib
kernel32.lib user32.libgdi32.lib comdlg32.lib ole32.lib dinput.lib
ddraw.lib dxguid.lib winmm.lib dsound.lib
link: too many arguments
Try `link --help' for more information.
typing link --help reveals that it's a gnu program.
And yes, I did remember to run vcvars32.bat in a dos-box and then start
cygwin from within the same dos-box, so my MSVC environment variables
have been setup.
Building the Mingw32 version of Allegro however works fine. Also, I have
been able to build Allegro 4.1.18 WIP for MSVC using a two-year old
installation of Cygwin.
AE.