aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)Author
2016-02-29oeqa/recipetests: Added __init__ file for recipetestsdistrate/bug_6370_testrecipe_finalDaniel Istrate
This will allow the modules inside recipetests to be imported from above. Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-26recipetests: buildrecipe: Test combinations of bbappendDaniel Istrate
Selectively use each combination of .bbappend files with the recipe; All the combinations should not break the recipe build Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-26oeqa/utils/commands: Added method - get_all_bbappendsDaniel Istrate
This method runs 'bitbake-layers show-appends' and returns a dictionary {recipe: [bbappends], ..} Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-25recipetests: buildrecipe: Test suite for recipe testsDaniel Istrate
Includes tests for: 1. test build recipe for all major architectures 2. test rebuild recipe from sstate 1 (with sstate) 3. test_rebuild_recipe_from_sstate_2 (without sstate) 4. test cleaning operations on recipe 5. test force major tasks on recipe fix for [YOCTO #6370] Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-25recipetests: base - Base Class for Test RecipesDaniel Istrate
Test Recipes should inherit this class. It sets up a custom tmp dir for the recipe under test. Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-25scripts: test-recipe Tool for running tests on recipesDaniel Istrate
It shares many functionality with oe-selftest. It requires an aditional argument --recipe <recipe> in order to know on which recipe to test against. Test recipes should be located at: meta/lib/oeqa/recipetests/ Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-25oeqa/utils/commands: Added 3 new methods for recipesDaniel Istrate
get_all_available_recipes, is_recipe_valid, get_tasks_for_recipe Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-25selftest: Moved list_classes, list_modules, run methods to runner.pyDaniel Istrate
Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-24selftest: Moved coverage functionality from oe-selftest to oeqa/runner.pyDaniel Istrate
Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-24selftest: Moved method from oe-selftest to oeqa/runner.pyDaniel Istrate
Moved methods to runner and added parameters to them in order for them to be used by other runners. Signed-off-by: Daniel Istrate <daniel.alexandrux.istrate@intel.com>
2016-02-22uclibc: Do not use immediate expansion operatorKhem Raj
:= causes none of _remove flags to work with uclibc e.g. security flags where we remove ssp options for libcs but it does not become effective for uclibc and hence the build fails (From OE-Core rev: 205b446f3fc4a9885179a66a8dab9d81bcc63dca) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22security_flags: Disable ssp when compiling uclibcKhem Raj
(From OE-Core rev: 208fbdbff17f19a23944a62f1b9ff380f1bc8ac8) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22rpm: fix building rpm 5 with internal beecryptJoshua Lock
RPM 5 cannot be built without beecrypt, therefore the EXTRA_OECONF arguments to pass when the beecrypt PACKAGECONFIG is disabled should enable the internal/bundled beecrypt. [YOCTO #9150] (From OE-Core rev: ed1c47e7c621491b892fb82bd18644dba42212b9) Signed-off-by: Joshua Lock <joshua.g.lock@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22alsa-lib: topology: Add missing include sys/stat.hMaxin B. John
Fixes this build error with uclibc: alsa-lib-1.1.0/src/topology/parser.c: In function 'snd_tplg_build_file': alsa-lib-1.1.0/src/topology/parser.c:262:35: error: 'S_IRUSR' undeclared (first use in this function) open(outfile, O_RDWR | O_CREAT, S_IRUSR | S_IWUSR); (From OE-Core rev: 9ec2c6d4fd9c5c1f745f4d402922b73649ff6287) Signed-off-by: Maxin B. John <maxin.john@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22libsdl2: Fix patch after upgradeRichard Purdie
(From OE-Core rev: 8e94bd650c3480dce6d33b7e7b5af0a440757c29) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0-libav_git: update 1.7.1 -> 1.7.2Andre McCurdy
Hash for libav LICENSE.md updated due to dropping libaacplus: https://github.com/FFmpeg/FFmpeg/commit/9ba54c1b82a81581e5283da75c153a76f04324c0 (From OE-Core rev: 070253835c45c9eff7ad045d99277d13f9d03173) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0-plugins-ugly_git: update 1.7.1 -> 1.7.2Andre McCurdy
(From OE-Core rev: 65128b26479631cd6109602624725aa7840c7e4a) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0-plugins-bad_git: update 1.7.1 -> 1.7.2Andre McCurdy
(From OE-Core rev: f5095eb11215c3aad76edd33cdccbb5dca8296cf) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0-plugins-good_git: update 1.7.1 -> 1.7.2Andre McCurdy
(From OE-Core rev: 2f396eea3c0d054d9b259260e98b688eb9d6d95d) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0-plugins-base_git: update 1.7.1 -> 1.7.2Andre McCurdy
(From OE-Core rev: 4ffd58202081c8492ba600f31e211e1d8241e81d) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-22gstreamer1.0_git: update 1.7.1 -> 1.7.2Andre McCurdy
(From OE-Core rev: 3ca15468208cd9e64eec8bc85d40bc2a13fd1348) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21libnewt: Fix build with PIE flagsKhem Raj
security flags add -pie -fpie to CFLAGS which is not right options for compiling .so files, they are only useful for compiling executables (From OE-Core rev: 2735d096aef2d039d711c13c311bb6dba979f437) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21pseudo: Fix build when security flags are enabledKhem Raj
filter out PIE options (From OE-Core rev: 138fdeacb822705f9d3d363753f93ff653e7928b) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21glibc: Upgrade to 2.23Khem Raj
Drop kconfig and options-group support Forward port cross-localedef support Assume ssp support in libc when building gcc-initial (From OE-Core rev: 9c3d461c4d54d684b38ec4c038a1c3c2fb9923f0) Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21no-static-libs: remove eglinfoRoss Burton
waf.bbclass disables no-static-libs for all waf recipes, so we don't need to have it explicitly disabled here now. (From OE-Core rev: 6eb64cdd5296c42a46f3485bca403814eec55b2c) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21freetype: use autotools instead of a manual do_configureRoss Burton
autotools.bbclass has enough variables now that we can use it instead of hand-coding a do_configure. (From OE-Core rev: c8bd926cfa2f74ca59c379072c40322605a76bd2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21classes/populate_sdk_ext: add a better config extension mechanismPaul Eggleton
The sdk_extraconf() method of setting the configuration was awkward since you needed to set it in a class and then inherit that class since function definitions aren't allowed in conf files. It seemed to me the a neater way to do this was to read the extra lines from an additional conf file sdk-extra.conf (which can be located in a conf/ directory anywhere along BBPATH as with other configuration files). (From OE-Core rev: b53edb86c65ad375df153017f245244ef97f3932) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21recipetool: create: improve CMake package mappingPaul Eggleton
* Package names are actually case sensitive near as I can tell, so we shouldn't be lowercasing them everywhere. * Look for CMake packages in pkgdata and map those back to recipes, so we aren't dependent on the hardcoded mappings (though those are still preserved). * Avoid duplicates in the unmapped package list (From OE-Core rev: 2ddad52ccca07245eea43d9b844c6c7d4b667ca3) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21recipetool: create: add additional extension mechanismsPaul Eggleton
Add a means of extending the dependency extraction for autotools and cmake. Note: in order to have this work, you need to have an __init__.py in the lib/recipetool directory within your layer along with the module implementing the handlers, and the __init__.py needs to contain: # Enable other layers to have modules in the same named directory from pkgutil import extend_path __path__ = extend_path(__path__, __name__) (From OE-Core rev: 915dea9f89cd737e5ba167c384e8d314c5c23c49) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: modify: tweak help description for behaviour changePaul Eggleton
I should have adjusted this in OE-Core commit 80a44e52609a89d9ffe816181ae193af491c06ac where the behaviour changed. (From OE-Core rev: 13409a2b899bb74b8060c840b8c7ef8759d099cb) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: deploy-target: preserve existing filesPaul Eggleton
If files would be overwritten by the deployment, preserve them in a separate location on the target so that they can be restored if you later run devtool undeploy-target. At the same time, also check for sufficient space before starting the operation so that we avoid potentially failing part way through. Fixes [YOCTO #8978]. (From OE-Core rev: a2da55712691bcf1066c53d813107d75213d6b10) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: undeploy-target: support undeploying all recipesPaul Eggleton
If you want to put the target device back to exactly how it was before devtool deploy-target started poking things into it, then it would make things easier if you didn't have to figure out which recipes were deployed. Now that we have the list stored on the target we can determine this reliably, so add a -a/--all option to undeploy-target to undeploy everything that has been deployed. One of the side-effects of this is that the dry-run functionality for undeploy-target had to be reimplemented to actually run the script on the target, since we have no way of knowing what's been deployed from the host side. We don't need to do the same for deploy-target though since we know exactly which files will be deployed without referring to the target. (From OE-Core rev: 41fed83060f0041e14e455d1446397bda277d953) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: deploy-target: write deployed files list to targetPaul Eggleton
When running devtool deploy-target, we save a list of deployed files, and this list is used by devtool undeploy-target (or the next time deploy-target is run if the list is present, in case any files have been renamed or deleted since the first time). We were writing this file to the host, but it makes more sense to write the list to the target instead, so that if we for example swap in a different board, or switch hosts, things will work as expected. In order to do this properly we have to construct a shell script and ship it over to the target so we can run it. The manifest is written out to a hidden directory in the root (/.devtool). Fixes [YOCTO #7908]. (From OE-Core rev: a16a0c9334b785e2df896266c8911a2c7a1806b8) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: sdk-update: tweak command-line handling of updateserverPaul Eggleton
Get the default value for updateserver from the configuration file and show it in the help; also only make the parameter optional if it's specified. This means we can also drop the check in the function as argparse will then ensure it's specified if there's no config setting. (From OE-Core rev: 82497bde58fc8bdae8d8acfbf025a1a90b14cc3e) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: (un)deploy-target: add help descriptionsPaul Eggleton
Add a long description used when running --help on the specific command. (From OE-Core rev: eb7787d1652fd84a149fd394969f4f1099406051) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21scripts/lib/argparse_oe: tweak title above optionsPaul Eggleton
Naming these as "optional arguments" is perhaps slightly confusing since some of the positional arguments might also be optional; in addition it's rare (though possible) for options to be mandatory - up until recently we had a recipetool option (-o) that was mandatory. It's not perfect, but change it to "options" so it's at least a bit more appropriate. (From OE-Core rev: 55e675de6191bf7eccd26df29189f2a6faa40a20) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: categorise and order subcommands in help outputPaul Eggleton
The listing of subcommands in the --help output for devtool was starting to get difficult to follow, with commands appearing in no particular order (due to some being in separate modules and the order of those modules being parsed). Logically grouping the subcommands as well as being able to exercise some control over the order of the subcommands and groups would help, if we do so without losing the dynamic nature of the list (i.e. that it comes from the plugins). Argparse provides no built-in way to handle this and really, really makes it a pain to add, but with some subclassing and hacking it's now possible, and can be extended by any plugin as desired. To put a subcommand into a group, all you need to do is specify a group= parameter in the call to subparsers.add_parser(). you can also specify an order= parameter to make the subcommand sort higher or lower in the list (higher order numbers appear first, so use negative numbers to force items to the end if that's what you want). To add a new group, use subparsers.add_subparser_group(), supplying the name, description and optionally an order number for the group itself (again, higher numbers appear first). (From OE-Core rev: e1b9d31e6ea3c254ecfe940fe795af44761e0e69) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: update-recipe: don't show workspace recipe warning if no updatePaul Eggleton
If we didn't make any changes to the file then there's no point warning the user that we have done. (From OE-Core rev: 391b9ba30d802ac420ddf382588e03e718861c01) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: reset: fix preserving patches/other files next to recipesPaul Eggleton
If files had been created next to the recipe (for example devtool add, edit the source and commit and then devtool update-recipe), running devtool reset failed to preserve those files and gave an error due to trying to rmdir the directory containing them which wasn't empty. Fix the preservation of files in the "attic" directory properly so we catch anything under the directory for the recipe, and replicate the same structure in the attic directory rather than slightly flattening it as we were before. (From OE-Core rev: bbe63eb97ae7f78959f117d6066ef821c4da1c77) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool / recipetool: use common code for launching editorPaul Eggleton
Looking at Chris Larson's code for starting the user's editor for "recipetool newappend" it was slightly better than what I wrote for "devtool edit-recipe" in that it checks VISUAL as well as EDITOR and defaults to vi if neither are set, so break this out to its own function and call it from both places. The broken out version passes shell=True however in case it's a more complicated command rather than just a name of an executable. (From OE-Core rev: 184a256931e8cdc7bea97a905c4e67a435964de0) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21devtool: minor fix for error messagePaul Eggleton
There is no -N/--name option for devtool, that's a recipetool option - with devtool you just specify the name as a positional argument. (From OE-Core rev: d2bc0cba5ca8a7220ffe1ef96acf856fe972ce7c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21staging.bbclass: remove trail slash from SYSROOT_DESTDIRRobert Yang
Fixed path: QA Issue: <foo> sysroot-destdir//usr/lib/ <foo> Note the 2 slashes "//". (From OE-Core rev: 227247dfebe6cdff67ba2c0976b59e3f9d34f7ea) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21terminal.bbclass: import oe.terminal for oe.terminal.prioritized()Robert Yang
Fixed: INHERIT += "typecheck" $ bitbake -p ERROR: Failure expanding expression auto none ${@" ".join(o.name for o in oe.terminal.prioritized())} which triggered exception AttributeError: 'module' object has no attribute 'terminal' (From OE-Core rev: 74bc2a65ec18c749d9343d9a33eccae93726846c) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21recipe_sanity.bbclass: skip DataSmart in recipe_sanity_eh()Robert Yang
Fixed: $ bitbake quilt -crecipe_sanity File "/path/to/poky/bitbake/lib/bb/siggen.py", line 261, in dump_sigtask p = pickle.dump(data, stream, -1) PicklingError: Can't pickle <COWDict Level: 1 Current Keys: 0>: attribute lookup bb.COW.C failed This is because of: cfgdata[k] = d.getVar(k, 0) If d.getVar(k, 0) is a DataSmart (for example, BB_ORIGENV), it won't have the attribute of bb.COW.C, so the error happend. (From OE-Core rev: 9979f8ad588564cd9d177e24a28ceefefec4df7d) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21image.bbclass: fix circular dependency when IMAGE_FSTYPES append hddimgRobert Yang
Fixed: IMAGE_FSTYPES_append = " hddimg" $ bitbake -g core-image-minimal-initramfs NOTE: Resolving any missing task queue dependencies NOTE: Preparing RunQueue ERROR: Task /path/to/core-image-minimal-initramfs.bb (do_bootimg) has circular dependency on /path/to/core-image-minimal-initramfs.bb (do_image_complete) ERROR: Command execution failed: Exited with 1 This is because IMAGE_FSTYPES = "${INITRAMFS_FSTYPES}", and if IMAGE_FSTYPES append hddimg, then core-image-minimal-initramfs.bb would be circular dependency: do_bootimg -> do_image_complete -> do_bootimg. Now we check and error out. (From OE-Core rev: 9b48bfbc2f60bdaa792a98485db68699e0635cbe) Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21toolchain-scripts.bbclass: add three other path to PATH in env.shJun Zhang
in sdk,there are some utils in sysroot/host-os/bin, sysroot/host-os/sbin/,sysroot/host-os/usr/bin need to use, so add these three paths to PATH in env.sh. (From OE-Core rev: 1116572916443109176c0df32efc275eceeb706a) Signed-off-by: Jun Zhang <jun.zhang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21libsoup-2.4: disable libsoup-gnome by defaultAndre McCurdy
libsoup-gnome is entirely deprecated and has just been stubs since 2.42. (From OE-Core rev: 1602e8edf998ad2cd7dc06c5d55f4aad1ff24af1) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21libsoup-2.4: prevent PACKAGECONFIG dependant package renamingAndre McCurdy
When built without gnome support, libsoup-2.4 will contain only one shared lib and will therefore become subject to renaming by debian.bbclass. Prevent renaming in order to keep the package name consistent regardless of whether gnome support is enabled or disabled. (From OE-Core rev: f5f95f501c8aacb3d624e683b4b5b8403115ba5d) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21libsoup-2.4: minor formatting improvementsAndre McCurdy
Also update HOMEPAGE from generic Gnome to something libsoup specific. (From OE-Core rev: 9473ffc11e586eba6a1cef2e5c8d293695685941) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2016-02-21populate_sdk_ext.bbclass: Add SDK_RECRDEP_TASKS variableRandy Witt
Currently there isn't a way for the extensible sdk to know all the tasks that will need sstate for an image. This is because a layer can add it's on custom tasks that are required for an image to be generated. The extensible sdk solved this for poky by using recrdeptask and specifying the tasks known to be required for the image as well as for building new recipes. So the SDK_RECRDEP_TASKS variable allows a user to specify additional tasks that need to be pulled in. (From OE-Core rev: 4236b9653f6dfbddc937108bbbd9a9445eb81382) Signed-off-by: Randy Witt <randy.e.witt@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>