| Age | Commit message (Collapse) | Author |
|---|
|
This adds the --tags argument to the git describe command that is used
to define the MICROPY_GIT_TAG macro. This makes it match non-annotated
tags. This is useful for MicroPython derivatives that don't use
annotated tags.
Signed-off-by: David Lechner <david@pybricks.com>
|
|
This environment variable, if defined during the build process,
indicates a fixed time that should be used in place of "now" when
such a time is explicitely referenced.
This allows for reproducible builds of micropython.
See https://reproducible-builds.org/specs/source-date-epoch/
Signed-off-by: iTitou <moiandme@gmail.com>
|
|
Some downstream projects may use tags in their repositories for more than
just designating MicroPython releases. In those cases, the
makeversionhdr.py script would end up using a different tag than intended.
So tell `git describe` to only match tags that look like a MicroPython
version tag, such as `v1.12` or `v2.0`.
|
|
This is run with uncrustify 0.70.1, and black 19.10b0.
|
|
It's more robust to have the version defined statically in a header file,
rather than dynamically generating it via git using a git tag. In case
git doesn't exist, or a different source control tool is used, it's
important to still have the uPy version number available.
|
|
|
|
The line in docs/conf.py with the release/version number was recently
changed and this patch makes the makeversionhdr.py script work again.
|
|
This script may be called by Windows IDEs (e.g. Visual Studio) and be passed
paths with backslashes.
|
|
|
|
Addresses issue #1420.
|
|
These scripts should run under as wide a range of Python versions as
possible.
|
|
Addresses issue #1285.
|
|
Also rename py-version.h to mpversion.h for consistency with mpconfig.h.
|
