summaryrefslogtreecommitdiffstats
path: root/meta/recipes-sato/images
Commit message (Collapse)AuthorAgeFilesLines
* core-image-sato-ptest-fast: don't hard fail in ptestsAlexander Kanavin2020-03-241-0/+3
| | | | | | | | | | Unfortunately, a couple of tests sporadically fail still; bugs have been filed, but they will take time to resolve. (From OE-Core rev: 6b408f40b6c214d05433c41f0cd6200c715cc615) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* ptest: add an option to enforce a failure (e.g. ptests are required to pass)Alexander Kanavin2020-02-251-0/+3
| | | | | | | | | | | | | | | | | | This can be useful with a more specific, targeted and robust set of ptest packages; the benefit is that ptest regressions are caught as they happen and can be more easily traced to changes that caused them. The existing AB ptest image continues to be expected to fail, my observation of the AB runs is that the full set of ptests is not robust enough (particularly around socket/network related tests) and sporadically fails in random places. This can probably be addressed by making ptests exclusive to a worker (e.g. there is no other workload happening at the same time as ptests). (From OE-Core rev: 102afcc7ea7d7673183f272a29ab233084ad168b) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: do not pull in ptest-pkgsAlexander Kanavin2020-02-211-2/+0
| | | | | | | | | | | | The lists of ptests are defined via PTESTS_FAST and PTESTS_SLOW; specifying 'ptests-pkgs' also pulls in additional ptests that are specifically excluded from those lists due to causing issues with ptesting. (particularly bash-ptest is one such item) (From OE-Core rev: 1d8e5d1bc1aa8fdaf967395e27b13cc989717fb7) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: use 2G of RAMAlexander Kanavin2020-01-281-1/+2
| | | | | | | | | | Particularly, 1G wasn't enough for lttng-tools ptests as half of that went to /tmp, and lttng-tools needs more. (From OE-Core rev: abc308a38c6e37afcaf507858a6578c10438c5d8) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato: don't use 512MB in qemumipsRoss Burton2019-09-061-0/+1
| | | | | | | | | | | | qemumips doesn't appear to work well with 512MB of RAM and randomly hangs. As the bump to 512MB was primarily motivated by the memory needs of virtualised GL which doesn't work in qemumips currently, drop the memory back to 256MB for qemumips. (From OE-Core rev: 499a31cf06c934b40b5866d5eb77c9ad20c9a15f) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* images: use 512M of RAM in qemu if 'opengl" is in DISTRO_FEATURESAlexander Kanavin2019-08-281-0/+2
| | | | | | | | | | | | 256M was found to be no longer sufficient, as the X server fails to start with the modesetting driver and 3D enabled. Only images that actually include X11 are adjusted. (From OE-Core rev: 9dd0812acc73287287b48d28e0935baf7f545b58) Signed-off-by: Alexander Kanavin <alex.kanavin@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Reduce image padding size due to bootimg 4GB limitRichard Purdie2019-07-091-2/+2
| | | | | | | | | | This image continues to run out of space on the autobuilder, tweak it a bit further now the image space requirements were reduced after various ptest fixes to avoid the error. (From OE-Core rev: 9f974dd51c18a1387134a9350097dea97ef5f7d0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Tweak size to stay within 4GB limitRichard Purdie2019-05-151-2/+2
| | | | | | | | | | Adding the valgrind debug symbol information caused the genericx86-64 image to overflow the 4GB boundary. Tweak the sizes to avoid autobuilder failures yet leave enough space all the tests still run successfully. (From OE-Core rev: fa24a5056acea6610e2ad1a1eb1e7425a3828979) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Add temporary PROVIDES core-image-sato-ptestRichard Purdie2019-04-231-0/+2
| | | | | | | | | | Since we want to ultimately move this recipe to that name, add a PROVIDES to allow things to work whilst we fix the bugs preventing the move. This avoids having to keep changing the autobuilder. (From OE-Core rev: 2b70ea6ca2c96fb233f42cfe5058cc89c9de5f82) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Include more ptests in ptest imageRichard Purdie2019-04-231-0/+4
| | | | | | | | | There are recipes not included in core-image-sato-sdk which have ptests, include these in our ptest test image using the new include file. (From OE-Core rev: f685ec5740e1a8c3922f8f0631ddaed4b2a5d1f0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-ptest-fast: Add 'fast' ptest execution imageRichard Purdie2019-04-231-0/+16
| | | | | | | | | | | | | | Create a common include file which lists recipes that have ptests divided into 'fast' and 'slow' groups. This allows us to include ptests which otherwise may not get included in images and allows us to test the faster running things more regularly. The new image allows access to these faster executing tests. 'fast' is defined as tests which execute in under 30s roughly speaking. (From OE-Core rev: 2d8f8ab85d98929b0f1f699f256b40b1d9cddaec) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Try and keep image below 4GB limitRichard Purdie2019-04-161-2/+2
| | | | | | (From OE-Core rev: 879b590fe810a543af4cb4ec2c593c448a22a56c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Fix free space issues causing test failuresRichard Purdie2019-04-041-3/+4
| | | | | | | | | | | | | | | Some tests such as strace-ptest require more than the current 500MB of free space. Increase the amount available, staying under the 4GB limit. We have more flexibility now since we shrank kernel-devsrc and the comments are out of date due to that. This should improve the strace-ptest results and the util-linux ones since those sort after strace and also hit the space issues as strace-ptest didn't clean up after itself when failing. (From OE-Core rev: 5c1b2459e2d5651b02bdfdf6cb93b7f9ce32df0a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: Increase qemu memory to 1GBRichard Purdie2019-02-021-0/+3
| | | | | | (From OE-Core rev: 975526b8e38a4a0087f8bbe42dc30a01a33179b0) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk-ptest: reduce sizeRoss Burton2017-09-261-0/+5
| | | | | | | | | | | | | | | | | | | | This image is very large and is skirting the maximum size of hddimg images (4GB, as they're embedded inside FAT partitions). Making the image 10MB bigger can be enough to cause the build to fail. This image is also used by QA so currently we need to keep it working. The default values for expanding an image to give it usable space are quite generous, (3GB rootfs * 1.3 gives 1GB of empty space), so change the overhead multiplier to 1.0x and explicitly request just 0.5GB of empty space in the images. This should give us a bit more breathing room until we can either remove hddimg from the default build, or make this image dramatically smaller. (From OE-Core rev: 98d9d8958fd5a3bba849e9051bf0310c28b551c2) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato: drop packagegroup-core-x11-sato-games from IMAGE_INSTALLMing Liu2017-06-231-2/+0
| | | | | | | | | | | | | | | | | | packagegroup-core-x11-sato-games package is being RDEPENDS by packagegroup-core-x11-sato, hence will be installed if x11-sato is choosen in IMAGE_FEATURES. So it's unnecessary appending it into IMAGE_INSTALL. Even worse, it's causing the following error when x11 is not in DISTRO_FEATURES: | ERROR: Required build target 'core-image-sato' has no buildable providers. | Missing or unbuildable dependency chain was: ['core-image-sato', 'packagegroup-core-x11-sato-games'] (From OE-Core rev: 6c28b122e6214a9e57e4b116ff85145d9ac845ec) Signed-off-by: Ming Liu <peter.x.liu@external.atlascopco.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato: SDK should contain intltool and glib-2.0 tools for NLSRichard Purdie2017-01-201-0/+3
| | | | | | | | | | | | | | The SDK (and its tests) need these tools. We happened to be finding them from the native tools in PATH but recipe specific sysroots prevents that. This fixes the SDK to work as originally intended and contain these tools. We have to clear this in the eSDK case since the _append can't be overridden from the class. Ugly, but we'll have to come back to this issue. (From OE-Core rev: edde4c52872fbd089f85b10b94db4d6ef1796be5) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Revert "core-image-sato: add gtk+ for M1"Ross Burton2016-07-201-2/+1
| | | | | | | | | | | | | | | We added gtk+ to core-image-sato for M1 solely because the SDK self test was building an application (sudoku) that links to GTK+ 2. Now that sukoku has been replaced with galculator this workaround can be removed. This reverts commit 282d5f7f8573551b94c6b610370db15665cf4bdf. (From OE-Core rev: aaccc1109fbdda72ffc5b5e66177d00b365d267b) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato: add gtk+ for M1Ross Burton2016-06-151-1/+2
| | | | | | | (From OE-Core rev: eae1717e500e5637cabb829e1b487f955491efaf) Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* sato/images: Add ptest imageRichard Purdie2016-03-021-0/+6
| | | | | | | | | | | We need an image containing the ptest packages for testing purposes. This adds such an image based on sato-sdk. We did try appending this in the autobuilder but it creates too much confusion about what is going on, and increases build time due to lack of parallelisation. (From OE-Core rev: 0f3ca0b4cae7d17d7b2d53cc433e87e1d148cdfb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* qt4: remove recipes and classesAlexander Kanavin2016-01-071-5/+1
| | | | | | | | | | | | Qt4 is no longer supportd upstream, but it is still needed for LSB compliancy. Qt4 recipes have been moved to a separate meta-qt4 layer to be consistent with meta-qt3 and meta-qt5. (From OE-Core rev: cb89d2b25b4edb1241bc5426a69a6bc44df9be2c) Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* arch-mips.inc: Change definition of TRANSLATED_TARGET_ARCHMark Hatle2015-01-291-0/+1
| | | | | | | | | | | | | | | | | | | | | | | [YOCTO #7230] In certain system configurations TRANSLATED_TARGET_ARCH will not expand in the right order for gcc-cross-candian-mips64n32 to be generated properly. This will cause SDKs to fail to generate properly. Changing the global definition of TRANSLATED_TARGET_ARCH always expands the ABIEXTENSION, which causes the OVERRIDES to pick it up as well. This effectively defines a new class of overrides for the 'n32'. The side effect is that we need to duplicate some mips64 overrides, and redefine others that were previously 'n32' or 'mips64' exclusive to have the correct semantics. (From OE-Core rev: 4b3a2b703b20583bd107f00a297d972e9bfb514a) Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk: Use kernel-devsrc to ensure kernel module builds workRichard Purdie2014-12-211-1/+1
| | | | | | | | | | With the move of the kernel source to the kernel-devsrc, we need this package to ensure the kernel module sanity tests made on core-image-sato-sdk continue to pass. Therefore update the name of the package included in the image. (From OE-Core rev: 51c19b97f7282eaba0a6f6b04703a62a3fea2b4a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk: Drop qt4 on mips64Richard Purdie2014-03-301-1/+4
| | | | | | | | qt4 doesn't build on mips64 so don't include it in sato-sdk images. (From OE-Core rev: 900584946698b5bb2c459ad9555709665843be2c) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-tools-debug: split out Eclipse packagesPaul Eggleton2013-03-231-1/+1
| | | | | | | | | | Split out the packages added for Eclipse remote debugging to a separate package group so that we can avoid pulling them in if not using Eclipse. Fixes [YOCTO #3251]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image: Add hwcodecs IMAGE_FEATURERichard Purdie2013-01-241-1/+1
| | | | | | | | | | | Currently hardware codecs are being injected in rather ugly ways and end up either in no or all images. This adds a dedicated IMAGE_FEATURE for them based on the MACHINE_HWCODECS variable. We may need to refine this in due course but this patch at least illustrates the concept. (From OE-Core rev: 1cb370587fd72e3f0f69678748108cc4116767fb) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-console: removePaul Eggleton2012-09-041-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | This provides one package group, packagegroup-core-apps-console, which is usually brought in by adding "apps-console-core" to IMAGE_FEATURES. Aside from the naming inconsistencies, this is a group of mostly unrelated packages, none of which are actually "apps". Handling each one: * dbus: should mostly be brought in by package runtime dependencies * avahi-daemon: if you are using packagegroup-base (as all images that inherit from core-image do) this is brought in by having "zeroconf" in DISTRO_FEATURES. * portmap: not very useful by itself; should be brought in by selecting NFS server/client through other means. * psplash (or whatever SPLASH is set to): this has been changed to be an explicit item "splash" in IMAGE_FEATURES. Since this is a fairly fundamental feature, a piece of code has been added to automatically handle this for images still using apps-console-core (and show a warning). (From OE-Core rev: 592d6e602466628d10704835a7b07d3d713f58e1) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-x11*: adjust X11 package groupsPaul Eggleton2012-09-041-0/+2
| | | | | | | | | | | | | | | | | | | Now the Sato pieces have been moved out, rebase packagegroup-core-x11 on packagegroup-x11-mini but using the structure/contents of meta-oe's task-x11 so that it can replace that; rename packagegroup-core-x11-mini to packagegroup-core-x11-base and pull in the xserver/utils packages via packagegroup-core-x11, and move both of these recipes under recipes-graphics. x11-mini is renamed to x11-base as it's what people should build on top of and since x11-mini is newer, the corresponding IMAGE_FEATURES item is less likely to be used in existing user recipes. (From OE-Core rev: 0cc9ced7d96b960994b0671095bc74becfc55e2c) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* packagegroup-core-x11: move out Sato applicationsPaul Eggleton2012-09-041-1/+1
| | | | | | | | | | | | | | Move Sato applications to packagegroup-core-x11-sato. Note that this eliminates both the apps-x11-core and apps-x11-games IMAGE_FEATURES; in practice it is unlikely these were useful to anyone outside of the Sato images however. (From OE-Core rev: 46cc375f29d5ecac7311613514a474f288d7c781) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/core-image: remove *_IMAGE_FEATURES variablesPaul Eggleton2012-09-043-11/+7
| | | | | | | | | | | | | | | | | This indirection does not add anything in terms of configuration and only serves to increase confusion; and given the nature of these it is unlikely they are being used outside of OE-Core. Change the sato-sdk and sato-dev images to be based on the main Sato image (avoiding the need for a common SATO_IMAGE_FEATURES variable) and eliminate all references to them. Fixes [YOCTO #2458]. (From OE-Core rev: 6488842b0d03cfec9f8675eca5a2e05675decf66) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* classes/core-image: remove SSHSERVER_IMAGE_FEATURESPaul Eggleton2012-09-041-3/+1
| | | | | | | | | | | | | This variable was added in the very same commit that added a mechanism that makes it obsolete: if you have dropbear and you want openssh, you just add ssh-server-openssh to your IMAGE_FEATURES and it will replace dropbear via IMAGE_FEATURES_REPLACES_. (From OE-Core rev: 6c78d99cc2e54a99af22357d7567f64e864949b9) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-*.bb: Remove usage of EXTRA_IMAGE_FEATURES from some .bb filesRobert P. J. Day2012-07-101-2/+2
| | | | | | | | | | | | Replace the usage of EXTRA_IMAGE_FEATURES in a small number of .bb files with IMAGE_FEATURES, and leave the use of EXTRA_IMAGE_FEATURES for developers in their local.conf files, to avoid the possibility of undesirable side effects. (From OE-Core rev: 347fc6e82a3d1c1ac7dbabd9e5cdd08abd864bfb) Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-*: remove copyright noticesPaul Eggleton2012-07-103-9/+0
| | | | | | | | | | | | These image recipes are meant to be examples that people can copy and modify completely for their own purposes, and most of them are so trivial they don't really need copyright notices anyway, so trim them off. (From OE-Core rev: 22db8917f6301595a48f6dcbcccc27627c8a3941) Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* image/core-image: Handle conflicting IMAGE_FEATURES.Lianhao Lu2012-07-031-0/+2
| | | | | | | | | | | | | | | | | IMAGE_FEATURES such as 'ssh-server-dropbear' and 'ssh-server-openssh' can't be both enabled. User can use the following variables to define the relationship of image features: IMAGE_FEATURES_REPLACES_foo = "bar" means including image feature "foo" would replace the image feature "bar". IMAGE_FEATURES_CONFLICTS_foo = "bar" means including both image features "foo" and "bar" would cause an parsing error. (From OE-Core rev: e36d12a9c1cf69540079e48a1dfadbc343758e48) Signed-off-by: Lianhao Lu <lianhao.lu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image*sdk: Add kernel-dev to sdk imagesDarren Hart2012-07-031-0/+3
| | | | | | | | | | | | | | | | While sdk images already have dev-pkgs included, the kernel-dev package is special and does not get installed. Add kernel-dev explicitly to the *sdk image recipes. Note: We have to be careful with "IMAGE_INSTALL +=" as it must appear after "inherit core-image" which makes an "IMAGE_INSTALL ?=" assignment. (From OE-Core rev: 337428316de3612a8e1efa70b3a4ba7cb6e058d2) Signed-off-by: Darren Hart <dvhart@linux.intel.com> CC: Jessica Zhang <jessica.zhang@intel.com> CC: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk: typo in DESCRIPTIONBeth Flanagan2012-04-161-1/+1
| | | | | | | | | Fix for a minor type in DESCRIPTION (From OE-Core rev: 25a997ca9b24d9265b62717fd01ebb26e7d21bba) Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Hob: Modify Image DescriptionsElizabeth Flanagan2012-04-063-8/+9
| | | | | | | | | | | Fixes [YOCTO #2227] I've updated the image descriptions per the bug description. (From OE-Core rev: 479b020edbc609c3ae1e3846e9e0d1643ac10059) Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-foo: add description to each image bb fileShane Wang2012-01-243-1/+8
| | | | | | | | | Add DESCRIPTION to each image bb file according to poky reference manual for Hob2 use later. (From OE-Core rev: 05a7c022e613f35de8ce47bb667140a7ce47fcea) Signed-off-by: Shane Wang <shane.wang@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove -directdisk.bb recipesSaul Wold2011-07-272-18/+0
| | | | | | | (From OE-Core rev: bdcd377eb54b5af34151b7c20459771901a65f4b) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Remove -live.bb recipesSaul Wold2011-07-272-22/+0
| | | | | | | (From OE-Core rev: 3b29e2c94cb696a22602f99d7714950a38b4eb8e) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* core-image-sato-sdk: ensure testapps is part of sdk imageSaul Wold2011-06-091-1/+3
| | | | | | | (From OE-Core rev: fd8967d30c41d8efd6333b5670022e65c5044f18) Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-lsb override to linuxstdbaseRichard Purdie2011-04-213-3/+3
| | | | | | (From OE-Core rev: 73a227a738da17229baac142ccd889c7929402ba) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*Richard Purdie2011-04-2111-40/+40
| | | | | | (From OE-Core rev: 560b04181d8f51d189b99f01a72f17210dadf7a3) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* poky-image-sdk* renamed to poky-image-sato-sdk*Saul Wold2011-01-255-20/+20
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* poky-image*-dev: Add -dev Images contianing headers and librariesSaul Wold2011-01-211-0/+9
| | | | Signed-off-by: Saul Wold <sgw@linux.intel.com>
* Add recipe for sdk directdisk targetJessica Zhang2010-10-111-0/+9
| | | | Signed-off-by: Jessica Zhang <jessica.zhang@intel.com>
* poky-image: Set LICENSE field for the image recipes (note this doesn't apply ↵Richard Purdie2010-09-075-0/+10
| | | | | | to the image contents, just the recipe and code used Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* task-poky-qt: create a task and add to poky-image-sdkSaul Wold2010-09-031-1/+1
| | | | | | Fixes [BUGID #260] Signed-off-by: Saul Wold <Saul.Wold@intel.com>
* Major layout change to the packages directoryRichard Purdie2010-08-275-0/+39
Having one monolithic packages directory makes it hard to find things and is generally overwhelming. This commit splits it into several logical sections roughly based on function, recipes.txt gives more information about the classifications used. The opportunity is also used to switch from "packages" to "recipes" as used in OpenEmbedded as the term "packages" can be confusing to people and has many different meanings. Not all recipes have been classified yet, this is just a first pass at separating things out. Some packages are moved to meta-extras as they're no longer actively used or maintained. Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
generated by cgit v1.2.3-54-g00ecf (git 2.39.0) at 2024-11-12 03:07:37 +0000