Re: [Mingw-w64-public] To 32 or 64, that is the question :)

2014-06-20 Thread Peter Kennard
On 6/20/2014 10:00 PM, JonY wrote: > I don't know what you mean by config files, but yes, each toolchain > install is independent from each other. It is best not to mix them. > By config files, only that some command line programs like GCC you can specity with a command line argument that it

Re: [Mingw-w64-public] To 32 or 64, that is the question :)

2014-06-20 Thread Peter Kennard
tion fully. Also, the two installs can't overlay each other and both be resident in the same install directory. One must install both bitness versions separately into separate install directories and keep the two wholly separate. Thanks. PK On 6/20/2014 7:11 AM, Koehne Kai wrote: >

Re: [Mingw-w64-public] To 32 or 64, that is the question :)

2014-06-20 Thread Peter Kennard
set should produce the identical target results if a build script is run for a particular source package. Thanks. PK On 6/20/2014 5:08 AM, JonY wrote: On 6/20/2014 08:18, Peter Kennard wrote: as the unified installer has options for 64 and 32 bit installs. I assume the 64 bit install

[Mingw-w64-public] To 32 or 64, that is the question :)

2014-06-19 Thread Peter Kennard
as the unified installer has options for 64 and 32 bit installs. I assume the 64 bit install will not run on a 32 bit machine or a 32 bit OS install. Does which install is chosen ONLY effect the actual running of the tools themselves on the HOST machine or does it have any influence on what the