diff options
Diffstat (limited to 'documentation/migration-guides')
| -rw-r--r-- | documentation/migration-guides/migration-4.3.rst | 10 | ||||
| -rw-r--r-- | documentation/migration-guides/release-notes-4.3.rst | 12 |
2 files changed, 22 insertions, 0 deletions
diff --git a/documentation/migration-guides/migration-4.3.rst b/documentation/migration-guides/migration-4.3.rst index c2e5699ccb..f526e366ce 100644 --- a/documentation/migration-guides/migration-4.3.rst +++ b/documentation/migration-guides/migration-4.3.rst | |||
| @@ -26,6 +26,16 @@ no longer the default supported configuration. This setting does not affect whic | |||
| 26 | kernel versions SDKs will run against and does not affect which versions of the kernel | 26 | kernel versions SDKs will run against and does not affect which versions of the kernel |
| 27 | can be used to run builds. | 27 | can be used to run builds. |
| 28 | 28 | ||
| 29 | Layername override implications | ||
| 30 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
| 31 | |||
| 32 | Code can now know which layer a recipe is coming from through the newly added | ||
| 33 | :term:`FILE_LAYERNAME` variable and the ``layer-<layername> override``. This is being used | ||
| 34 | for enabling QA checks on a per layer basis. For existing code this has the | ||
| 35 | side effect that the QA checks will apply to things being bbappended to recipes | ||
| 36 | from other layers. Those other layers would need to have patch upstream status | ||
| 37 | entries for patches being bbappended for example. | ||
| 38 | |||
| 29 | .. _migration-4.3-supported-distributions: | 39 | .. _migration-4.3-supported-distributions: |
| 30 | 40 | ||
| 31 | Supported distributions | 41 | Supported distributions |
diff --git a/documentation/migration-guides/release-notes-4.3.rst b/documentation/migration-guides/release-notes-4.3.rst index d782a5917d..c19cf6e4f9 100644 --- a/documentation/migration-guides/release-notes-4.3.rst +++ b/documentation/migration-guides/release-notes-4.3.rst | |||
| @@ -17,6 +17,18 @@ New Features / Enhancements in 4.3 | |||
| 17 | 17 | ||
| 18 | - :term:`KERNEL_DTBVENDORED`: whether to keep vendor subdirectories. | 18 | - :term:`KERNEL_DTBVENDORED`: whether to keep vendor subdirectories. |
| 19 | 19 | ||
| 20 | - :term:`FILE_LAYERNAME`: bitbake now sets this to the name of the layer containing the recipe | ||
| 21 | |||
| 22 | - Layername functionality available through overrides | ||
| 23 | |||
| 24 | Code can now know which layer a recipe is coming from through the newly added :term:`FILE_LAYERNAME` | ||
| 25 | variable. This has been added as an override of the form ``layer-<layername>``. In particular, | ||
| 26 | this means QA checks can now be layer specific, for example:: | ||
| 27 | |||
| 28 | ERROR_QA:layer-core:append = " patch-status" | ||
| 29 | |||
| 30 | which will enable the ``patch-status`` QA check for the core layer. | ||
| 31 | |||
| 20 | - Architecture-specific enhancements: | 32 | - Architecture-specific enhancements: |
| 21 | 33 | ||
| 22 | - Kernel-related enhancements: | 34 | - Kernel-related enhancements: |
