Mirror
/
cpython
mirror of https://github.com/python/cpython
4
1
Fork 0
Code Issues Releases Wiki Activity
cpython/PCbuild/_testcapi.vcxproj

143 lines
6.1 KiB
XML
Raw Normal View History

Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<?xml version="1.0" encoding="utf-8"?>
<Project DefaultTargets="Build" ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
<ItemGroup Label="ProjectConfigurations">
bpo-35976: Enable Windows projects to build with platform ARM32 (GH-11825) This change adds the necessary items to the build projects to avoid erroring out right at the start. It does not add _support_ for targeting Windows on ARM32, but is a necessary prerequisite for adding it.
2019-02-14 12:31:30 -04:00
<ProjectConfiguration Include="Debug|ARM">
<Configuration>Debug</Configuration>
<Platform>ARM</Platform>
</ProjectConfiguration>
bpo-36941: Windows build changes for Windows ARM64 (GH-13365)
2019-05-17 14:07:24 -03:00
<ProjectConfiguration Include="Debug|ARM64">
<Configuration>Debug</Configuration>
<Platform>ARM64</Platform>
</ProjectConfiguration>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ProjectConfiguration Include="Debug|Win32">
<Configuration>Debug</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Debug|x64">
<Configuration>Debug</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
bpo-35976: Enable Windows projects to build with platform ARM32 (GH-11825) This change adds the necessary items to the build projects to avoid erroring out right at the start. It does not add _support_ for targeting Windows on ARM32, but is a necessary prerequisite for adding it.
2019-02-14 12:31:30 -04:00
<ProjectConfiguration Include="PGInstrument|ARM">
<Configuration>PGInstrument</Configuration>
<Platform>ARM</Platform>
</ProjectConfiguration>
bpo-36941: Windows build changes for Windows ARM64 (GH-13365)
2019-05-17 14:07:24 -03:00
<ProjectConfiguration Include="PGInstrument|ARM64">
<Configuration>PGInstrument</Configuration>
<Platform>ARM64</Platform>
</ProjectConfiguration>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ProjectConfiguration Include="PGInstrument|Win32">
<Configuration>PGInstrument</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="PGInstrument|x64">
<Configuration>PGInstrument</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
bpo-35976: Enable Windows projects to build with platform ARM32 (GH-11825) This change adds the necessary items to the build projects to avoid erroring out right at the start. It does not add _support_ for targeting Windows on ARM32, but is a necessary prerequisite for adding it.
2019-02-14 12:31:30 -04:00
<ProjectConfiguration Include="PGUpdate|ARM">
<Configuration>PGUpdate</Configuration>
<Platform>ARM</Platform>
</ProjectConfiguration>
bpo-36941: Windows build changes for Windows ARM64 (GH-13365)
2019-05-17 14:07:24 -03:00
<ProjectConfiguration Include="PGUpdate|ARM64">
<Configuration>PGUpdate</Configuration>
<Platform>ARM64</Platform>
</ProjectConfiguration>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ProjectConfiguration Include="PGUpdate|Win32">
<Configuration>PGUpdate</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="PGUpdate|x64">
<Configuration>PGUpdate</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
bpo-35976: Enable Windows projects to build with platform ARM32 (GH-11825) This change adds the necessary items to the build projects to avoid erroring out right at the start. It does not add _support_ for targeting Windows on ARM32, but is a necessary prerequisite for adding it.
2019-02-14 12:31:30 -04:00
<ProjectConfiguration Include="Release|ARM">
<Configuration>Release</Configuration>
<Platform>ARM</Platform>
</ProjectConfiguration>
bpo-36941: Windows build changes for Windows ARM64 (GH-13365)
2019-05-17 14:07:24 -03:00
<ProjectConfiguration Include="Release|ARM64">
<Configuration>Release</Configuration>
<Platform>ARM64</Platform>
</ProjectConfiguration>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ProjectConfiguration Include="Release|Win32">
<Configuration>Release</Configuration>
<Platform>Win32</Platform>
</ProjectConfiguration>
<ProjectConfiguration Include="Release|x64">
<Configuration>Release</Configuration>
<Platform>x64</Platform>
</ProjectConfiguration>
</ItemGroup>
<PropertyGroup Label="Globals">
<ProjectGuid>{6901D91C-6E48-4BB7-9FEC-700C8131DF1D}</ProjectGuid>
<RootNamespace>_testcapi</RootNamespace>
<Keyword>Win32Proj</Keyword>
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<SupportPGO>false</SupportPGO>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
</PropertyGroup>
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<Import Project="python.props" />
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.Default.props" />
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<PropertyGroup Label="Configuration">
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ConfigurationType>DynamicLibrary</ConfigurationType>
<CharacterSet>NotSet</CharacterSet>
</PropertyGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.props" />
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<PropertyGroup>
gh-112984 Update Windows build and installer for free-threaded builds (GH-113129)
2024-01-17 17:52:23 -04:00
<TargetExt>$(PyStdlibPydExt)</TargetExt>
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
</PropertyGroup>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ImportGroup Label="ExtensionSettings">
</ImportGroup>
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<ImportGroup Label="PropertySheets">
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<Import Project="$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props" Condition="exists('$(UserRootDir)\Microsoft.Cpp.$(Platform).user.props')" Label="LocalAppDataPlatform" />
Issue #22919: Windows build updated to support VC 14.0 (Visual Studio 2015), which will be used for the official 3.5 release.
2014-11-22 16:54:57 -04:00
<Import Project="pyproject.props" />
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
</ImportGroup>
<PropertyGroup Label="UserMacros" />
<PropertyGroup>
<_ProjectFileVersion>10.0.30319.1</_ProjectFileVersion>
</PropertyGroup>
<ItemGroup>
<ClCompile Include="..\Modules\_testcapimodule.c" />
gh-93649: Split getargs tests from _testcapimodule.c (#99346)
2022-11-14 17:23:41 -04:00
<ClCompile Include="..\Modules\_testcapi\getargs.c" />
gh-93649: Split vectorcall testing from _testcapimodule.c (GH-94549) The `_testcapimodule.c` file is getting too large to work with effectively. This PR lays out a general structure of how tests can be split up, with more splitting to come later if the structure is OK. Vectorcall tests aren't the biggest issue -- it's just an area I want to work on next, so I'm starting here. An issue specific to vectorcall tests is that it wasn't clear that e.g. `MethodDescriptor2` is related to testing vectorcall: the `/* Test PEP 590 */` section had an ambiguous end. Separate file should make things like this much clearer. OTOH, for some pieces it might not be clear where they should be -- I left `meth_fastcall` with tests of the other calling conventions. IMO, even with the ambiguity it's still worth it to split the huge file up. I'm not sure about the buildsystem changes, hopefully CI will tell me what's wrong. @vstinner, @markshannon: Do you think this is a good idea? Automerge-Triggered-By: GH:encukou
2022-07-08 12:56:26 -03:00
<ClCompile Include="..\Modules\_testcapi\vectorcall.c" />
gh-93649: Split heaptype tests from _testcapimodule.c (GH-95386) This removes the unused negative_dictoffset function: the type this function would create is available as _testcapi.HeapCTypeWithNegativeDict
2022-08-01 10:04:14 -03:00
<ClCompile Include="..\Modules\_testcapi\heaptype.c" />
gh-107178: Add the C API tests for the Abstract Objects Layer (GH-107179) Cover all the Mapping Protocol, almost all the Sequence Protocol (except PySequence_Fast) and a part of the Object Protocol. Move existing tests to Lib/test/test_capi/test_abstract.py and Modules/_testcapi/abstract.c. Add also tests for PyDict C API.
2023-08-07 12:51:43 -03:00
<ClCompile Include="..\Modules\_testcapi\abstract.c" />
gh-93649: Split unicode tests from _testcapimodule.c & add some more (GH-95819) - Move PyUnicode tests to a separate file - Add some more tests for PyUnicode_FromFormat Co-authored-by: philg314 <110174000+philg314@users.noreply.github.com>
2022-08-10 04:10:25 -03:00
<ClCompile Include="..\Modules\_testcapi\unicode.c" />
gh-107178: Add the C API tests for the Abstract Objects Layer (GH-107179) Cover all the Mapping Protocol, almost all the Sequence Protocol (except PySequence_Fast) and a part of the Object Protocol. Move existing tests to Lib/test/test_capi/test_abstract.py and Modules/_testcapi/abstract.c. Add also tests for PyDict C API.
2023-08-07 12:51:43 -03:00
<ClCompile Include="..\Modules\_testcapi\dict.c" />
gh-110525: Add CAPI tests for set and frozenset objects (GH-110526)
2023-10-09 05:57:48 -03:00
<ClCompile Include="..\Modules\_testcapi\set.c" />
gh-111495: add stub files for C API test modules (GH-111586) This is to reduce merge conflicts (Modules/Setup.stdlib.in) for subsequent pull requests for the issue.
2023-11-01 02:44:54 -03:00
<ClCompile Include="..\Modules\_testcapi\list.c" />
<ClCompile Include="..\Modules\_testcapi\tuple.c" />
gh-93649: Split pytime and datetime tests from _testcapimodule.c (#99494)
2022-11-15 03:17:52 -04:00
<ClCompile Include="..\Modules\_testcapi\datetime.c" />
gh-93649: Split memory and docstring tests from _testcapimodule.c (#99517)
2022-11-16 09:09:10 -04:00
<ClCompile Include="..\Modules\_testcapi\docstring.c" />
<ClCompile Include="..\Modules\_testcapi\mem.c" />
gh-93649: Split watcher API tests from _testcapimodule.c (#99532)
2022-11-16 15:13:32 -04:00
<ClCompile Include="..\Modules\_testcapi\watchers.c" />
gh-93649: Split float/long tests from _testcapimodule.c (GH-99549) Automerge-Triggered-By: GH:erlend-aasland
2022-11-17 04:56:56 -04:00
<ClCompile Include="..\Modules\_testcapi\float.c" />
gh-111495: add stub files for C API test modules (GH-111586) This is to reduce merge conflicts (Modules/Setup.stdlib.in) for subsequent pull requests for the issue.
2023-11-01 02:44:54 -03:00
<ClCompile Include="..\Modules\_testcapi\complex.c" />
gh-93649: Split float/long tests from _testcapimodule.c (GH-99549) Automerge-Triggered-By: GH:erlend-aasland
2022-11-17 04:56:56 -04:00
<ClCompile Include="..\Modules\_testcapi\long.c" />
gh-111495: add stub files for C API test modules (GH-111586) This is to reduce merge conflicts (Modules/Setup.stdlib.in) for subsequent pull requests for the issue.
2023-11-01 02:44:54 -03:00
<ClCompile Include="..\Modules\_testcapi\numbers.c" />
gh-47146: Soft-deprecate structmember.h, expose its contents via Python.h (GH-99014) The ``structmember.h`` header is deprecated, though it continues to be available and there are no plans to remove it. There are no deprecation warnings. Old code can stay unchanged (unless the extra include and non-namespaced macros bother you greatly). Specifically, no uses in CPython are updated -- that would just be unnecessary churn. The ``structmember.h`` header is deprecated, though it continues to be available and there are no plans to remove it. Its contents are now available just by including ``Python.h``, with a ``Py`` prefix added if it was missing: - `PyMemberDef`, `PyMember_GetOne` and`PyMember_SetOne` - Type macros like `Py_T_INT`, `Py_T_DOUBLE`, etc. (previously ``T_INT``, ``T_DOUBLE``, etc.) - The flags `Py_READONLY` (previously ``READONLY``) and `Py_AUDIT_READ` (previously all uppercase) Several items are not exposed from ``Python.h``: - `T_OBJECT` (use `Py_T_OBJECT_EX`) - `T_NONE` (previously undocumented, and pretty quirky) - The macro ``WRITE_RESTRICTED`` which does nothing. - The macros ``RESTRICTED`` and ``READ_RESTRICTED``, equivalents of `Py_AUDIT_READ`. - In some configurations, ``<stddef.h>`` is not included from ``Python.h``. It should be included manually when using ``offsetof()``. The deprecated header continues to provide its original contents under the original names. Your old code can stay unchanged, unless the extra include and non-namespaced macros bother you greatly. There is discussion on the issue to rename `T_PYSSIZET` to `PY_T_SSIZE` or similar. I chose not to do that -- users will probably copy/paste that with any spelling, and not renaming it makes migration docs simpler. Co-Authored-By: Alexander Belopolsky <abalkin@users.noreply.github.com> Co-Authored-By: Matthias Braun <MatzeB@users.noreply.github.com>
2022-11-22 03:25:43 -04:00
<ClCompile Include="..\Modules\_testcapi\structmember.c" />
gh-93649: Split exception tests from _testcapimodule.c (GH-102173) Automerge-Triggered-By: GH:erlend-aasland
2023-02-23 11:03:13 -04:00
<ClCompile Include="..\Modules\_testcapi\exceptions.c" />
gh-101101: Unstable C API tier (PEP 689) (GH-101102)
2023-02-28 04:31:01 -04:00
<ClCompile Include="..\Modules\_testcapi\code.c" />
gh-102500: Implement PEP 688 (#102521) Co-authored-by: Kumar Aditya <59607654+kumaraditya303@users.noreply.github.com>
2023-05-04 11:59:46 -03:00
<ClCompile Include="..\Modules\_testcapi\buffer.c" />
gh-108337: Add pyatomic.h header (#108701) This adds a new header that provides atomic operations on common data types. The intention is that this will be exposed through Python.h, although that is not the case yet. The only immediate use is in the test file. Co-authored-by: Sam Gross <colesbury@gmail.com>
2023-08-31 18:41:18 -03:00
<ClCompile Include="..\Modules\_testcapi\pyatomic.c" />
gh-111495: add stub files for C API test modules (GH-111586) This is to reduce merge conflicts (Modules/Setup.stdlib.in) for subsequent pull requests for the issue.
2023-11-01 02:44:54 -03:00
<ClCompile Include="..\Modules\_testcapi\file.c" />
<ClCompile Include="..\Modules\_testcapi\codec.c" />
gh-111545: Test PyHash_GetFuncDef() function (#112098) Add Modules/_testcapi/hash.c and Lib/test/test_capi/test_hash.py.
2023-11-14 22:41:29 -04:00
<ClCompile Include="..\Modules\_testcapi\hash.c" />
gh-110850: Add PyTime_t C API (GH-115215) * gh-110850: Add PyTime_t C API Add PyTime_t API: * PyTime_t type. * PyTime_MIN and PyTime_MAX constants. * PyTime_AsSecondsDouble(), PyTime_Monotonic(), PyTime_PerfCounter() and PyTime_GetSystemClock() functions. Co-authored-by: Victor Stinner <vstinner@python.org>
2024-02-12 13:13:10 -04:00
<ClCompile Include="..\Modules\_testcapi\time.c" />
gh-84436: Add integration C API tests for immortal objects (gh-103962)
2023-05-02 12:05:30 -03:00
<ClCompile Include="..\Modules\_testcapi\immortal.c" />
gh-93649: Split gc- and allocation tests from _testcapimodule.c (GH-104403)
2023-05-12 06:26:07 -03:00
<ClCompile Include="..\Modules\_testcapi\gc.c" />
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
</ItemGroup>
Adds version info to all signed binaries on Windows.
2016-04-06 16:35:24 -03:00
<ItemGroup>
<ResourceCompile Include="..\PC\python_nt.rc" />
</ItemGroup>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
<ItemGroup>
<ProjectReference Include="pythoncore.vcxproj">
<Project>{cf7ac3d1-e2df-41d2-bea6-1e2556cdea26}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
gh-95991: Add some infrastructure for testing Limited API in _testcapi (GH-95992) - Limited API needs to be enabled per source file - Some builds don't support Limited API, so Limited API tests must be skipped on those builds (currently this is `Py_TRACE_REFS`, but that may change.) - `Py_LIMITED_API` must be defined before `<Python.h>` is included. This puts the hoop-jumping in `testcapi/parts.h`, so individual test files can be relatively simple. (Currently that's only `vectorcall_limited.c`, imagine more.)
2022-08-17 08:48:43 -03:00
<ProjectReference Include="python3dll.vcxproj">
<Project>{885d4898-d08d-4091-9c40-c700cfe3fc5a}</Project>
<ReferenceOutputAssembly>false</ReferenceOutputAssembly>
</ProjectReference>
Fix #13210. Port the Windows build from VS2008 to VS2010.
2012-05-13 13:19:23 -03:00
</ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>
gh-106316: Remove pytime.h header file (#106317) Remove the "cpython/pytime.h" header file: it only contained private functions. Move functions to the internal pycore_time.h header file. Move tests from _testcapi to _testinternalcapi. Rename also test methods to have the same name than tested C functions. No longer export these functions: * _PyTime_Add() * _PyTime_As100Nanoseconds() * _PyTime_FromMicrosecondsClamp() * _PyTime_FromTimespec() * _PyTime_FromTimeval() * _PyTime_GetPerfCounterWithInfo() * _PyTime_MulDiv()
2023-07-01 19:27:18 -03:00
</Project>