Talk:Building Chocolate Doom on Windows

build-chocolate-doom doesn't work on Cygwin without the "normal" gcc
It'll bomb out immediately saying it can't find gcc, even though it really ought to be looking for i686-pc-mingw32-gcc instead. --chungy (talk) 06:35, 27 October 2014 (UTC)


 * This can be worked around by something like

mkdir bin cd bin ln -s $(which i686-pc-mingw32-gcc.exe gcc) export PATH=$(pwd):$PATH cd ..

But the article should be updated to reflect this (or fix the script, but we're replacing it now)

-- Jdowland (talk) 21:47, 12 July 2016 (BST)

cygwin 64 vs 32
With 64 bit cygwin, mingw-gcc-core doesn't exist anymore, but mingw64-x86_64-gcc-core does; mingw-w32api doesn't and I'm not sure what a suitable alternative would be. There's a w32api-headers and w32api-runtime (heading: "MinGW-w64 Windows API libraries/headers for Cygwin"). -- Jdowland (talk) 21:42, 12 July 2016 (BST)

The SDL 1.2.15 configure script does not like the 64bit compiler, complaining that it doesn't create win32 executables.

Perhaps only 32 bit builds are "supported" for current -- Jdowland (talk) 21:49, 12 July 2016 (BST)

OK additional ,same error for gcc -> i686-w64-mingw32-gcc, which does produce win32 binaries. -- Jdowland (talk) 21:56, 12 July 2016 (BST)


 * instructions still all broken. new w32api packages might be: w32api-headers, w32api-runtime; cygwin32-w32api-headers; cygwin32-w32api-runtime -- DimensionalShambler (talk) 14:23, 10 March 2017 (UTC)


 * The list of packages on the page are not sufficient to get a cc or gcc in $PATH anymore. -- DimensionalShambler (talk) 15:12, 10 March 2017 (UTC)

Replacing Cygwin with MSYS2
The Cygwin instructions constantly go out of date (as they are at the moment of writing) due to changes to the Cygwin package names and general process. I've even been unsuccessful with building a _working_ EXE via the Cygwin mingw packages (which seem to be out of date frequently, as well).

I've personally experimented with MSYS2 and it seems like a very good solution. It uses a much easier package manager (pacman, from Arch Linux) where package names can be copy/pasted instead of hunted down in a GUI, and they seem to base their PKGBUILDs directly from Arch Linux packages, containing pretty much every MinGW package that's on AUR. It even keeps up to date with GCC, providing GCC 7.3 at the time of this writing, which is the latest version. Cygwin only has something in the 5.x series.

Because of the way this particular article languishes with outdated instructions for a troublesome environment (my only conclusion is that Cygwin just can't be used for building non-Cygwin applications), it doesn't appear anyone ever actually builds via Cygwin on a regular basis and I'll take charge in making MSYS2 the officially recommended mechanism for building on Windows. --chungy (talk) 21:43, 15 February 2018 (UTC)