How To Install Mingw 64 Bit Windows 10

Unfortunately, but equally with the 64-bit installation to a higher place, the hardest part is configuring Windows to use the compiler. If you are having problems, it is probable because yous oasis't set up up things properly after the installation.

The rest of this guide assumes that you installed the compiler to c:\mingw32 during the installation.

Currently, when you type g++ from the command line, you will run the 64-bit version of the MinGW one thousand++ compiler. You want to continue to do that. To run the 32-flake version, y'all will need to create a batch file chosen g++32.bat and put it in your PATH somewhere. (You should have created a C:\utils directory on your reckoner to put your add-on programs. This directory should be the get-go directory in your PATH.) The contents of the batch file should wait like this:

:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: : This batch file only handles xx options for the compiler. This should : be sufficient. You can figure out how to add together more than, if necessary. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: @repeat off  fix /a count=1  :BEGIN if "%i"=="" goto Terminate set up arg%count%=%ane shift set /a count=%count%+ane goto BEGIN  :End c:\mingw32\mingw32\bin\thou++.exe %arg1% %arg2% %arg3% %arg4% %arg5% %arg6% %arg7% %arg8% ^ %arg9% %arg10% %arg11% %arg12% %arg13% %arg14% %arg15% %arg16% ^ %arg17% %arg18% %arg19% %arg20%  set up arg1= set arg2= set arg3= ready arg4= set arg5= set arg6= set arg7= set arg8= set arg9= fix arg10= prepare arg11= set arg12= gear up arg13= set arg14= set arg15= fix arg16= ready arg17= set arg18= set arg19= set arg20=        

Yous can create the batch file with whatever text editor (east.g. notepad++) or, yous tin download the batch file hither: yard++32.bat (recommended). You need to download this file, not click on it and run information technology (the default in some versions of Windows). There is also a batch file for gcc here: gcc32.bat. Use this to compile 32-flake C programs.

One time yous've downloaded the batch to (or created information technology in) some directory in your PATH, you can cheque that it'due south correct by typing this from any directory:

thou++32 --version          

If everything was setup properly, you should run into this bulletin in the panel:

chiliad++.exe (i686-posix-dwarf-rev1, Built by MinGW-W64 project) seven.1.0 Copyright (C) 2017 Complimentary Software Foundation, Inc. This is free software; see the source for copying conditions.  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A Particular PURPOSE.          

Now, when building 32-bit programs, you type g++32 instead of thou++. For example, to build a 64-bit program (presume all of the usual command line options)

            g++            file1.cpp file2.cpp file3.cpp -o prog64.exe          

To build a 32-bit program:

            g++32            file1.cpp file2.cpp file3.cpp -o prog32.exe          

IMPORTANT NOTE #one:

When running the executable program, if you get an mistake saying something like:

"The programme can't showtime because <some_dll_file>" is missing from your reckoner..."

or

"The application was unable to commencement correctly (0xc000007b)..."

then you lot volition need to put the bin directory of the 32-fleck MinGW compiler at the end of your PATH. If you installed information technology to the location recommended in these notes, that directory is

C:\mingw32\mingw32\bin

. The name of the missing DLL file may be something similar

libwinpthread-1.dll

, or

libgcc_s_dw2-1.dll

, or another file.

Note: If y'all put the bin directory somewhere other than the terminate of your PATH, it may interfere with your 64-bit compiler causing it to no longer piece of work.

Important Notation #2:

When running the executable program, if you get an error bulletin that looks like this:

And so you need to statically link the executable. Add this option (in bold) to the control line:

g++32 file1.cpp file2.cpp file3.cpp -o prog32.exe -static

This will make the executable much bigger, but it should avoid the mistake.

This is also trivial to override the compiler in your makefile. If your makefile has a macro like this (which all of your makefiles should have)

CC=g++          

You can simply run make like this:

make CC=g++32.bat          

and it will build a 32-flake executable instead of a 64-bit executable. Note that you must provide the .bat file extension for the makefile.

To verify that your plan is really a 32-fleck executable, use the file control (role of the Cygwin utilities). For instance, this command:

            file            prog32.exe prog64.exe          

will display this in the console:

prog32.exe: PE32 executable (console) Intel 80386, for MS Windows prog64.exe: PE32+ executable (console) x86-64, for MS Windows          

PE32 is a 32-bit (Intel 80386) executable.
PE32+ is a 64-bit (x86-64) executable.

Notation to Linux and Mac users: Building a 32-bit program under Mac or Linux is footling. You but add a -m32 pick to the control line. For example:

thou++ -Wall -Wextra -ansi -pedantic            -m32            foo.c          

That'south it!

Incidentally, to create a 64-bit executable, you can use -m64, but since this is the default, y'all don't have to provide it to the compiler. If y'all run the file command on Linux, you lot would see something like this (with possibly more than information displayed)

prog32: ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV) prog64: ELF 64-bit LSB  executable, x86-64, version 1 (SYSV)          

And on macOS you would encounter this:

prog32: Mach-O executable i386 prog64: Mach-O 64-bit executable x86_64          

---

Source: https://azrael.digipen.edu/~mmead/www/public/mingw/

Posted by: floresloguithat36.blogspot.com

Share this post