On 1/11/2014 22:24, Ruben Van Boxem wrote: >> >> 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. >
You have it backwards. While it is the norm to assume that Windows is downright incapable of doing anything right at all, cross compiling is actually possible there, even without autotools, just call the prefixed version and you are set. No guessing games about what "gcc" is producing for output.
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________ Mingw-w64-public mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
