FutureMigrationGuide: Difference between revisions
No edit summary |
|||
| Line 16: | Line 16: | ||
5. poky is now using security compiler files by default. These may cause new failures due to stricter checking for various potential security issues in code. | 5. poky is now using security compiler files by default. These may cause new failures due to stricter checking for various potential security issues in code. | ||
6. postinstalls now need to be explicitly marked to defer to target as the warnings in the previous release became errors | |||
Revision as of 14:19, 30 October 2018
| This page should be used to keep track of items which should be added to the migration guide in the YP Reference Manual. It's a living document for the life of a development cycle and by M4 should represent a significant proportion of items that are worthy of note in the migration guide.
Once the migration guide for a release has been completed the contents of this page should be cleared out. |
2.6 Migration Guide items
1. TEST_IMAGE is removed. To do testimage automatically, set TESTIMAGE_AUTO to boolean true.
2. It's now encouraged that users use IMAGE_CLASSES instead of INHERIT for 'testimage' and 'testsdk'. The interface for INHERIT might not be supported in later releases.
3. openssl was upgraded from 1.0 to 1.1 by default and this may cause problems for recipes which end up with both versions in their dependency chains as they both cannot be installed together at build time. It is possible to have both libraries at runtime.
4. The _remove operator now preserves whitespace whereas previous it was documented not to.
5. poky is now using security compiler files by default. These may cause new failures due to stricter checking for various potential security issues in code.
6. postinstalls now need to be explicitly marked to defer to target as the warnings in the previous release became errors
