Re: [Mingw-w64-public] what is x86_64-w64-mingw32 folder?

[Ruben V. B. <van...@gm...>]

2014/1/2 ResQue <res...@gm...>

> Question 1:
> I downloaded MinGW-W64 today:
>
> http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.8.2/threads-win32/seh/x86_64-4.8.2-release-win32-seh-rt_v3-rev1.7z/download
>
> and noticed in the 64bit precompiled version there is a folder called
> "x86_64-w64-mingw32"
>
> it seems to contain a couple of files that are already inside the bin
> folder.
> What is the purpose of these files?
> In what scenario should i be using them over the files with the same
> name inside of the bin folder?
>

These files are internal executables used by binutils and gcc. You should
never call these directly. Ignore them.


>
> Question 2:
> Inside the bin folder there are a collection of files named
>      x86_64-w64-mingw32-c++.exe
>      x86_64-w64-mingw32-g++.exe
>      x86_64-w64-mingw32-gcc-4.8.2.exe
>      x86_64-w64-mingw32-gcc-ar.exe
>      x86_64-w64-mingw32-gcc-nm.exe
>      x86_64-w64-mingw32-gcc-ranlib.exe
>      x86_64-w64-mingw32-gcc.exe
>      x86_64-w64-mingw32-gfortran.exe
> All of these files have a counter part in the same directory, with the
> "x86_64-w64-mingw32-" removed.
> What is the purpose of these files?
> In what scenario should i be using them?
>

These prefixed versions are provided to satisfy autotools configure scripts
and facilitate cross-compiling from e.g. Linux. In the native Windows
toolchain case (as you are describing) they make little sense, but it's
what the GCC build system creates. Just call the non-prefixed versions, as
they are the exact same as their prefixed counterparts.

Cheers,

Ruben


>
> ResQue
>