This allows to blacklist platforms not officially supported in a DEY
release. It only works at help-level, you can actually create projects
for any platform whose config files exist, but the help of the mkproject
command will only show the officially supported platforms.
At the moment the BLACKLIST variable is not filled. This will be done in
the release branch.
https://jira.digi.com/browse/DEL-1073
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With the update to Dora, the BB_NUMBER_THREADS and PARALLEL_MAKE entries
in the template config file changed slightly (added a '?'), but enough
so our mkproject script failed to match and configure them properly at
project creation time.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This will allow to pass a TEMPLATECONF path with a predefined
local.conf.template and bblayers.conf.template that will allow
to customize those files.
https://jira.digi.com/browse/DEL-468
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This allows to set MACHINE_VARIANT to the empty string:
MACHINE_VARIANT = ""
in the project's local.conf by running something like:
. /path/to/mkproject.sh -v "" -p <platform>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This script is *sourced*, so we need to make sure that the variables
used do not collide with other variables that may be already in the
environment.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds basic support for platform variants. The script does
not make any sanity check on the variant name. It's user's
responsibility to use the correct variant for the platform.
https://jira.digi.com/browse/DEL-435
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The script in the root directory needs to be in sync with the 'master'
script in the 'meta-digi' layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Alex Gonzalez