Setting up a MinGW-w64 build environment - Revision history

Jpye: /* Switchable 32- and 64-bit modes */

2014-04-19T22:23:22Z

Switchable 32- and 64-bit modes

← Older revision		Revision as of 22:23, 19 April 2014
Line 65:		Line 65:
	*** '''<tt>64\</tt>''' (the 64-bit compiler and all our 64-bit compiled-and-installed libraries will live here)		*** '''<tt>64\</tt>''' (the 64-bit compiler and all our 64-bit compiled-and-installed libraries will live here)
	*** '''<tt>32\</tt>''' (the <tt>mingw-get</tt> binary will already be inside here, as well as the 32-bit compiler if we install it later)		*** '''<tt>32\</tt>''' (the <tt>mingw-get</tt> binary will already be inside here, as well as the 32-bit compiler if we install it later)
	** '''<tt>msys\</tt>''' (the MSYS environment, and loads of useful non-compiler tools can be installed here, but they shouldn't have any binary dependencies in <tt>c:\mingw\64</tt> or <tt>c:\mingw\32</tt>, or things will get broken!)		*** '''<tt>msys\</tt>''' (the MSYS environment, and loads of useful non-compiler tools can be installed here, but they shouldn't have any binary dependencies in <tt>c:\mingw\64</tt> or <tt>c:\mingw\32</tt>, or things will get broken!)

	In principle, all we need to do to switch between the 64-bit and 32-bit build environments is to edit the text file <tt>/etc/fstab</tt> (changing '32' to '64' or vice versa), then reload MSYS. In other words, if you want to now switch to 64-bit mode, you would modify <tt>/etc/fstab</tt> to read		In principle, all we need to do to switch between the 64-bit and 32-bit build environments is to edit the text file <tt>/etc/fstab</tt> (changing '32' to '64' or vice versa), then reload MSYS. In other words, if you want to now switch to 64-bit mode, you would modify <tt>/etc/fstab</tt> to read

Jpye: /* First steps */

2014-01-10T02:58:36Z

First steps

← Older revision		Revision as of 02:58, 10 January 2014
Line 26:		Line 26:
	* Download and install the [https://projects.gnome.org/gedit/ gedit] text editor for Windows. We used this package: [http://ftp.gnome.org/pub/GNOME/binaries/win32/gedit/2.30/gedit-setup-2.30.1-1.exe gedit-setup-2.30.1-1.exe] (32-bit).		* Download and install the [https://projects.gnome.org/gedit/ gedit] text editor for Windows. We used this package: [http://ftp.gnome.org/pub/GNOME/binaries/win32/gedit/2.30/gedit-setup-2.30.1-1.exe gedit-setup-2.30.1-1.exe] (32-bit).
	** To ensure that Windows knows that gedit is a text editor, use Windows Explorer to navigate to <tt>c:\Program Files (x86)\gedit\share\doc</tt> and right-click on README, and select Open. In the dialog, click Browse, then select <tt>c:\Program Files (x86)\gedit\bin\gedit.exe</tt>, and click OK to open the file. This will ensure that <tt>gedit</tt> appears in the list of editors for other text files you want to open in future.		** To ensure that Windows knows that gedit is a text editor, use Windows Explorer to navigate to <tt>c:\Program Files (x86)\gedit\share\doc</tt> and right-click on README, and select Open. In the dialog, click Browse, then select <tt>c:\Program Files (x86)\gedit\bin\gedit.exe</tt>, and click OK to open the file. This will ensure that <tt>gedit</tt> appears in the list of editors for other text files you want to open in future.
			** Note: be aware that some other installers may modify your system PATH in a way that causes gedit to break. If you start to get errors when launching gedit, this is probably what has happened.
	* Download and install NSIS. We used [http://prdownloads.sourceforge.net/nsis/nsis-2.46-setup.exe?download nsis-2.46-setup.exe]. You can tell the installer ''not'' to actually run NSIS, no need for that. If you will be building ASCEND, you should also download the [http://nsis.sourceforge.net/Inetc_plug-in Inetc] plugin and put the DLL from that zip file into the <tt>Plugins</tt> subdirectory where you installed NSIS.		* Download and install NSIS. We used [http://prdownloads.sourceforge.net/nsis/nsis-2.46-setup.exe?download nsis-2.46-setup.exe]. You can tell the installer ''not'' to actually run NSIS, no need for that. If you will be building ASCEND, you should also download the [http://nsis.sourceforge.net/Inetc_plug-in Inetc] plugin and put the DLL from that zip file into the <tt>Plugins</tt> subdirectory where you installed NSIS.

Jpye: /* MinGW-w64 */

2013-12-05T02:40:06Z

MinGW-w64

← Older revision		Revision as of 02:40, 5 December 2013
Line 109:		Line 109:

	''TODO'': add instructions for also installing the 32-bit compilers, and instructions for getting things working on a 32-bit Windows system.		''TODO'': add instructions for also installing the 32-bit compilers, and instructions for getting things working on a 32-bit Windows system.

			'''Note''': the above TDM 64-bit installer does not install a fortran compiler, but a fortran compiler is required for building ASCEND. The alternative appears to be to use the latest [http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/tdm-gcc-webdl.exe/download tdm-gcc-webdl.exe] downloader-installer. Select all options, but select not to install to PATH.

	== MinGW 32-bit compilers ''(optional)'' ==		== MinGW 32-bit compilers ''(optional)'' ==

Jpye: /* MinGW-w64 */

2013-12-05T02:27:20Z

MinGW-w64

← Older revision		Revision as of 02:27, 5 December 2013
Line 77:		Line 77:

	* Download the TDM-GCC 'MinGW-w64 sjlj' installer for from [http://tdm-gcc.tdragon.net/download this page]. We used [http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/tdm64-gcc-4.7.1-3.exe/download tdm64-gcc-4.7.1-3.exe].		* Download the TDM-GCC 'MinGW-w64 sjlj' installer for from [http://tdm-gcc.tdragon.net/download this page]. We used [http://sourceforge.net/projects/tdm-gcc/files/TDM-GCC%20Installer/tdm64-gcc-4.7.1-3.exe/download tdm64-gcc-4.7.1-3.exe].
	* Install the TDM-GCC package into the directory <tt>c:\mingw\64</tt>, selecting to install '''all''' components.		* Install the TDM-GCC package into the directory <tt>c:\mingw\64</tt>, selecting to install '''all''' components. Select '''not''' to add MinGW-w64 to the <tt>PATH</tt>.
	* After the installer completes, use the Start menu, right-click on 'Computer', select 'Properties' then 'Advanced Systems Settings' then 'Advanced' tab, click button 'Environment variables'. Under system variables, edit the variable named <tt>PATH</tt> and from then end of the path, ''remove'' <tt>c:\mingw\64\bin</tt>. We ''don't'' want this in the path because it messes with gedit, and will also cause confusion when running 32-bit compilers.		* After the installer completes, use the Start menu, right-click on 'Computer', select 'Properties' then 'Advanced Systems Settings' then 'Advanced' tab, click button 'Environment variables'. Under system variables, edit the variable named <tt>PATH</tt> and from then end of the path, ''remove'' <tt>c:\mingw\64\bin</tt>. We ''don't'' want this in the path because it messes with gedit, and will also cause confusion when running 32-bit compilers.
	* Open the MSYS shell (make sure you are in 64-bit mode, as mentioned above) by double-clicking your new desktop shortcut, and type <tt>gcc --version</tt>. You should see		* Open the MSYS shell (make sure you are in 64-bit mode, as mentioned above) by double-clicking your new desktop shortcut, and type <tt>gcc --version</tt>. You should see

Jpye: /* MinGW 32-bit compilers (optional) */

2013-12-04T04:38:24Z

MinGW 32-bit compilers (optional)

← Older revision		Revision as of 04:38, 4 December 2013
Line 124:		Line 124:
	And you should see output that starts with <tt>mingw32</tt>, confirming you have the 32-bit compiler running.		And you should see output that starts with <tt>mingw32</tt>, confirming you have the 32-bit compiler running.

	Note, due to current [http://sourceforge.net/p/mingw/bugs/1950/ bug 1950] in MinGW (Dec 2013), you may need to downgrade 'msys-core-bin' package to version 1.0.17 to avoid problems with parallel builds, eg <tt>make -j4</tt>. The necessary command is:		Note, due to current [http://sourceforge.net/p/mingw/bugs/1950/ bug 1950] in MinGW (Dec 2013), you may need to downgrade 'msys-core-bin' package to version 1.0.17 to avoid problems with parallel builds, eg <tt>make -j4</tt>. The necessary command which should probably be run from an standard Windows command prompt, is
			cd c:\mingw\32\bin
	mingw-get upgrade msys-core-bin=1.0.17-1		mingw-get upgrade msys-core-bin=1.0.17-1

Jpye: /* MinGW 32-bit compilers (optional) */

2013-12-04T04:33:53Z

MinGW 32-bit compilers (optional)

← Older revision		Revision as of 04:33, 4 December 2013
Line 123:		Line 123:

	And you should see output that starts with <tt>mingw32</tt>, confirming you have the 32-bit compiler running.		And you should see output that starts with <tt>mingw32</tt>, confirming you have the 32-bit compiler running.

			Note, due to current [http://sourceforge.net/p/mingw/bugs/1950/ bug 1950] in MinGW (Dec 2013), you may need to downgrade 'msys-core-bin' package to version 1.0.17 to avoid problems with parallel builds, eg <tt>make -j4</tt>. The necessary command is:
			mingw-get upgrade msys-core-bin=1.0.17-1

	== SCons ==		== SCons ==

Jpye: /* MSYS */

2013-12-04T04:05:46Z

MSYS

← Older revision		Revision as of 04:05, 4 December 2013
Line 35:		Line 35:
	** Select to install MinGW to the directory <tt>c:\MinGW\32</tt> (this is '''not''' the default location)		** Select to install MinGW to the directory <tt>c:\MinGW\32</tt> (this is '''not''' the default location)
	** Select '''not''' to install the graphical user interface		** Select '''not''' to install the graphical user interface
	[[Image:mingw-get-setup-0.6b.png\|thumb\|~~500px~~\|none\|Screenshot of MinGW-get-setup showing selected installation options]]		[[Image:mingw-get-setup-0.6b.png\|thumb\|400px\|none\|Screenshot of MinGW-get-setup showing selected installation options]]
	* Open gedit and edit the file <tt>c:\mingw\32\var\lib\mingw-get\data\profile.xml</tt> and replace the entire contents of the file with the following text:		* Open gedit and edit the file <tt>c:\mingw\32\var\lib\mingw-get\data\profile.xml</tt> and replace the entire contents of the file with the following text:
	<source lang=xml>		<source lang=xml>

Jpye: /* MSYS */

2013-12-04T04:05:17Z

MSYS

← Older revision		Revision as of 04:05, 4 December 2013
Line 35:		Line 35:
	** Select to install MinGW to the directory <tt>c:\MinGW\32</tt> (this is '''not''' the default location)		** Select to install MinGW to the directory <tt>c:\MinGW\32</tt> (this is '''not''' the default location)
	** Select '''not''' to install the graphical user interface		** Select '''not''' to install the graphical user interface
			[[Image:mingw-get-setup-0.6b.png\|thumb\|500px\|none\|Screenshot of MinGW-get-setup showing selected installation options]]
	* Open gedit and edit the file <tt>c:\mingw\32\var\lib\mingw-get\data\profile.xml</tt> and replace the entire contents of the file with the following text:		* Open gedit and edit the file <tt>c:\mingw\32\var\lib\mingw-get\data\profile.xml</tt> and replace the entire contents of the file with the following text:
	<source lang=xml>		<source lang=xml>

Jpye: /* Switchable 32- and 64-bit modes */

2013-12-04T03:55:44Z

Switchable 32- and 64-bit modes

← Older revision		Revision as of 03:55, 4 December 2013
Line 69:		Line 69:
	c:/mingw/64 /mingw		c:/mingw/64 /mingw

	After making this change, be sure to close and re-open your MinGW/MSYS command window (re-open it using the MSYS icon that you created on your desktop)		After making this change, be sure to close and re-open your MinGW/MSYS command window (re-open it using the MSYS icon that you created on your desktop).

	== MinGW-w64 ==		== MinGW-w64 ==

Jpye: /* Usage tips */

2013-12-04T03:52:13Z

Usage tips

← Older revision		Revision as of 03:52, 4 December 2013
Line 271:		Line 271:
	This will have the result that libraries and new tools will be installed into <tt>c:\mingw\64</tt>.		This will have the result that libraries and new tools will be installed into <tt>c:\mingw\64</tt>.

	If you ever want to switch building 32-bit code, ~~and you followed~~ the ~~optional~~ 32-~~bit steps in the above, then you simply edit <tt>c:\mingw\msys\etc\fstab</tt>~~ and ~~change~~		If you ever want to switch building 32-bit code, recall the instructions above about [[#Switchable 32- and 64-bit modes]]. This re-routes "/mingw" to your 64-bit or 32-bit compiler and libraries according to which setting to you choose. Then, the 'if' statement in the <tt>.profile</tt> file above takes care of replacing 64-bit stuff with the 32-bit alternatives. This approach also has the result that, when running <tt>./configure</tt> scripts, there is usually no need to add the <tt>--build</tt> flag to specify the 32- or 64-bit build architecture, as only one compiler will be visible/accessible at any one time, anyway.
	~~c:/mingw/~~64 /mingw
	to
	~~c:/mingw/~~32 ~~/mingw~~
	~~The~~ 'if' statement in the <tt>.profile</tt> file above ~~will take~~ care of replacing 64-bit stuff with the 32-bit alternatives. ~~Also~~, when running <tt>./configure</tt> scripts, there is usually no need to add the <tt>--build</tt> flag ~~for~~ 32-bit ~~builds~~.

	== Example of building a simple program ==		== Example of building a simple program ==