Building EDuke32 on Windows - Revision history

Hendricks266: /* MinGW-w64/GCC with MSYS2 */

2023-05-29T12:53:03Z

MinGW-w64/GCC with MSYS2

← Older revision		Revision as of 05:53, 29 May 2023
Line 44:		Line 44:
	#Next, we will need to install some additional packages. The ''pacman'' package manager covers all of MSYS2 and is not affected by which shortcut you chose in the previous item.		#Next, we will need to install some additional packages. The ''pacman'' package manager covers all of MSYS2 and is not affected by which shortcut you chose in the previous item.
	#*These packages are necessary to build:		#*These packages are necessary to build:
	#**<code>pacman -S --needed --noconfirm mingw-w64-i686~~-toolchain mingw-w64-~~x86_64-toolchain make nasm yasm</code>		#**<code>pacman -S --needed --noconfirm mingw-w64-{i686,x86_64}-toolchain make nasm yasm</code>
	#*If you would like to use Subversion and Git directly from the MSYS2 shell:		#*If you would like to use Subversion and Git directly from the MSYS2 shell:
	#**<code>pacman -S --needed --noconfirm subversion git</code>		#**<code>pacman -S --needed --noconfirm subversion git</code>
	#*If you would like ''clang'' as an additional compiler option:		#*If you would like ''clang'' as an additional compiler option:
	#**<code>pacman -S --needed --noconfirm mingw-w64-i686~~-clang mingw-w64-~~x86_64-clang</code>		#**<code>pacman -S --needed --noconfirm mingw-w64-{i686,x86_64}-{clang,lld}</code>
	#*EDuke32 includes prebuilt Windows static libraries for all external dependencies with its source code, and therefore installing them through the package manager is superfluous. However, for reference:		#*EDuke32 includes prebuilt Windows static libraries for all external dependencies with its source code, and therefore installing them through the package manager is superfluous. However, for reference:
	#**<code>pacman -S --needed --noconfirm `pacman -Ssq sdl~~` `pacman -Ssq libogg` `pacman -Ssq libvorbis~~` `pacman -Ssq flac` `pacman -Ssq libvpx~~` `pacman -Ssq luajit~~`</code>		#**<code>pacman -S --needed --noconfirm `pacman -Ssq sdl` `pacman -Ssq flac` `pacman -Ssq libvpx`</code>

	You should now be all set.		You should now be all set.

TX: /* MinGW-w64/GCC (Standalone) */ Neither of these issues apply to current versions of MSYS2 anymore

2022-05-30T04:51:29Z

MinGW-w64/GCC (Standalone): Neither of these issues apply to current versions of MSYS2 anymore

← Older revision		Revision as of 21:51, 29 May 2022
Line 79:		Line 79:
	==MinGW-w64/GCC (Standalone)==		==MinGW-w64/GCC (Standalone)==

	MSYS2 has some minor downsides: occasional slowness in the shell and file I/O, and the unchangeable default of using POSIX threading (requiring distribution of libwinpthread-1.dll with your binaries) instead of native Win32 threads. For advanced users seeking the best-quality binaries for distribution, it is possible to build with nothing but a standalone MinGW-w64 toolchain and [[Working with the Windows Command Prompt\|cmd.exe]].		It is also possible to build with nothing but a standalone MinGW-w64 toolchain and [[Working with the Windows Command Prompt\|cmd.exe]].

	===setup===		===setup===

Hendricks266: /* setup */ newer versions of MSYS2 say: :: To complete this update all MSYS2 processes including this terminal will be closed. Confirm to proceed [Y/n]

2020-08-16T06:45:28Z

setup: newer versions of MSYS2 say: :: To complete this update all MSYS2 processes including this terminal will be closed. Confirm to proceed [Y/n]

← Older revision		Revision as of 23:45, 15 August 2020
Line 40:		Line 40:

	#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.		#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.
	#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, press Ctrl+C to dismiss it, then exit the session and open a new one. Alternatively, close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or by using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].
	#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.		#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.
	#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.		#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.

Hendricks266: /* MinGW-w64/GCC (Standalone) */

2020-05-18T04:06:34Z

MinGW-w64/GCC (Standalone)

← Older revision		Revision as of 21:06, 17 May 2020
Line 86:		Line 86:
	====GCC====		====GCC====

	#First, download one or more MinGW-w64 packages. These contain the entire toolchain. For our purposes, Win32 threads are preferred to POSIX threads, and seh (for 64-bit) and dwarf (for 32-bit) exception handling methods are preferred to sjlj.		#First, download [http://www.winlibs.com/ a MinGW-w64 package]. You will generally want Win64 unless you specifically need a 32-bit binary. Recent packages come with clang too.
	#*[http://~~sourceforge~~.~~net~~/~~projects/mingw~~-w64~~/files/Toolchains%20targetting%20Win32/Personal%20Builds/mingw-builds/ Targeting Win32 (i686)~~]
	~~#*[http://sourceforge~~.~~net/projects/mingw~~-~~w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/ Targeting Win64 (x86_64)]~~
	#You are going to want to extract these in an organized fashion. For example:		#You are going to want to extract these in an organized fashion. For example:
	#*<code>C:\MinGW-w64\mingw32\bin\gcc.exe</code>		#*<code>C:\MinGW-w64\mingw32\bin\gcc.exe</code>
Line 94:		Line 92:
	#If you are interested in building 32-bit binaries, also download '''[http://www.nasm.us/ NASM]''' and extract its contents to the i686 bin folder, so nasm.exe is located there.		#If you are interested in building 32-bit binaries, also download '''[http://www.nasm.us/ NASM]''' and extract its contents to the i686 bin folder, so nasm.exe is located there.
	#*<code>C:\MinGW-w64\mingw32\bin\nasm.exe</code>		#*<code>C:\MinGW-w64\mingw32\bin\nasm.exe</code>
	#Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms. You will need ~~to use the included '''mingw32env.cmd''' or '''mingw64env.cmd'''~~ to set up your PATH variables for a session that can use the toolchain you have set up. When building, the executables generated will match the target of whatever compiler is the highest in PATH--no extra make parameters needed.		#Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms. You will need to set up your PATH variables for a session that can use the toolchain you have set up. For example, <code>set PATH=C:\MinGW-w64\mingw64\bin;%PATH%</code>. When building, the executables generated will match the target of whatever compiler is the highest in PATH, with no extra make parameters needed.
	#*Power users can permanently set up their PATH to one or the other toolchain through ''Advanced system settings'' (aka ''sysdm.cpl'') if desired. If you have enabled the "Launch folder windows in a separate process" option in Windows Explorer, you will need to restart explorer.exe (either by terminating and relaunching it in Task Manager, or restarting your computer) for changes made to persistent PATH to take effect in command prompt windows launched from within Explorer.		#*Power users can permanently set up their PATH to one or the other toolchain through ''Advanced system settings'' (aka ''sysdm.cpl'') if desired. If you have enabled the "Launch folder windows in a separate process" option in Windows Explorer, you will need to restart explorer.exe (either by terminating and relaunching it in Task Manager, or restarting your computer) for changes made to persistent PATH to take effect in command prompt windows launched from within Explorer.
	#MinGW-w64 comes with GNU Make, but it is named ''mingw32-make.exe''. If you don't want to type <code>mingw32-make</code> where you would normally type <code>make</code>, feel free to <code>copy mingw32-make.exe make.exe</code>.		#MinGW-w64 comes with GNU Make, but it is named ''mingw32-make.exe''. If you don't want to type <code>mingw32-make</code> where you would normally type <code>make</code>, feel free to <code>copy mingw32-make.exe make.exe</code>.
Line 107:		Line 105:
	====clang====		====clang====

	~~This process should set up a fully working GCC~~. ~~Unfortunately~~, ~~clang is a different story. Recent~~ releases of clang for Windows default to acting as a drop-in replacement for Visual Studio, rather than MinGW. However, for the adventurous:		It is also possible to use mainline releases of LLVM/clang. However, recent releases of clang for Windows default to acting as a drop-in replacement for Visual Studio rather than the preferred GCC as with MinGW-w64. However, for the adventurous:

	#Download [http://releases.llvm.org/download.html clang for Windows].		#Download [http://releases.llvm.org/download.html clang for Windows].
Line 117:		Line 115:
	===building===		===building===

	Open ~~'''mingw32env.cmd''' or '''mingw64env.cmd''' (double-clicking is fine) to start~~ a [[Working with the Windows Command Prompt\|command prompt window]]. Once there, building is the same as with MSYS2, with the exception of using <code>mingw32-make</code> instead of <code>make</code> if you did not copy it.		Open a [[Working with the Windows Command Prompt\|command prompt window]] in the source code's location. Once there, building is the same as with MSYS2, with the exception of using <code>mingw32-make</code> instead of <code>make</code> if you did not copy it.

	In order to allow building in the absence of an ''sh.exe'', the PRETTY_OUTPUT colorful build process message feature provided by EDuke32's Makefile is disabled with this setup. Advanced users can open the ''MSYS2 MSYS'' shortcut, if installed above, or [https://git-scm.com/download/win Git Bash], in combination with manually configuring their Unix-style PATH variable, to get colorful output with a standalone toolchain.		In order to allow building in the absence of an ''sh.exe'', the PRETTY_OUTPUT colorful build process message feature provided by EDuke32's Makefile is disabled with this setup. Advanced users can open the ''MSYS2 MSYS'' shortcut, if installed above, or [https://git-scm.com/download/win Git Bash], in combination with manually configuring their Unix-style PATH variable, to get colorful output with a standalone toolchain.

	[[Category:Distribution documentation]]		[[Category:Distribution documentation]]

Hendricks266: /* setup */

2019-11-25T20:43:07Z

setup

← Older revision		Revision as of 13:43, 25 November 2019
Line 40:		Line 40:

	#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.		#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.
	#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, press Ctrl+C to dismiss it, then exit ~~and~~ the session and open a new one. Alternatively, close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or by using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].		#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, press Ctrl+C to dismiss it, then exit the session and open a new one. Alternatively, close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or by using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].
	#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.		#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.
	#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.		#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.

Hendricks266: /* setup */

2019-11-25T20:42:48Z

setup

← Older revision		Revision as of 13:42, 25 November 2019
Line 40:		Line 40:

	#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.		#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.
	#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, ~~you will need~~ to close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].		#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, press Ctrl+C to dismiss it, then exit and the session and open a new one. Alternatively, close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or by using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].
	#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.		#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.
	#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.		#Try updating all packages with <code>pacman -Syuu</code> to verify you've completed the instructions. If all is well, you should see <code>there is nothing to do</code>. Otherwise, accept the update and repeat until there is nothing further to update.
	#Next, we will need to install some additional packages. The ''pacman'' package manager covers all of MSYS2 and is not affected by which shortcut you chose in the previous item.		#Next, we will need to install some additional packages. The ''pacman'' package manager covers all of MSYS2 and is not affected by which shortcut you chose in the previous item.
	#*These packages are necessary to build:		#*These packages are necessary to build:
	#**<code>pacman -S --needed --noconfirm mingw-w64-i686-toolchain mingw-w64-x86_64-toolchain make nasm</code>		#**<code>pacman -S --needed --noconfirm mingw-w64-i686-toolchain mingw-w64-x86_64-toolchain make nasm yasm</code>
	#*If you would like to use Subversion directly from the MSYS2 shell:		#*If you would like to use Subversion and Git directly from the MSYS2 shell:
	#**<code>pacman -S --needed --noconfirm subversion</code>		#**<code>pacman -S --needed --noconfirm subversion git</code>
	#*If you would like ''clang'' as an additional compiler option:		#*If you would like ''clang'' as an additional compiler option:
	#**<code>pacman -S --needed --noconfirm mingw-w64-i686-clang mingw-w64-x86_64-clang</code>		#**<code>pacman -S --needed --noconfirm mingw-w64-i686-clang mingw-w64-x86_64-clang</code>

Hendricks266: /* MinGW-w64/GCC (Standalone) */

2019-03-07T23:52:15Z

MinGW-w64/GCC (Standalone)

← Older revision		Revision as of 16:52, 7 March 2019
Line 80:		Line 80:
	==MinGW-w64/GCC (Standalone)==		==MinGW-w64/GCC (Standalone)==

	MSYS2 has some minor downsides: occasional slowness in the shell and file I/O, and the unchangeable default of using POSIX threading (requiring distribution of libwinpthread-1.dll with your binaries) instead of native Win32 threads. For advanced users seeking the best-quality binaries for distribution, it is possible to to build with nothing but a standalone MinGW-w64 toolchain and [[Working with the Windows Command Prompt\|cmd.exe]].		MSYS2 has some minor downsides: occasional slowness in the shell and file I/O, and the unchangeable default of using POSIX threading (requiring distribution of libwinpthread-1.dll with your binaries) instead of native Win32 threads. For advanced users seeking the best-quality binaries for distribution, it is possible to build with nothing but a standalone MinGW-w64 toolchain and [[Working with the Windows Command Prompt\|cmd.exe]].

	===setup===		===setup===

Hendricks266: /* building */

2018-11-06T01:18:54Z

building

← Older revision		Revision as of 18:18, 5 November 2018
Line 119:		Line 119:
	Open '''mingw32env.cmd''' or '''mingw64env.cmd''' (double-clicking is fine) to start a [[Working with the Windows Command Prompt\|command prompt window]]. Once there, building is the same as with MSYS2, with the exception of using <code>mingw32-make</code> instead of <code>make</code> if you did not copy it.		Open '''mingw32env.cmd''' or '''mingw64env.cmd''' (double-clicking is fine) to start a [[Working with the Windows Command Prompt\|command prompt window]]. Once there, building is the same as with MSYS2, with the exception of using <code>mingw32-make</code> instead of <code>make</code> if you did not copy it.

	In order to allow building in the absence of an ''sh.exe'', the PRETTY_OUTPUT colorful build process message feature provided by EDuke32's Makefile is disabled with this setup. Advanced users can open the ''MSYS2 MSYS'' shortcut, if installed above, in combination with manually configuring their Unix-style PATH variable, to get colorful output with a standalone toolchain.		In order to allow building in the absence of an ''sh.exe'', the PRETTY_OUTPUT colorful build process message feature provided by EDuke32's Makefile is disabled with this setup. Advanced users can open the ''MSYS2 MSYS'' shortcut, if installed above, or [https://git-scm.com/download/win Git Bash], in combination with manually configuring their Unix-style PATH variable, to get colorful output with a standalone toolchain.

	[[Category:Distribution documentation]]		[[Category:Distribution documentation]]

Hendricks266: /* tips to remember */

2017-12-20T19:35:25Z

tips to remember

← Older revision		Revision as of 12:35, 20 December 2017
Line 34:		Line 34:

	*You can press the middle mouse button to paste text into the MSYS2 terminal, or right-click for more options.		*You can press the middle mouse button to paste text into the MSYS2 terminal, or right-click for more options.
	*You can navigate folders using the <code>cd</code> command (short for "change directory"), or the <code>pushd</code> command, which adds the new path you specify to a stack, allowing you to return to your previous location with <code>popd</code>.		*You can navigate folders using the <code>cd</code> command (short for ''change directory''), or the <code>pushd</code> command, which adds the new path you specify to a stack, allowing you to return to your previous location with <code>popd</code>.
	*Paths use forward slashes (<code>/</code>) instead of backslashes (<code>\</code>) and drive letters take the form <code>/c/</code> instead of <code>C:\</code>, though it will likely understand either way if you put your path in "quotes".		*Paths use forward slashes (<code>/</code>) instead of backslashes (<code>\</code>) and drive letters take the form <code>/c/</code> instead of <code>C:\</code>, though it will likely understand either way if you put your path in <code>"quotes"</code>.

	===setup===		===setup===

Hendricks266 at 00:43, 16 October 2017

2017-10-16T00:43:07Z

← Older revision		Revision as of 17:43, 15 October 2017
Line 30:		Line 30:

	For a more Unix-like style of development, [http://www.msys2.org/ MSYS2] provides a bash shell, native GCC and clang builds, and the ''pacman'' package manager originally from Arch Linux.		For a more Unix-like style of development, [http://www.msys2.org/ MSYS2] provides a bash shell, native GCC and clang builds, and the ''pacman'' package manager originally from Arch Linux.

			===tips to remember===

			*You can press the middle mouse button to paste text into the MSYS2 terminal, or right-click for more options.
			*You can navigate folders using the <code>cd</code> command (short for "change directory"), or the <code>pushd</code> command, which adds the new path you specify to a stack, allowing you to return to your previous location with <code>popd</code>.
			*Paths use forward slashes (<code>/</code>) instead of backslashes (<code>\</code>) and drive letters take the form <code>/c/</code> instead of <code>C:\</code>, though it will likely understand either way if you put your path in "quotes".

	===setup===		===setup===

	#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.		#First, [http://www.msys2.org/ install MSYS2], following the instructions on that page fully. Install whichever architecture matches your computer; both can cross-compile to the other.
	~~#*You can press the middle mouse button to paste text into the MSYS2 terminal, or right-click for more options.~~
	#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, you will need to close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].		#*If you see the prompt <code>warning: terminate MSYS2 without returning to shell and check for updates again</code> during this process, you will need to close ''pacman.exe'', ''bash.exe'', and ''mintty.exe'' in the Task Manager, or using <code>taskkill /f /im <exe></code> from a [[Working with the Windows Command Prompt\|Windows command prompt (cmd.exe)]].
	#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.		#The installer will create three shortcuts in the Start Menu. Ignore '''MSYS2 MSYS'''. Open '''MSYS MinGW (32-bit)''' or '''(64-bit)''' to select which architecture you would like to target while building during the shell session that begins. Unfortunately, one deficiency in MinGW-w64 is that the each of the two targets (32-bit and 64-bit) require their own separate executables, instead of using one binary with the <code>-arch</code> parameter as on other platforms.
Line 51:		Line 56:

	===building===		===building===
	Now that we've got everything together, you can try building EDuke32 and Mapster32. Navigate to the base directory containing [[Acquiring the EDuke32 Source Code\|the EDuke32 source code]], and ~~type:~~		Now that we've got everything together, you can try building EDuke32 and Mapster32. Navigate to the base directory containing [[Acquiring the EDuke32 Source Code\|the EDuke32 source code]], type the following and ''eduke32.exe'' and ''mapster32.exe'' should be created.
	make		make
	''~~eduke32~~.~~exe~~'' and ''~~mapster32~~.~~exe~~'' ~~should be created~~.		For quick testing of changes, it is recommended to build a debug executable, which skips all compiler optimizations for a much faster compile time, and also includes information about the source code called ''debug symbols'' for debugging with GDB. Append ''RELEASE=0'' to the command, like this:
			make RELEASE=0
			You can enable parallelism and build multiple objects at the same time with '-j'. The flag by itself will use the total number of threads available, or you can specify a number, such as '-j2'.
			make RELEASE=0 -j4
	To compile only either the game or the editor, simply give ''make'' the name of the executable, like		To compile only either the game or the editor, simply give ''make'' the name of the executable, like
	make eduke32.exe		make RELEASE=0 -j4 eduke32.exe
	~~To compile a version suitable for later debugging with GDB, append ''RELEASE=0'' to the command, like this:~~
	~~make RELEASE=0~~
	To build with clang, append the setting <code>CLANG=1</code> to your ''make'' invocation.		To build with clang, append the setting <code>CLANG=1</code> to your ''make'' invocation.
	make CLANG=1		make RELEASE=0 -j4 eduke32.exe CLANG=1

	===troubleshooting===		===troubleshooting===