Thanks for noticing - I actually waited until I got the notification that registration was successful after replying to the verification message - mabe a few minutes later.

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.

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 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 
tools build and link - ie: what compile targets are built and what 
libraries are present and/or linked with?

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?

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?

Hope this isn't too messy a set of questions :)  I just didn't see any 
explicit mention of it.

    
I don't understand the questions, are you trying to use multilib builds?

There are cross compile builds of various imaginable combinations that
will fit your needs. make isn't architecture specific, it just runs
commands.



  
------------------------------------------------------------------------------ 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 Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public