| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 20/04/16 02:22 PM, M. J. Everitt wrote: |
| 5 |
> On 20/04/16 19:17, Mike Frysinger wrote: |
| 6 |
>> agreed ... we have kernel_Winnt & elibc_Winnt already. i |
| 7 |
>> think those represent a mingw environment (vs a cygwin env). |
| 8 |
> Surely 'winnt' is a somewhat out-of-date and potentially |
| 9 |
> confusing flag? Can't we migrate to a win32 and win64 as |
| 10 |
> pertaining to current/recent architectures, and directly relating |
| 11 |
> to mingw32 and mingw64 or such-like?! |
| 12 |
> |
| 13 |
> Sooner or later win32 is going to be EOL (as the operating |
| 14 |
> systems themselves soon will be) ... |
| 15 |
> |
| 16 |
|
| 17 |
kernel_Winnt may seem old but it's accurate in comparison with |
| 18 |
kernel_DOS, which would be its predecessor if we had ever attempted |
| 19 |
to support it -- the executable is still NTKRNL*.exe or NTOSKRNL.exe |
| 20 |
after all, right? |
| 21 |
|
| 22 |
Recall this isn't the ARCH, which can still be either x86 or amd64 |
| 23 |
(ie x86_64). |
| 24 |
|
| 25 |
The win32 flag I was proposing here was relating to the UI toolkit, |
| 26 |
which is likely (i'm guessing) called win32 for legacy reasons |
| 27 |
rather than explicitly being 32bit, given I expect the 64bit toolkit |
| 28 |
has more or less the same API -- again, not 32bit-windows vs |
| 29 |
64-bit-windows related. |
| 30 |
|
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2 |
| 33 |
|
| 34 |
iF4EAREIAAYFAlcXzvUACgkQAJxUfCtlWe2ezQEAyWMp3J7msrHqQbqZH/Ww1bXe |
| 35 |
pXY0rkEcC0nW7nq6TiUA/Ry56nWOGVobygHia+4bP7b9fomnPha39GdLLZyvafS5 |
| 36 |
=SEOj |
| 37 |
-----END PGP SIGNATURE----- |
Archives