Ok thanks, so the below is really not a fully correct assumption.
> So I assume from your answer the *only* difference in the two installs
> is the host machine the tools run on, Meaning all sets of static libs
> and the other resources the compiler and other tools need to build all
> targets specified by the command line arguments and config files (and
> thus the build scripts using them) are present in both the 32 bit and
> 64 bit install.
>
> So either install if the paths are correctly set should produce the
> identical target results if a build script is run for a particular
> source package.
That is though the tool chains will output any target that is
*100%*fully*specified*. The default values for configuration files and
command line arguments are different:
the 32 bit install defaulting to 32 bit, and,
the 64 bit install defaulting to 64 bit optimal configurations.
So in the case of a module provided by someone else one should use the
64 bit version to build the 64 bit targets, and the 32 bit version to
build the 32 bit targets unless one is 100% sure that the supplied build
scripts specify each target's configuration 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:
>> -----Original Message-----
>> From: Peter Kennard [mailto:[email protected]]
>> Sent: Friday, June 20, 2014 2:19 AM
>> To: [email protected]
>> Subject: [Mingw-w64-public] To 32 or 64, that is the question :)
>>
>> 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.
>>
> Yes (unless you're running it inside in an emulator ;)
>
>
>> 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
>> tools build and link - ie: what compile targets are built and what libraries
>> are
>> present and/or linked with?
>>
> The bitness in the installer first of all says how the _toolchain_ is
> compiled.
> By default the toolchain will also generate code for the same bitness (
> 32 bit gcc toolchain will generate 32 bit applications, a 64 bit gcc
> toolchain will generate
> 64 bit applications), but gcc is also able to work as a cross-compiler (-m64
> -m32 gcc arguments).
> I don't think all toolchains support this though, you'd have to check. Last
> time I tried the mingw-builds
> toolchains supported this.
>
>
>> Or is what target is built 100% selected by the build scripts coded to use
>> the
>> tools?
>>
>> Related, Will both versions run underneath 32 bit shells or interpreters like
>> ant, make, or ruby that may be 32 bit executables themselves yet running on
>> a 64 bit OS?
>>
> Yes.
>
>
>> If there is a difference in the output targets, can one install BOTH
>> versions in
>> the same install directory (ie: can then unzip on either a
>> 32 or 64 bit machine and the proper libraries/dlls for runtime are lanuched
>> by
>> the master .exe or does one have two installs and select which one to use by
>> setting the path appropriately?
>>
> The master.exe determines the bitness. You can't AFAIK mix 32 bit libraries
> with 64 bit executables under Windows, or the other way round.
>
>
>> Hope this isn't too messy a set of questions :) I just didn't see any
>> explicit
>> mention of it.
>>
> Regards
>
> Kai
>
> ------------------------------------------------------------------------------
> HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
> Find What Matters Most in Your Big Data with HPCC Systems
> Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
> Leverages Graph Analysis for Fast Processing& Easy Data Exploration
> http://p.sf.net/sfu/hpccsystems
> _______________________________________________
> Mingw-w64-public mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
>
>
------------------------------------------------------------------------------
HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions
Find What Matters Most in Your Big Data with HPCC Systems
Open Source. Fast. Scalable. Simple. Ideal for Dirty Data.
Leverages Graph Analysis for Fast Processing & Easy Data Exploration
http://p.sf.net/sfu/hpccsystems
_______________________________________________
Mingw-w64-public mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
