mirrors
/
micropython
mirror of https://github.com/micropython/micropython.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
micropython/windows
History
Alexander Steffen 55f33240f3 all: Use the name MicroPython consistently in comments 
There were several different spellings of MicroPython present in comments,
when there should be only one.
 		2017-07-31 18:35:40 +10:00
..
msvc all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
.appveyor.yml windows: Add Appveyor CI builds for msvc port. 2015-12-18 21:49:35 +00:00
.gitignore windows: Make msvc project file support any version from VS2013 to VS2017 2017-03-23 15:44:27 +11:00
Makefile all/Makefile: Remove -ansi from GCC flags, its ignored anyway. 2017-03-23 15:32:12 +11:00
README.md windows/README: Add a note about stack usage for msvc 2017-05-01 12:06:43 +02:00
fmode.c mpy-cross: Use binary file translation mode for creating mpy files on windows 2016-07-22 21:21:54 +03:00
fmode.h all: Unify header guard usage. 2017-07-18 11:57:39 +10:00
init.c all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
init.h all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
micropython.vcxproj windows: Make msvc project file support any version from VS2013 to VS2017 2017-03-23 15:44:27 +11:00
mpconfigport.h all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
mpconfigport.mk windows: Follow unix port changes regarding "utime" module. 2016-06-18 00:17:18 +03:00
realpath.c all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
realpath.h all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
sleep.c all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
sleep.h all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
windows_mphal.c all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00
windows_mphal.h all: Use the name MicroPython consistently in comments 2017-07-31 18:35:40 +10:00

README.md

This is the 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.

Building on 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-

Building 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-

Building using MS Visual Studio 2013 (or higher)

In the IDE, open micropython.vcxproj and build.

To build from the command line:

msbuild micropython.vcxproj

Stack usage

The msvc compiler is quite stack-hungry which might result in a "maximum recursion depth exceeded" RuntimeError for code with lots of nested function calls. There are several ways to deal with this:

  • increase the threshold used for detection by altering the argument to mp_stack_set_limit in unix/main.c
  • disable detection all together by setting MICROPY_STACK_CHECK to "0" in windows/mpconfigport.h
  • disable the /GL compiler flag by setting WholeProgramOptimization to "false"

See issue 2927 for more information.

Running on Linux using Wine

The default build (MICROPY_USE_READLINE=1) uses extended Windows console functions and thus should be ran using the 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.