Mirror of git.yoctoproject.org/poky https://git.enea.com/cgit/linux/poky.git/atom?h=uninative-1.3 2016-07-12T22:10:15+00:00 2016-07-12T22:10:15+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2016-07-10T23:07:56+00:00 urn:sha1:5c91537ab250e823b362bf5cc94760d26c6a4429 Certain recipes cannot be used with devtool extract / modify / upgrade - usually because they don't provide any source. Return a specific exit code (4) so that scripts such as scripts/contrib/devtool-stress.py know the difference between this and a genuine failure. (From OE-Core rev: ffd295fed4ab81fc0bd00bb145ef4d72c49584bf) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-06-03T12:13:29+00:00 Ed Bartosh ed.bartosh@linux.intel.com 2016-06-02T10:13:02+00:00 urn:sha1:cdff6bc0c154a5d58a6e6892979af4f99d5a0d74 (From OE-Core rev: 4b544ff388497cac82b0585f237900595523e1cb) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-06-02T07:24:01+00:00 Ed Bartosh ed.bartosh@linux.intel.com 2016-05-18T18:57:23+00:00 urn:sha1:3ee70cb7259aad3b53e51884ec5b9122e804d77e Moved call of decode('utf-8') as close as possible to call of subprocess API to avoid calling it in a lot of other places. Decoded binary data to utf-8 where appropriate to fix devtool and recipetool tests in python 3 environment. (From OE-Core rev: 30d02e2aa2d42fdf76271234b2dc9f37bc46b250) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-06-02T07:24:01+00:00 Ed Bartosh ed.bartosh@linux.intel.com 2016-05-18T18:52:33+00:00 urn:sha1:ed7abe6b9a2ff81d320e7c63841487d37e61b5a5 Python 3 doesn't have basestring type as all string are unicode strings. (From OE-Core rev: e8cfab060f4ff3c4c16387871354d407910e87aa) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-06-02T07:24:01+00:00 Ed Bartosh ed.bartosh@linux.intel.com 2016-05-18T18:39:44+00:00 urn:sha1:7eab022d4b484aec40998f95835ba46c5da168cf Replaced iteritems -> items, itervalues -> values, iterkeys -> keys or 'in' (From OE-Core rev: 25d4d8274bac696a484f83d7f3ada778cf95f4d0) Signed-off-by: Ed Bartosh <ed.bartosh@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-01-26T18:05:14+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2016-01-26T02:53:54+00:00 urn:sha1:89a7ed5b67ca61c24abef07045e781cae892884d When you need to set EXTRA_OECONF for a recipe, you need to know what options the configure script actually supports; the configure script however is only accessible from within a devshell and (at least in the case of autotooled software fetched from an SCM repository) may not actually exist until do_configure has run. Thus, provide a "devtool configure-help" subcommand that runs the configure script for a recipe with --help and shows you the output through a pager (e.g. less), prefaced by a header describing the current options being specified. There is basic support for autotools, cmake and bare configure scripts. The cmake support is a little hacky since cmake doesn't really have a concise help option that lists user-defined knobs (without actually running through the configure process), however that being a design feature of cmake there's not much I can think of to do about that at the moment. (From OE-Core rev: 0e5d84d9705091b338000ef02720cfa090f76888) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-01-11T15:41:46+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2016-01-06T11:15:55+00:00 urn:sha1:b2fe2a8fdc90f1945b9b3184b13b8d5e3e844e2e It's logical that you would want to build BBCLASSEXTENDed items separately through devtool build, so simply allow that - we're just passing the name verbatim to bitbake, so all it means is adjusting the validation. (From OE-Core rev: 25dc5ac42c9da53c01416e7fdcc819d729281133) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2016-01-11T15:41:46+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2016-01-06T11:15:54+00:00 urn:sha1:38ed03975347424558fc02d2973eb4adc88ced85 If the recipe file itself was created in the workspace, and it uses BBCLASSEXTEND (e.g. through devtool add --also-native), then we need to clean the other variants as well. (From OE-Core rev: e1bf6a30679a83d4dbcf37276204f639541e95f9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2015-12-28T09:25:13+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2015-12-22T04:03:06+00:00 urn:sha1:20746544231f9e239ae5ca8993c0369578af9214 We're repeating this in a couple of places, so we might as well have a function to do it. (From OE-Core rev: 67a28109a1ee1383d1b17a8dafa4fe510948238b) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 2015-12-01T21:32:04+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2015-10-14T20:15:33+00:00 urn:sha1:671f41e1d15307964dccc298270f2a739c297f41 This is just belt-and-braces but we ought to use try..finally in this kind of situation, so just do it. (From OE-Core rev: a30b407474d4eb6620f1ec549b54187ebbaff008) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>