[RTEMS Project] #4548: Add RTEMS version option to waf configure
RTEMS trac
trac at rtems.org
Sun Nov 14 02:56:59 UTC 2021
#4548: Add RTEMS version option to waf configure
-------------------------+---------------------
Reporter: Chris Johns | Owner: (none)
Type: enhancement | Status: new
Priority: normal | Milestone: 6.1
Component: build | Version: 6
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
-------------------------+---------------------
Comment (by Chris Johns):
I think maintainer experiments should be done with `spec` file changes on
feature branches. My concern about a generic method from the command line,
INI file or any other method is the testable dependencies it exposes. I
feel what we have and where we are at is a good compromise between the web
of options we had with //autoconf's// `configure` the ever present
complexity of build and BSP options we have to have.
I agree the implementation of how to manage this should follow reasonable
design paths but I think the type of action needed has to be explicit with
`wscript` or `spec` file changes.
I have added a call names `item_set_action_value()` that takes a `path`
and `value`. The `value` needs to be of a type and nature that matches the
`action`. The code to set the major version from the command line is:
{{{
if conf.options.rtems_version is not None:
item_set_action_value(conf, '/cpukit/optvermaj/set-value',
conf.options.rtems_version)
}}}
I think a path to address an item is a suitable abstraction. This version
value update happens before the items are processed by `configure` which
is important.
--
Ticket URL: <http://devel.rtems.org/ticket/4548#comment:2>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
More information about the bugs
mailing list