8dec62a1a4
- Use a single file env.props for defining the main directories used when building.
env.props resolves the base directory and defines overridable output directories,
and is used by all other build files.
- Fix the build currently failing, basically because the preprocessing command for generating
qstrdefs uses different include directories than the build itself does.
(specifically, qstrdefs.h uses #include "py/mpconfig.h" since the fixes for #1022
in 51dfcb4, so we need to use the base directory as include directory, not the py dir itself).
So define a single variable containing the include directories instead and use it where needed.
17 lines
851 B
XML
17 lines
851 B
XML
<?xml version="1.0" encoding="utf-8"?>
|
|
<Project DefaultTargets="Build" ToolsVersion="12.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
|
|
<Import Project="env.props" Condition="$(PyEnvIncluded)!=True"/>
|
|
<ItemGroup>
|
|
<ClCompile Include="$(PyBaseDir)py\*.c" />
|
|
<ClCompile Include="$(PyBaseDir)extmod\*.c" />
|
|
<ClCompile Include="$(PyBaseDir)unix\*.c" Exclude="$(PyBaseDir)unix\alloc.c;$(PyBaseDir)unix\modffi.c;$(PyBaseDir)unix\modsocket.c;$(PyBaseDir)unix\modtermios.c;$(PyBaseDir)unix\seg_helpers.c" />
|
|
<ClCompile Include="$(PyBaseDir)windows\*.c" />
|
|
<ClCompile Include="$(PyBaseDir)windows\msvc\*.c" />
|
|
</ItemGroup>
|
|
<ItemGroup>
|
|
<ClInclude Include="$(PyBaseDir)py\*.h" />
|
|
<ClInclude Include="$(PyBaseDir)windows\*.h" />
|
|
<ClInclude Include="$(PyBaseDir)windows\msvc\*.h" />
|
|
</ItemGroup>
|
|
</Project>
|