Skip to content
Snippets Groups Projects
Unverified Commit ab296fcd authored by Chrissi^'s avatar Chrissi^ Committed by Matthias Schiffer
Browse files

docs: mention GLUON_RELEASE in make manifest instructions


Adding the fact that GLUON_RELEASE is needed with 'make manifest'
if it is used with 'make'.

This fact was mentioned in the v2017.1 release notes but is not (clearly)
mentioned inside other parts of the documentation.

Signed-off-by: default avatarChrissi^ <chris@tinyhost.de>

[Matthias Schiffer: minor rewording]
parent 2c7f4487
No related branches found
No related tags found
No related merge requests found
......@@ -22,6 +22,11 @@ for updates hourly (at a random minute of the hour), but usually only updates du
``GLUON_PRIORITY`` may be an integer or a decimal fraction.
If ``GLUON_RELEASE`` is passed to ``make`` explicitly or it is generated dynamically
in ``site.mk``, care must be taken to pass the same ``GLUON_RELEASE`` to ``make manifest``,
as otherwise the generated manifest will be incomplete.
Automated nightly builds
------------------------
......
......@@ -184,7 +184,8 @@ GLUON_REGION
GLUON_RELEASE
Firmware release number: This string is displayed in the config mode, announced
via respondd/alfred and used by the autoupdater to decide if a newer version
is available.
is available. The same GLUON_RELEASE has to be passed to ``make`` and ``make manifest``
to generate a correct manifest.
GLUON_TARGET
Target architecture to build.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment