djsundog/circuitpython
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
b25087fc6f
circuitpython/ports/windows/msvc/sources.props

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

34 lines
1.8 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"?>
windows: Unify project file headers. The xmlns attribute is required for older msbuild version (e.g. for VS2015). Add it where needed, and reorder the attributes so all files look the same.
2022-02-22 09:42:50 -05:00
<Project xmlns="http://schemas.microsoft.com/developer/msbuild/2003" ToolsVersion="14.0">
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'"/>
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
<ItemGroup>
windows/msvc: Change the way sources are listed. Reserve sources.props for listing just the MicroPython core and extmod files, similar to how py.mk lists port-independent source files. This allows reusing the source list, for instance for building mpy-cross. The sources for building the executable itself are listed in the corresponding project file, similar to how the other ports specify the source files in their Makefile.
2017-08-16 04:32:47 -04:00
<PyCoreSource Include="$(PyBaseDir)py\*.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\machine_mem.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\machine_pinbase.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\machine_pulse.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\machine_signal.c" />
windows/uasyncio: Add support for uasyncio to windows dev variant.
2022-02-06 22:38:53 -05:00
<PyExtModSource Include="$(PyBaseDir)extmod\moduasyncio.c" />
windows/msvc: Change the way sources are listed. Reserve sources.props for listing just the MicroPython core and extmod files, similar to how py.mk lists port-independent source files. This allows reusing the source list, for instance for building mpy-cross. The sources for building the executable itself are listed in the corresponding project file, similar to how the other ports specify the source files in their Makefile.
2017-08-16 04:32:47 -04:00
<PyExtModSource Include="$(PyBaseDir)extmod\modubinascii.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\moductypes.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\moduhashlib.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\moduheapq.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\modujson.c" />
windows: Switch to VFS subsystem and use VfsPosix. Following the unix port. Signed-off-by: Damien George <damien@micropython.org>
2022-03-08 20:45:06 -05:00
<PyExtModSource Include="$(PyBaseDir)extmod\moduos.c" />
windows/msvc: Change the way sources are listed. Reserve sources.props for listing just the MicroPython core and extmod files, similar to how py.mk lists port-independent source files. This allows reusing the source list, for instance for building mpy-cross. The sources for building the executable itself are listed in the corresponding project file, similar to how the other ports specify the source files in their Makefile.
2017-08-16 04:32:47 -04:00
<PyExtModSource Include="$(PyBaseDir)extmod\modurandom.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\modure.c" />
windows/uselect: Enable micropython select in dev variant.
2021-11-24 20:09:40 -05:00
<PyExtModSource Include="$(PyBaseDir)extmod\moduselect.c" />
windows/msvc: Change the way sources are listed. Reserve sources.props for listing just the MicroPython core and extmod files, similar to how py.mk lists port-independent source files. This allows reusing the source list, for instance for building mpy-cross. The sources for building the executable itself are listed in the corresponding project file, similar to how the other ports specify the source files in their Makefile.
2017-08-16 04:32:47 -04:00
<PyExtModSource Include="$(PyBaseDir)extmod\modutimeq.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\moduzlib.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\utime_mphal.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\virtpin.c" />
windows: Switch to VFS subsystem and use VfsPosix. Following the unix port. Signed-off-by: Damien George <damien@micropython.org>
2022-03-08 20:45:06 -05:00
<PyExtModSource Include="$(PyBaseDir)extmod\vfs.c" />
<PyExtModSource Include="$(PyBaseDir)extmod\vfs_posix.c" />
unix: Remove custom file implementation to use extmod's VFS POSIX one. The implementation in extmod/vfs_posix_file.c is now equivalent to that in ports/unix/file.c, so remove the latter and use the former instead.
2020-03-18 02:47:15 -04:00
<PyExtModSource Include="$(PyBaseDir)extmod\vfs_posix_file.c" />
windows: Switch to VFS subsystem and use VfsPosix. Following the unix port. Signed-off-by: Damien George <damien@micropython.org>
2022-03-08 20:45:06 -05:00
<PyExtModSource Include="$(PyBaseDir)extmod\vfs_reader.c" />
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
</ItemGroup>
<ItemGroup>
windows/msvc: Change the way sources are listed. Reserve sources.props for listing just the MicroPython core and extmod files, similar to how py.mk lists port-independent source files. This allows reusing the source list, for instance for building mpy-cross. The sources for building the executable itself are listed in the corresponding project file, similar to how the other ports specify the source files in their Makefile.
2017-08-16 04:32:47 -04:00
<PyCoreInclude Include="$(PyBaseDir)py\*.h" />
<PyExtModInclude Include="$(PyBaseDir)extmod\*.h" />
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
</ItemGroup>
</Project>
Reference in New Issue Copy Permalink