1berry/cpython
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Issue #19962: The Windows build process now creates "python.bat"

Browse Source 
in the root of the source tree, which passes all arguments through
to the most recently built interpreter.
This commit is contained in:
Zachary Ware 2014-04-30 15:47:53 -05:00
parent b151f8f60b
commit 45bc17b6b4
3 changed files with 166 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
.hgignore
View File

@ -18,6 +18,7 @@ db_home
platform$ platform$
pyconfig.h$ pyconfig.h$
python$ python$
python.bat$
python.exe$ python.exe$
python-config$ python-config$
python-config.py$ python-config.py$

4
Misc/NEWS
View File

@ -322,6 +322,10 @@ IDLE
Build Build
----- -----
- Issue #19962: The Windows build process now creates "python.bat" in the
root of the source tree, which passes all arguments through to the most
recently built interpreter.
- Issue #21285: Refactor and fix curses configure check to always search - Issue #21285: Refactor and fix curses configure check to always search
in a ncursesw directory. in a ncursesw directory.

160
PCbuild/python.vcxproj
View File

@ -156,6 +156,14 @@
<CodeAnalysisRuleSet Condition="'$(Configuration)|$(Platform)'=='Release|x64'">AllRules.ruleset</CodeAnalysisRuleSet> <CodeAnalysisRuleSet Condition="'$(Configuration)|$(Platform)'=='Release|x64'">AllRules.ruleset</CodeAnalysisRuleSet>
<CodeAnalysisRules Condition="'$(Configuration)|$(Platform)'=='Release|x64'" /> <CodeAnalysisRules Condition="'$(Configuration)|$(Platform)'=='Release|x64'" />
<CodeAnalysisRuleAssemblies Condition="'$(Configuration)|$(Platform)'=='Release|x64'" /> <CodeAnalysisRuleAssemblies Condition="'$(Configuration)|$(Platform)'=='Release|x64'" />
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='PGInstrument|Win32'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='PGInstrument|x64'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='PGUpdate|Win32'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='PGUpdate|x64'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">Link</CustomBuildAfterTargets>
<CustomBuildAfterTargets Condition="'$(Configuration)|$(Platform)'=='Release|x64'">Link</CustomBuildAfterTargets>
</PropertyGroup> </PropertyGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|Win32'">
<ClCompile> <ClCompile>
@ -176,6 +184,25 @@
<StackReserveSize>2000000</StackReserveSize> <StackReserveSize>2000000</StackReserveSize>
<BaseAddress>0x1d000000</BaseAddress> <BaseAddress>0x1d000000</BaseAddress>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Release|x64'">
<Midl> <Midl>
@ -199,6 +226,25 @@
<StackReserveSize>2000000</StackReserveSize> <StackReserveSize>2000000</StackReserveSize>
<BaseAddress>0x1d000000</BaseAddress> <BaseAddress>0x1d000000</BaseAddress>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|Win32'">
<ClCompile> <ClCompile>
@ -221,6 +267,25 @@
<StackReserveSize>2000000</StackReserveSize> <StackReserveSize>2000000</StackReserveSize>
<BaseAddress>0x1d000000</BaseAddress> <BaseAddress>0x1d000000</BaseAddress>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='Debug|x64'">
<Midl> <Midl>
@ -246,6 +311,25 @@
<StackReserveSize>4194304</StackReserveSize> <StackReserveSize>4194304</StackReserveSize>
<BaseAddress>0x1d000000</BaseAddress> <BaseAddress>0x1d000000</BaseAddress>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGInstrument|Win32'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGInstrument|Win32'">
<ClCompile> <ClCompile>
@ -268,6 +352,25 @@
<ImportLibrary> <ImportLibrary>
</ImportLibrary> </ImportLibrary>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGInstrument|x64'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGInstrument|x64'">
<Midl> <Midl>
@ -294,6 +397,25 @@
</ImportLibrary> </ImportLibrary>
<TargetMachine>MachineX64</TargetMachine> <TargetMachine>MachineX64</TargetMachine>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGUpdate|Win32'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGUpdate|Win32'">
<ClCompile> <ClCompile>
@ -316,6 +438,25 @@
<ImportLibrary> <ImportLibrary>
</ImportLibrary> </ImportLibrary>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGUpdate|x64'"> <ItemDefinitionGroup Condition="'$(Configuration)|$(Platform)'=='PGUpdate|x64'">
<Midl> <Midl>
@ -342,6 +483,25 @@
</ImportLibrary> </ImportLibrary>
<TargetMachine>MachineX64</TargetMachine> <TargetMachine>MachineX64</TargetMachine>
</Link> </Link>
<CustomBuildStep>
<Command>echo @rem This script invokes the most recently built Python with all arguments&gt; "$(SolutionDir)..\python.bat"
echo @rem passed through to the interpreter. This file is generated by the&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem build process and any changes *will* be thrown away by the next&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem rebuild.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem This is only meant as a convenience for developing CPython&gt;&gt; "$(SolutionDir)..\python.bat"
echo @rem and using it outside of that context is ill-advised.&gt;&gt; "$(SolutionDir)..\python.bat"
echo @echo Running $(Configuration)^^^|$(Platform) interpreter...&gt;&gt; "$(SolutionDir)..\python.bat"
echo @"$(OutDir)python$(PyDebugExt).exe" %%*&gt;&gt; "$(SolutionDir)..\python.bat"</Command>
</CustomBuildStep>
<CustomBuildStep>
<Message>Creating convenience batch file for easily invoking the newly built interpreter.</Message>
</CustomBuildStep>
<CustomBuildStep>
<Outputs>$(SolutionDir)..\python.bat</Outputs>
</CustomBuildStep>
<CustomBuildStep>
<Inputs>$(OutDir)python$(PyDebugExt).exe;%(Inputs)</Inputs>
</CustomBuildStep>
</ItemDefinitionGroup> </ItemDefinitionGroup>
<ItemGroup> <ItemGroup>
<None Include="..\PC\pycon.ico" /> <None Include="..\PC\pycon.ico" />