➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2007-12-05 18:28 by christian.heimes, last changed 2022-04-11 14:56 by admin. This issue is now closed.
| Messages (2) | |||
|---|---|---|---|
| msg58224 - (view) | Author: Christian Heimes (christian.heimes) *  |
Date: 2007-12-05 18:28 | |
In VS 2008 the x64 platform doesn't define the _WIN64 macro. The _WIN64 macro defines the MS_WIN64 macro which sets several other macros and changes some variables in pyconfig.h. Question: Should we enforce MS_WIN64 for the x64 platform although _WIN64 is not defined? Question 2: WHY THE H... is the _WIN64 macro not defined? I'm googling now. |
|||
| msg58232 - (view) | Author: Christian Heimes (christian.heimes) * |
Date: 2007-12-05 21:59 | |
Sorry guys, it was false alarm. From r59375: The macros _WIN32, _WIN64 and _M_X64 are defined by the compiler. The VS 2008 IDE doesn't know about (some) of the macros and can display wrong information. In my case a section #ifdef _WIN64 was grayed out although the platform was x64. I've added the macros to pyproject.vsprops and x64.vsprops to avoid future confusion. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:56:28 | admin | set | github: 45899 |
| 2008-01-06 22:29:44 | admin | set | keywords:
- py3k versions: Python 3.0 |
| 2007-12-05 21:59:00 | christian.heimes | set | status: open -> closed resolution: not a bug messages: + msg58232 |
| 2007-12-05 18:28:26 | christian.heimes | create | |