github
/
micropython
mirror of https://github.com/micropython/micropython.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
4934 Commits
3 Branches
62 Tags
504 MiB
Tree: c1481bb0ab
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c1481bb0ab'
${ noResults }
micropython/windows/msvc/genhdr.targets

56 lines
2.4 KiB
Raw Normal View History

Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="GenerateHeaders">
msvc: Define main build/include directories in a single location - 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 &#34;py/mpconfig.h&#34; 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.
10 years ago
<Import Project="env.props" Condition="$(PyEnvIncluded)!=True"/>
py: Replace py-version.sh with makeversionhdr.py, written in Python. Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
10 years ago
<!--Generate qstrdefs.h and mpversion.h similar to what is done in py/py.mk-->
<Target Name="GenerateHeaders" DependsOnTargets="MakeQstrData;MakeVersionHdr">
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</Target>
<PropertyGroup>
msvc: Define main build/include directories in a single location - 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 &#34;py/mpconfig.h&#34; 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.
10 years ago
<DestDir>$(PyBuildDir)genhdr\</DestDir>
py: Replace py-version.sh with makeversionhdr.py, written in Python. Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
10 years ago
<PySrcDir>$(PyBaseDir)py\</PySrcDir>
windows: Allow specifying the python executable to use for msvc builds This defaults to &#39;python&#39; but can be now overridden if needed
9 years ago
<PyPython Condition="'$(PyPython)' == ''">python</PyPython>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</PropertyGroup>
<Target Name="MakeDestDir">
<MakeDir Directories="$(DestDir)"/>
</Target>
<Target Name="MakeQstrData" DependsOnTargets="MakeDestDir">
<PropertyGroup>
<PreProc>$(DestDir)qstrdefs.preprocessed.h</PreProc>
msvc: Define main build/include directories in a single location - 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 &#34;py/mpconfig.h&#34; 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.
10 years ago
<QstrDefs>$(PyBaseDir)unix\qstrdefsport.h</QstrDefs>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
<DestFile>$(DestDir)qstrdefs.generated.h</DestFile>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<TmpFile>$(DestFile).tmp</TmpFile>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</PropertyGroup>
msvc: Define main build/include directories in a single location - 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 &#34;py/mpconfig.h&#34; 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.
10 years ago
<ItemGroup>
<PyIncDirs Include="$(PyIncDirs)"/>
</ItemGroup>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<Exec Command="cl /nologo /I@(PyIncDirs, ' /I') /Fi$(PreProc) /P $(PySrcDir)qstrdefs.h"/>
windows: Allow specifying the python executable to use for msvc builds This defaults to &#39;python&#39; but can be now overridden if needed
9 years ago
<Exec Command="$(PyPython) $(PySrcDir)makeqstrdata.py $(PreProc) $(QstrDefs) > $(TmpFile)"/>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<MSBuild Projects="$(MSBuildThisFileFullPath)" Targets="CopyFileIfDifferent" Properties="SourceFile=$(TmpFile);DestFile=$(DestFile)"/>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</Target>
py: Replace py-version.sh with makeversionhdr.py, written in Python. Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
10 years ago
<Target Name="MakeVersionHdr" DependsOnTargets="MakeDestDir">
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
<PropertyGroup>
py: Replace py-version.sh with makeversionhdr.py, written in Python. Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
10 years ago
<DestFile>$(DestDir)mpversion.h</DestFile>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<TmpFile>$(DestFile).tmp</TmpFile>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</PropertyGroup>
windows: Allow specifying the python executable to use for msvc builds This defaults to &#39;python&#39; but can be now overridden if needed
9 years ago
<Exec Command="$(PyPython) $(PySrcDir)makeversionhdr.py $(TmpFile)"/>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<MSBuild Projects="$(MSBuildThisFileFullPath)" Targets="CopyFileIfDifferent" Properties="SourceFile=$(TmpFile);DestFile=$(DestFile)"/>
</Target>
<!--Copies SourceFile to DestFile only if SourceFile's content differs from DestFile's.
We use this to 'touch' the generated files only when they are really newer
so a build is only triggered if the generated content actually changed,
and not just because the file date changed since the last build-->
<Target Name="CopyFileIfDifferent">
<Exec Command="fc /B $(SourceFile) $(DestFile) > NUL 2>&amp;1" IgnoreExitCode="true">
msvc: Only update generated headers when there are changes This fixes generating the headers casuing complete rebuilds, even when the headere&#39;s content didn&#39;t really change.
11 years ago
<Output TaskParameter="ExitCode" PropertyName="FilesDiffer" />
</Exec>
msvc: Use single build target for dealing with generated files Remove some duplication in the code for generating qstrdefs.generated.h and py-version.h
10 years ago
<Copy SourceFiles="$(SourceFile)" DestinationFiles="$(DestFile)" Condition="'$(FilesDiffer)'!='0'"/>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
11 years ago
</Target>
</Project>