circuitpython/windows/msvc
stijn 967ceba5b7 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-12-11 23:42:30 +02:00
..
sys windows: Add modtime implementation 2014-05-09 13:58:15 +02:00
common.props msvc: Use different output directories depending on build type 2015-12-11 23:42:30 +02:00
debug.props Windows MSVC port 2014-05-08 10:06:43 +02:00
genhdr.targets msvc: Use different output directories depending on build type 2015-12-11 23:42:30 +02:00
gettimeofday.c windows: Add modtime implementation 2014-05-09 13:58:15 +02:00
paths.props msvc: Use different output directories depending on build type 2015-12-11 23:42:30 +02:00
release.props Windows MSVC port 2014-05-08 10:06:43 +02:00
sources.props msvc: Use different output directories depending on build type 2015-12-11 23:42:30 +02:00
unistd.h windows: Make unistd.h more posix compatible 2015-08-14 12:04:23 +02:00