-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Mark Hammond wrote:
>> At 04:00 PM 7/18/2007 +1000, Mark Hammond wrote:
>>> This will result in both the final version of most bdist_*
>> installations
>>> having the architecture in the filename.  It also has the
>> nice side effect
>>> of having the temp directories used by these commands include the
>>> architecture in their names, meaning its possible to build
>> multiple Windows
>>> architectures from the same build tree, although that is not
>> the primary
>>> motivation.
>> I presume the intention of this is to have it end up as either
>> 'win32' or 'win64', yes?
> 
> Probably 'win32', 'amd64' or 'itanium' - I'm not worried about the specific
> strings, but there would need to be different ones for each of the 64bit
> architectures.

Why would you use processor type IDs to indicate Windows-specifc
platforms?  Lots of systems running on AMD64 boxen don't run windows
(can't say "lots" and "Itanium" in the same sentence, I guess, but I
know for a fact that OpenVMS is running on Itanium, at least).


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          [EMAIL PROTECTED]
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD4DBQFGnqpU+gerLs4ltQ4RAj5PAJ4jKxm7Lqxx9hwXRaRZl69CLysQ6ACVEKAb
ql/iXfN18/e9wmdYWKxnAQ==
=8r02
-----END PGP SIGNATURE-----

_______________________________________________
Distutils-SIG maillist  -  Distutils-SIG@python.org
http://mail.python.org/mailman/listinfo/distutils-sig

Reply via email to