djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
61b560f63f
circuitpython/windows/msvc/genhdr.targets

56 lines
2.4 KiB
Plaintext
Raw Normal View History

Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
<?xml version="1.0" encoding="utf-8"?>
<Project ToolsVersion="4.0" xmlns="http://schemas.microsoft.com/developer/msbuild/2003" DefaultTargets="GenerateHeaders">
msvc: Use different output directories depending on build type This allows multiple versions (e.g. Debug/Release, x86/x64) of micropython.exe to co-exist instead and also solves potential problems where msbuild does not completely rebuild the output and/or pdb files when switching between builds, which in turn can cause linker errors in dependent projects. By default exe/map/... files go in windows/build/$(Configuration)$(Platform) After each build micropython.exe is still copied from the above directory to the windows directory though, as that is consistent with the other ports and the test runner by default uses that location as well. Also rename env.props -> path.props which is a clearer name, and add ample documentation in the affected build files. (also see discussion in #1538)
2015-11-12 03:42:12 -05:00
<Import Project="paths.props" Condition="'$(PyPathsIncluded)' != 'True'"/>
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 "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.
2015-01-02 05:49:23 -05:00
py: Replace py-version.sh with makeversionhdr.py, written in Python. Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
2015-04-22 12:38:05 -04:00
<!--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
2014-05-05 06:18:27 -04:00
</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 "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.
2015-01-02 05:49:23 -05:00
<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.
2015-04-22 12:38:05 -04:00
<PySrcDir>$(PyBaseDir)py\</PySrcDir>
windows: Allow specifying the python executable to use for msvc builds This defaults to 'python' but can be now overridden if needed
2015-11-07 14:00:26 -05:00
<PyPython Condition="'$(PyPython)' == ''">python</PyPython>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
</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 "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.
2015-01-02 05:49:23 -05:00
<QstrDefs>$(PyBaseDir)unix\qstrdefsport.h</QstrDefs>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
<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
2015-01-02 10:31:49 -05:00
<TmpFile>$(DestFile).tmp</TmpFile>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
</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 "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.
2015-01-02 05:49:23 -05:00
<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
2015-01-02 10:31:49 -05:00
<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 'python' but can be now overridden if needed
2015-11-07 14:00:26 -05:00
<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
2015-01-02 10:31:49 -05:00
<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
2014-05-05 06:18:27 -04:00
</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.
2015-04-22 12:38:05 -04:00
<Target Name="MakeVersionHdr" DependsOnTargets="MakeDestDir">
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
<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.
2015-04-22 12:38:05 -04:00
<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
2015-01-02 10:31:49 -05:00
<TmpFile>$(DestFile).tmp</TmpFile>
Windows MSVC port Extend the windows port so it compiles with the toolchain from Visual Studio 2013
2014-05-05 06:18:27 -04:00
</PropertyGroup>
windows: Allow specifying the python executable to use for msvc builds This defaults to 'python' but can be now overridden if needed
2015-11-07 14:00:26 -05:00
<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
2015-01-02 10:31:49 -05:00
<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's content didn't really change.
2014-05-28 10:03:38 -04:00
<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
2015-01-02 10:31:49 -05:00
<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
2014-05-05 06:18:27 -04:00
</Target>
</Project>
Reference in New Issue Copy Permalink