Home | History | Annotate | Download | only in Python-2.7.3

Lines Matching full:msvc

10 +  dnl To be compatible with MSVC build.
115 +# For debug versions MSVC build prepend suffix by '_d'.
154 + #MSVC in-compatable storage layout for bitfields in structures (Roumen has -mms-bitfields)
488 +# Note MSVC build use Python/dtoa.c, but I could not find any reason
511 + # Some MSVC runtimes don't preserve zero sign.
523 +dnl MSVC build PC/pyconfig.h define HAVE_DECL_ISINF but it is useless
526 +dnl For mingw to keep compatibility with MSVC build we will define
750 + here for Py_IS_INFINITY we define same as for MSVC build.
803 + So the question is "Separate SDKs" required for w2k in MSVC build ?
819 + in _math.h but as MSVC don't define them we will undefine HAVE_XXX
820 + too to use _Py_* replacements same as MSVC build .
838 + MSVC windows port is handled in PC/pyconfig.h.
886 + # and MSVC. It is addressed in GCC issue #36834.
900 + # and MSVC. It is addressed in GCC issue #36834.
918 """Return the version of MSVC that was used to build Python.
983 # pyconfig.h that MSVC groks. The other Windows compilers all seem
1021 """Include the appropriate MSVC runtime library if Python was built
1022 with MSVC 7.0 or later.
1030 + # Issue: for MSVC compiler we can get the version and from version
1485 + /* FIXME: for stdcall decorated export functions MSVC compiler add
1732 + * To be compatible with MSVC build we has to undef some defines.
1917 + * Why MSVC builds don't include it ?
2212 + * This is what MSVC build do - it is build and packed
2655 + # NOTE: MSVC build alwais include _md5 and _sha modules