Lines Matching full:overrides

53 overrides, some are less obvious, for example the packaging variables such as
55 ``${PN}-ptest``) as overrides. These overrides are not always in
56 :term:`OVERRIDES` but applied conditionally in specific contexts
58 context being specific tasks in that case. Tune overrides are another special
59 case where some code does use them as overrides but some does not. We plan to try
60 and make the tune code use overrides more consistently in the future.
70 Once configured with the overrides used by a layer, this can be run as::
72    <oe-core>/scripts/contrib/convert-overrides.py <layerdir>
77    expected to handle every case. In particular, it needs to be told which overrides
78    the layer uses (usually machine and distro names/overrides) and the result should
85 variable names without intending to be overrides. This should allow us to proceed
264   built-in override support in the fetcher or overrides in general