openmano-mpy/windows/msvc/genhdr.targets, branch master MicroPython source and hardware configuration for OpenMano ports: Make new ports/ sub-directory and move all ports there. 2017-09-06T03:40:51+00:00 Damien George 2017-09-06T03:40:51+00:00 01dd7804b87d60b2deab16712eccb3b97351a9b7 This is to keep the top-level directory clean, to make it clear what is core and what is a port, and to allow the repository to grow with new ports in a sustainable way. 
This is to keep the top-level directory clean, to make it clear what is
core and what is a port, and to allow the repository to grow with new ports
in a sustainable way.
msvc: Workaround parser bug in older MSBuild versions 2017-05-03T00:41:53+00:00 stijn 2017-05-01T08:50:58+00:00 ab4a8618cffc02d0838bd64372b066c99c2d2d7e Versions prior to v14.0 have a bug in parsing item functions when used within a condition: https://github.com/Microsoft/msbuild/issues/368. Since commit [db9c2e3] this results in an error when building MicroPython with for example VS2013. Fix this by creating an intermediate property. 
Versions prior to v14.0 have a bug in parsing item functions when used
within a condition: https://github.com/Microsoft/msbuild/issues/368.
Since commit [db9c2e3] this results in an error when building MicroPython
with for example VS2013.
Fix this by creating an intermediate property.
msvc: Rebuild all qstrs when mpconfig headers are modified 2017-04-30T11:30:39+00:00 stijn 2017-04-03T11:16:12+00:00 db9c2e310e0039c8280256c17ac338f31bcbd9cc Make qstr generation depend on modifications in mpconfigport.h, mpconfig.h and makeqstrdata.py and if any of those change scan all source files for qstrs again since they might have changed (for example typcially when enabling new features in mpconfig.h). This fixes #2982 for msvc builds. 
Make qstr generation depend on modifications in mpconfigport.h, mpconfig.h
and makeqstrdata.py and if any of those change scan all source files for
qstrs again since they might have changed (for example typcially when
enabling new features in mpconfig.h).
This fixes #2982 for msvc builds.
msvc: Remove directory with generated files when cleaning. 2017-03-23T04:49:57+00:00 stijn 2017-03-22T09:54:40+00:00 3f3df435014cc835ce9357e15ddb8996c5866f43 This assures after cleaning all build artefacts (qstr related files, generated version header) have been removed. 
This assures after cleaning all build artefacts (qstr related files,
generated version header) have been removed.
py: Rename __QSTR_EXTRACT flag to NO_QSTR. 2016-06-15T22:42:48+00:00 Paul Sokolovsky 2016-06-15T22:40:31+00:00 f469c764428230363a2b22fedf303d86eea82853 It has more usages than just qstr extraction, for example, embedding (where people don't care about efficient predefined qstrs). 
It has more usages than just qstr extraction, for example, embedding (where
people don't care about efficient predefined qstrs).
windows/msvc: Rewrite qstr auto-generation. 2016-04-25T21:34:24+00:00 stijn 2016-04-23T16:55:14+00:00 29c8c8aecb3409e57a43256f8fe5cb25de1e9856 Builds have been broken since reworking autogeneration in c618f91 and related, this gets fixed here by applying similar qstr generation logic for the msvc builds: c files are only preprocessed when changed (or not yet preprocessed) and the concatenated output is fed into makeqstrdefs.py. To speed up this process, the concatenated output is already filtered to contain only lines which makeqstrdefs really needs: this makes the qstr generation stage about twice as fast (checked on different machines). 
Builds have been broken since reworking autogeneration in c618f91 and
related, this gets fixed here by applying similar qstr generation logic
for the msvc builds: c files are only preprocessed when changed (or not
yet preprocessed) and the concatenated output is fed into makeqstrdefs.py.
To speed up this process, the concatenated output is already filtered to
contain only lines which makeqstrdefs really needs: this makes the qstr
generation stage about twice as fast (checked on different machines).
windows/msvc: Implement automatic qstr generation using makeqstrdefs. 2016-04-16T12:19:15+00:00 stijn 2016-03-15T09:22:34+00:00 9a627e8881c1b5d8fad9f1a563b5af23716e1b55 Note this still needs some work: currently all source files are always preprocessed no matter which one actually changed, moreover that happens file by file without any parallellism so builds are painstakingly slow. 
Note this still needs some work: currently all source files are always
preprocessed no matter which one actually changed, moreover that happens
file by file without any parallellism so builds are painstakingly slow.
msvc: Use different output directories depending on build type 2015-12-11T21:42:30+00:00 stijn 2015-11-12T08:42:12+00:00 967ceba5b7fc56f7642947b2c48199a4d9db0d4a 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) 
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)
windows: Allow specifying the python executable to use for msvc builds 2015-11-10T15:37:09+00:00 stijn 2015-11-07T19:00:26+00:00 b1dbbd32ebcdafd046e8d69ec29a1565f42765cb This defaults to 'python' but can be now overridden if needed 
This defaults to 'python' but can be now overridden if needed
py: Replace py-version.sh with makeversionhdr.py, written in Python. 2015-04-28T22:52:36+00:00 Damien George 2015-04-22T16:38:05+00:00 95f53461c2c42490d12acd41463b86f0056e6f40 Also rename py-version.h to mpversion.h for consistency with mpconfig.h. 
Also rename py-version.h to mpversion.h for consistency with mpconfig.h.