Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=morty-16.0.0 2016-10-15T12:21:54+00:00 2016-10-15T12:21:54+00:00 brian avery brian.avery@intel.com 2016-10-14T15:28:01+00:00 urn:sha1:4b94b498e21aeba945fe7e72a6b7c4bb0314fb83 Set Morty to be the default release in toaster for the Morty release when creating new projects. (Bitbake rev: 00f79096f639ce3a9c0b7c72cfb36f14e264733d) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-15T12:21:54+00:00 brian avery brian.avery@intel.com 2016-10-14T15:28:00+00:00 urn:sha1:33324267c1f26c89342fdaca57316b2e3a232503 Update the poky fixture to the Morty release. This removes the master branch from the release and limits it to the morty branch. Normally, we would also support at least one past branch but the change from Python 2.7 -> Python 3 makes that infeasible. (Bitbake rev: 2674ca33b900f4f3f16be504d7c67d0fc69c1c2d) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-15T12:21:54+00:00 brian avery brian.avery@intel.com 2016-10-14T15:27:59+00:00 urn:sha1:7656dea6dba988f3e85b682e9fd52adca6ecd745 Update the oe-core fixture to the Morty release. This removes the master branch from the release and limits it to the morty branch. Normally, we would also support at least one past branch but the change from Python 2.7 -> Python 3 makes that infeasible. (Bitbake rev: 93f1e6c3d022b1f12a230879160efa941cb1e250) Signed-off-by: brian avery <brian.avery@intel.com> Signed-off-by: Michael Wood <michael.g.wood@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-15T09:01:44+00:00 Aníbal Limón anibal.limon@linux.intel.com 2016-10-14T15:48:39+00:00 urn:sha1:924ca1037c86b9e18ebe9f473df134162ccd570d If bitbake ends before _uiready and bb.event.LogHandler was add to the bitbake logger it causes an infinite loop when logging something. The scenario is print_ui_queue is called at exit and executes the log handlers [2] one of them is bb.event.LogHandler this handler appends the same entry to ui_queue causing the inifine loop [3]. In order to fix a new copy of the ui_queue list is created when iterate ui_queue. [YOCTO #10399] [1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=10399#c0 [2] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n156 [3] http://git.openembedded.org/bitbake/tree/lib/bb/event.py?id=41d9cd41d40b04746c82b4a940dca47df02514fc#n164 (Bitbake rev: 46fecca9d531a07788b5cac8b2dc6a8267d8b6d0) Signed-off-by: Aníbal Limón <anibal.limon@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-13T22:29:25+00:00 Scott Rifenbark srifenbark@gmail.com 2016-10-13T22:00:23+00:00 urn:sha1:1a95d4a0701b87ae3674239a01aabe38a0123585 The BB_SETSCENE_VERIFY_FUNCTION variable has effectively changed to BB_SETSCENE_VERIFY_FUNCTION2. I changed the three areas in the book. Basically a name change. (Bitbake rev: 41d9cd41d40b04746c82b4a940dca47df02514fc) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-13T22:29:25+00:00 Scott Rifenbark srifenbark@gmail.com 2016-10-11T14:59:46+00:00 urn:sha1:19d39be99bddcc72d012710438f6ec636e9f2945 Fixes [YOCTO #10401] Applied some edits to various areas of the section. These were minor in nature. (Bitbake rev: ec99f168fd0d6feca67f2890917ba4829933c73b) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-13T22:29:25+00:00 Scott Rifenbark srifenbark@gmail.com 2016-10-10T19:49:06+00:00 urn:sha1:ce70355260ea0cb0c569706356d60aca2bcf15af Fixes [YOCTO #10401] Added some wording to clarify that setting these flags to "1" causes the desired action. Also, provided a cautionary note about tasks depending on any [nostamp] task causes the task to always be executed and could cause unnecessary rebuild time. (Bitbake rev: b6a4a6147b9e455cc1fec37553fb577f187a2d73) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-13T22:29:25+00:00 Scott Rifenbark srifenbark@gmail.com 2016-10-10T19:39:59+00:00 urn:sha1:1d4031a4dfc3fe633479bb66f97b713be433b49a Fixes [YOCTO #10401] The "addtask" documentation was rewritten to tighten up the introductory section and to flesh out the actual examples. (Bitbake rev: c3373399c5d565de033c40a39e6f6f9399bb782e) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-13T22:29:25+00:00 Scott Rifenbark srifenbark@gmail.com 2016-10-10T18:48:03+00:00 urn:sha1:eedb264387e87e43a51117fbc539993f3aea5bf3 Fixes [YOCTO #10400] No information existed for cases when a variable did not exist. I added this information to each of the variables in the table. (Bitbake rev: 466b2c30f31754a7b6a2478e359f687ec6888e0d) Signed-off-by: Scott Rifenbark <srifenbark@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-10-11T22:43:16+00:00 Randy Witt randy.e.witt@linux.intel.com 2016-10-11T22:36:19+00:00 urn:sha1:a75bccdd14cec2ce6b74a0e6dc3d557593f6abd2 The whitelist checks for BB_SETSCENE_ENFORCE were running for every call to execute(). Since the task list doesn't change for each call into execute, the checks only need to be ran once. [YOCTO #10369] (Bitbake rev: f65e631ab6705dfd9188f19ee423eca33bca7d7d) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>