c61131380d
Instead of having the PlatformToolset property hardcoded to a specific version just set it to the value of DefaultPlatformToolset: this gets defined according to the commandline environment in which the build was started. Instead of just supporting VS2015 the project can now be built by any version from VS2013 to VS2017 and normally future versions as well, without quirks like VS asking whether you want to upgrade the project to the latest version (as was the case when opening the project in VS2017) or not being able to build at all (as was the case when opening the project in VS2013). Also adjust the .gitignore file to ignore any artefacts from VS2017. |
||
---|---|---|
.. | ||
msvc | ||
.appveyor.yml | ||
.gitignore | ||
fmode.c | ||
fmode.h | ||
init.c | ||
init.h | ||
Makefile | ||
micropython.vcxproj | ||
mpconfigport.h | ||
mpconfigport.mk | ||
README | ||
realpath.c | ||
realpath.h | ||
sleep.c | ||
sleep.h | ||
windows_mphal.c | ||
windows_mphal.h |
This is experimental, community-supported Windows port of MicroPython. It is based on Unix port, and expected to remain so. The port requires additional testing, debugging, and patches. Please consider to contribute. To cross-compile under Debian/Ubuntu Linux system: sudo apt-get install gcc-mingw-w64 make CROSS_COMPILE=i686-w64-mingw32- If for some reason the mingw-w64 crosscompiler is not available, you can try mingw32 instead, but it comes with a really old gcc which may produce some spurious errors (you may need to disable -Werror): sudo apt-get install mingw32 mingw32-binutils mingw32-runtime make CROSS_COMPILE=i586-mingw32msvc- To compile under Cygwin: Install following packages using cygwin's setup.exe: mingw64-i686-gcc-core, mingw64-x86_64-gcc-core, make Build using: make CROSS_COMPILE=i686-w64-mingw32- or for 64bit: make CROSS_COMPILE=x86_64-w64-mingw32- To compile using Visual Studio 2013 (or higher): Open micropython.vcxproj and build To compile using Visual Studio 2013 (or higher) commandline: msbuild micropython.vcxproj To run on Linux using Wine: The default build (MICROPY_USE_READLINE=1) uses extended Windows console functions and thus should be run using "wineconsole" tool. Depending on the Wine build configuration, you may also want to select the curses backend which has the look&feel of a standard Unix console: wineconsole --backend=curses ./micropython.exe For more info, see https://www.winehq.org/docs/wineusr-guide/cui-programs If built without line editing and history capabilities (MICROPY_USE_READLINE=0), the resulting binary can be run using the standard "wine" tool.