summaryrefslogtreecommitdiff
path: root/meta/conf
AgeCommit message (Collapse)AuthorFiles
2013-08-26linux-libc-headers: update to v3.10Bruce Ashfield1
Now that the 3.10 kernel has been released we can bump the libc-headers to that version and remove the 3.8 variant. Userspace compatibility is maintained through kernel versions, we also make the single 3.10 version the toolchain default. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-23default-providers: Set the preferred provider for bluezCristian Iorga1
There is a need for a default provider for bluez now that bluez5 recipe is also present. After the introduction of bluez5 recipe, the following warnings are displayed: "NOTE: multiple providers are available for runtime libasound-module-bluez (bluez4, bluez5) NOTE: consider defining a PREFERRED_PROVIDER entry to match libasound-module-bluez" Upon debug, bitbake shows: DEBUG: checking PREFERRED_PROVIDER_bluez4 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez4-4.101-r5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7 (value None) against ['bluez4', 'bluez5'] DEBUG: checking PREFERRED_PROVIDER_bluez5-5.7-r0 (value None) against ['bluez4', 'bluez5'] Bitbake is faced with the question "what should provide libasound-module-bluez?" which is a runtime name. It needs to try and find a PREFERRED_PROVIDER entry which matches this but those use *build time* naming. So it converts "libasound-module-bluez" into the canonical ${PN} of bluez4 and bluez5 and then tries to look those up. What it actually should do is go one step further of mapping bluez4/bluez5 into the virtual/bluez but that does not happen. Bug opened on this issue: YB5044 https://bugzilla.yoctoproject.org/show_bug.cgi?id=5044 [YOCTO #5030] Signed-off-by: Cristian Iorga <cristian.iorga@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22Drop darwin8/darwin9 usageRichard Purdie1
There were darwin8/darwin9 overrides spinkled in the code from times gone by. Lets settle on the darwin override and remove the others since its pointless duplication. We always inject darwin into OVERRIDES if needed in the darwin8/9 cases. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22bitbake.conf: Work around dev symlink problems on darwinRichard Purdie1
On darwin, we have: libxxx.dylib -> libxxx.Y.dylib compared to Linux which has: libxxx.so -> libxxx.so.Y Our ordering of PACKAGES with -dev first and then ${PN} makes it impossible to match the files correctly using simple globbing. This makes darwin targets completely broken since both the libs and the dev symlinks end up in ${PN}-dev. Whilst this commit is a hack, it at least puts the files into ${PN} and allows the builds to be used. Symlinks don't take up much space so this isn't the end of the world. I'm open to better solutions to this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22bitbake.conf/classes/gcc: Don't hardcode -nativesdkRichard Purdie1
Hardcoding -nativesdk as the sdk package architecture is inflexible. We may have multiple different target OS and we need a way to be able to separate them. Turning this into a configurable value allows the flexibility we need to build different SDKMACHINEs with different OS targets. The commit should have no behaviour change, just makes things more configurable. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianRichard Purdie1
The gettext handling of USE_NLS has become a bit tricky to understand, or alter from the SDK context. This patch introduces a SDKUSE_NLS which can be set to configure a given SDK/ADT to use NLS or not. This is independent of the target system NLS usage. The code in gettext.bbclass is therefore simplified and the classes themselves now set USE_NLS to appropriate values. No NLS is used for native, cross and crosssdk since it is never used there and would just increase build time. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-08-22package_rpm.bbclass: NO_RECOMMENDATIONS supportMark Hatle2
Add NO_RECOMMENDATIONS support. A way to disable all recommended packages from being installed. This will help shrink the size of the resulting filesystem. Add documentation on NO_RECOMMENDATIONS and BAD_RECOMMENDATIONS. Note, using NO_RECOMMENDATIONS has side effects such that kernel-modules may not have been installed. A user will need to manually add to their image any kernel-modules required to be on the image for functionality. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-22image.bbclass: Add basic support for PACKAGE_EXCLUDEMark Hatle1
Add the foundation for the PACKAGE_EXCLUDE support. As part of this work, it was noticed that the PACKAGE_INSTALL and PACKAGE_INSTALL_ATTEMPTONLY were still using he 'normal' version for dependencies. This should no longer be necessary as of the change in the way the complementary package groups (dev, dbg, ptest and others) are defined. By making this change the dependency tree is more correct than before, and gives the ability for manipulating PACKAGE_INSTALL and PACKAGE_INSTALL_ATTEMPTONLY, while adjusting the dependencies at the same time. Warning messages will be generated if the user is trying to exclude a package that was previously in the PACKAGE_INSTALL or PACKAGE_INSTALL_ATTEMPTONLY variables. (See additional commits for package manager specific support.) Add documentation on PACKAGE_EXCLUDE and related variables. Signed-off-by: Mark Hatle <mark.hatle@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-20default-distrovars.inc: Add 'DISTRO_FEATURES_DEFAULT' variableOtavio Salvador1
When making distributions based on the default distro-less config, it is useful to be able to reuse the default DISTRO_FEATURES options without the need of duplication. The new variable, DISTRO_FEATURES_DEFAULT, allow this reuse and customization. So distros can include 'default-distrovars.inc' and use: ,----[ Use example ] | DISTRO_FEATURES ?= "${DISTRO_FEATURES_DEFAULT} myfeature" `---- Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-20qemuppc: Change default tune to 74xxKhem Raj1
We use mac99 as platform for qemuppc lets choose a tuning thats appropriate for it Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-20tune-ppc7400.inc: Add tune fileKhem Raj1
This is appropriate tune for mac99/g4 platform that we use for emulating qemuppc Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-16qemu, default-providers: Add mesa as default virtual/eglMartin Jansa2
* it's safer to select it consistently with virtual/libgl* providers Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-13mesa: fix and enable out-of-tree buildsRoss Burton1
One patch (submitted upstream) for when Gallium is enabled, and another (inappropriate for upstream) to fix out-of-tree builds with 0003-EGL-Mutate-NativeDisplayType-depending-on-config. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-08-09separatebuilddir: add commentsRoss Burton1
Add a comment explaining the libproxy failure, and note that wpa-supplicant doesn't support B!=S. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-30csl-versions.inc: instruct user to check local.confLaurentiu Palcu1
In case the compiler version cannot be extracted instruct user to check that the toolchain supports MACHINE's architecture and that the latter is set correctly in local.conf. [YOCTO #4901] Signed-off-by: Laurentiu Palcu <laurentiu.palcu@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-27external-sourcery: add missing providersSaul Wold1
Addess the issue with multiple .bb providers ERROR: Multiple .bb files are due to be built which each provide virtual/libc (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. ERROR: Multiple .bb files are due to be built which each provide virtual/arm-none-linux-gnueabi-libc-for-gcc (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. ERROR: Multiple .bb files are due to be built which each provide virtual/libiconv (/srv/hdd/releases/dylan/meta/recipes-core/eglibc/eglibc_2.17.bb /srv/hdd/releases/dylan/meta/recipes-core/meta/external-sourcery-toolchain.bb). This usually means one provides something the other doesn't and should. Thanks to Kergoth (Chris Larson) and Lpapp (Lazslo) [YOCTO #4908] Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-27classes/rootfs_rpm: implement BAD_RECOMMENDATIONS for RPMPaul Eggleton1
Add support for the BAD_RECOMMENDATIONS variable that can be used to prevent specific packages from being installed via an RRECOMMENDS relationship when using the RPM backend. (Previously this functionality was only available when using ipk packaging.) In the process this moves the defaulting of BAD_RECOMMENDATIONS (as empty) to bitbake.conf since it is no longer specific to the ipk backend, as well as unifying some of the code that creates the configuration for smart for use on the host and target. Fixes [YOCTO #3916]. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-18local.conf.sample.extended: add example for EXTRA_USERS_PARAMSChen Qi1
Add detailed explanation of EXTRA_USERS_PARAMS which is used for image level user/group configuration. [YOCTO #4074] Signed-off-by: Chen Qi <Qi.Chen@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-10security_flags: Add addition recipes to the non pie listSaul Wold1
Create a local SECURITY_NO_PIE_CFLAGS to cover the recipes that have issues with with pic and pie cflags set. Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05tcmode-default: Pin eglibc to 2.18Khem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05distro/conf: Drop libc-libm-bigKhem Raj2
Its gone with eglibc 2.18 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-05layer.conf: Bumping LAYERVERSION_coreElizabeth Flanagan1
Bumping LAYERVERSION_core to denote where meta-toolchain* is being depreciated. This goes back to my RFC: http://comments.gmane.org/gmane.comp.handhelds.openembedded.core/39016 As we are removing meta-toolchain* and replacing it with bitbake <imagename> -c populate_sdk this causes issues with those of us who need to do automated builds both on the current development branch and on prior development branches. Example: For prior releases, I need to build meta-toolchain*. Without having a simple way to figure out where this is no longer the case, I (and other folks who run automated builds) end up having to jump through a lot of hoops trying to figure out where this layer changed. Utilizing LAYERVERSION_* to do it makes sense as there is a significant change that would cause issues for build engineers. Signed-off-by: Elizabeth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02security_flags: Add the compiler and linker flags that enhance securitySaul Wold1
These flags add addition checks at compile, link and runtime to prevent stack smashing, checking for buffer overflows, and link at program start to prevent call spoofing later. This needs to be explicitly enabled by adding the following line to your local.conf: require conf/distro/include/security_flags.inc [YOCTO #3868] Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02local.conf.sample.extended: Add example line for enabling security flagsSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-07-02seperatebuilddir: cogl and clutter build out of treeRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-27tcmode-default: Set GCC 4.8 as defaultSaul Wold1
Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-17licences: Add SGI licenseDiego Rondini1
Add SGI license used, for example, in glmark2 Signed-off-by: Diego Rondini <diego.ml@zoho.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-17site.conf.sample: Update git proxy instructionsRichard Purdie1
Somewhere along the line this change got lost, update the git proxy examples to match the current usage. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-17local.conf.sample: use ?= to assign BB_ENV_EXTRAWHITE variablesJesse Zhang2
Use ?= so that the BB_ENV_EXTRAWHITE variables can be overridden from the environment. [YOCTO #4367] Signed-off-by: Jesse Zhang <sen.zhang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14documentation.conf: Drop variables for class that no longer exists in OE-CoreRichard Purdie1
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14classes/conf: Add eventmasks for event handlersRichard Purdie2
Now that bitbake supports masking events for event handlers, lets use this so event handlers are only called for events they care about. This lets us simplify the code indentation a bit at least as well as mildly improving the event handling performance. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14sanity.conf: Update minimum bitbake version requirement to 1.19.1 for ↵Richard Purdie1
bitbake-worker This is due to the need to rely on bitbake-worker being present going forwards. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-14bitbake.conf: Add extra fakeroot parametersRichard Purdie1
In order to correctly handle fakeroot at the bitbake level we need some extra information which we provide with these new variables. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-13gzip : upgrade to 1.6Andrei Dinu1
tcmode-default: Update gzip PREFFERED_VERSION to 1.6 Signed-off-by: Andrei Dinu <andrei.adrianx.dinu@intel.com> [sgw - updated tcmode-default] Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-12tune-cortexa*.inc: fix tunings for cortex a5, a7, a8, a9, a15 machines.Andy Voltz7
Using CORTEX_ID variable reference in the tuning overrides did not work. This reverts those changes, and adds a tuning file for the cortex-a5. Revert "tune-cortexa5.inc: Add tune file for cortex-a5" Revert "tune-cortexa.inc: create a common include for cortex-a armv7a tuning" Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-06-07tune-cortexa5.inc: Add tune file for cortex-a5Andy Voltz1
Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-07tune-cortexa.inc: create a common include for cortex-a armv7a tuningAndy Voltz6
The tuning files for the cortex-a* processors are mostly identical for the A7,A8,A9,A15 processors. Rework these files to use a CORTEX_ID variable to setup the tuning for each specific processor. Signed-off-by: Andy Voltz <andy.voltz@timesys.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-06-07defaultsetup.conf: remove INHERIT_INSANERobert Yang1
The insane has been inherited by package.bbclass and becomes a requirement, so we can remove it from defaultsetup.conf. Note: You can decide whether to take this patch or not. [YOCTO #3190] [YOCTO #4396] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-31qemu*: restrict NFSD to linux-yocto onlyBruce Ashfield1
In the current releases, not all linux-yocto derived kernels have NFS support, or NFS support fragments availble. To ensure that derived kernels like linux-yocto-cutom continue to work against poky-lsb, we can make the KERNEL_FEATURE append more specific to the linux-yocto recipe. Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-21image_types.bbclass: remove the old imagesRobert Yang1
Remove the old image before the new one generated to save disk space when RM_OLD_IMAGE is set to 1, this is an easy way to keep the DEPLOY_DIR_IMAGE clean. [YOCTO #4391] Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-16machine/qemumips64: Add machine definitionKhem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-15bitbake.conf: define empty EXTRA_IMAGE_FEATURES before using themMartin Jansa1
* fixes build without EXTRA_IMAGE_FEATURES defined: ERROR: '${EXTRA_IMAGE_FEATURES}' in IMAGE_FEATURES is not a valid image feature. Valid features: dbg-pkgs .... Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-12bitbake.conf: export STRINGSMartin Jansa1
* remove STRINGS export from systemd Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-10bitbake.conf: update way to set default ROOT_HOMEKang Kai1
Use "??=" to set default ROOT_HOME. It can be overwrote by developer with "?=" in any layer and at same time it also can be overwrote in local.conf. Signed-off-by: Kang Kai <kai.kang@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09eglibc/machine-sdk: Drop SDK_GLIBC_ADDONSRichard Purdie3
We no longer change GLIBC_ADDONS per target so we no longer need to special case the SDK settings for it either. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-09bitbake.conf: Use casting to ensure valid comparisionRichard Purdie1
python3 is stricter about type comparisions so add an explicit cast to int() to ensure this code is portable. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2013-05-08tcmode-default.inc: Pin binutils to 2.23.2Khem Raj1
Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08qemu: Ensure kernel nfsd module is enabledSaul Wold1
This will ensure that qemu images that include the nfs-server package have the kernel feature correctly enabled Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08libgnome-keyring: remove, nothing in oe-core uses this anymoreRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
2013-05-08gnome-keyring: remove, nothing uses it in oe-coreRoss Burton1
Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Saul Wold <sgw@linux.intel.com>
generated by cgit v1.2.3 (git 2.25.1) at 2024-12-25 09:55:21 +0000