| Age | Commit message (Collapse) | Author |
|
Moving forward, tags in this repository will always have three components.
Signed-off-by: Damien George <damien@micropython.org>
|
|
This is handy when you are doing builds outside of the Git repository but
still want to record that information.
Signed-off-by: David Grayson <davidegrayson@gmail.com>
|
|
If a CMake-build is run with `make BUILD=/outside/path` then
makeversionheader.py is run with the CWD set to the build directory, which
means the git version lookup will fail and silently fall back to the
mpconfig.h mode (giving the wrong result).
This commit:
- Uses the location of makeversionheader.py to find the repo path.
- Allows overriding this path via --repo-path.
This work was funded through GitHub Sponsors.
Signed-off-by: Jim Mussared <jim.mussared@gmail.com>
|
|
Commit 64af916c111b61bce82c00f356a6b1cb81946d87 removed the version string
from docs/conf.py. py/mpconfig.h is a better place to get the version
from, so use that (when there is no git repository).
Signed-off-by: Damien George <damien@micropython.org>
|
|
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.
|