summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorZachary Ware <zachary.ware@gmail.com>2014-03-06 19:21:45 (GMT)
committerZachary Ware <zachary.ware@gmail.com>2014-03-06 19:21:45 (GMT)
commit54d04a46f3a0c274fa971ae457134529b22eb64e (patch)
tree96cd4025025196c92ce5067e6fd7946cdf597343
parentccdf352370da4acf2c3f1c77e4a21bc954b4dcf6 (diff)
downloadcpython-54d04a46f3a0c274fa971ae457134529b22eb64e.zip
cpython-54d04a46f3a0c274fa971ae457134529b22eb64e.tar.gz
cpython-54d04a46f3a0c274fa971ae457134529b22eb64e.tar.bz2
Make pywlauncher.vcxproj depend on make_versioninfo.vcxproj.
pylauncher.vcxproj already has the same dependency, and adding it to the pywlauncher project eliminates the possibility of the pywlauncher build failing when building the solution in parallel. In particular, pywlauncher may fail to build when doing a "Rebuild Solution" from the VS Build menu.
-rw-r--r--PCbuild/pywlauncher.vcxproj5
1 files changed, 5 insertions, 0 deletions
diff --git a/PCbuild/pywlauncher.vcxproj b/PCbuild/pywlauncher.vcxproj
index 08e35a7..96ea421 100644
--- a/PCbuild/pywlauncher.vcxproj
+++ b/PCbuild/pywlauncher.vcxproj
@@ -240,6 +240,11 @@
<ItemGroup>
<ResourceCompile Include="..\PC\pylauncher.rc" />
</ItemGroup>
+ <ItemGroup>
+ <ProjectReference Include="make_versioninfo.vcxproj">
+ <Project>{f0e0541e-f17d-430b-97c4-93adf0dd284e}</Project>
+ </ProjectReference>
+ </ItemGroup>
<Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
<ImportGroup Label="ExtensionTargets">
</ImportGroup>