linux/poky.git/meta/conf/bitbake.conf, branch 1.1_M3.final

bitbake.conf/qemux86-64: Automate TRANSLATED_TARGET_ARCH

2011-08-04T01:47:47+00:00

(From OE-Core rev: 6def7129cf7580a935c05cc05b7f803812d5bb18) Signed-off-by: Richard Purdie

bitbake.conf: Add SDK_PACKAGE_ARCHS

2011-08-02T13:32:11+00:00

Add SDK_PACKAGE_ARCHS to avoid the sed operations we were previously doing inside of the variouns populate_sdk functions and related items. Also add documentation to populate_sdk to explain when the various functions are expected to be doing. Finally fix a bug in populate_sdk_rpm where the wrong value was being set, noticed while working on this change. (From OE-Core rev: 587c1d5bac71fa6faa65ee3a271391cbf931e8f7) Signed-off-by: Mark Hatle Signed-off-by: Richard Purdie

bitbake.conf: remove PACKAGE_EXTRA_ARCHS_tune-XXX default

2011-08-01T13:16:54+00:00

Because of the way BitBake handles ??= under certain circumstances, this default setting ends up stepping all over the real setting from the arch include file. Since virtually all arch include files or tune files define a real value for this we shouldn't need to have a default (or it needs to be done in a different way). (From OE-Core rev: 6c43ca6fc6a7fffc84cf28684cac0c0eb4129902) Signed-off-by: Paul Eggleton Acked-by: Kumar Gala Signed-off-by: Khem Raj Signed-off-by: Richard Purdie

multilib: Add support for compiling recipes against multiple ABIs

2011-07-27T15:18:40+00:00

This patch adds the core multilib class which can be used along with a parameter specifying the mutlilib to use in BBCLASSEXTEND. The MLPREFIX variable is added and can be used in cases where its too difficult to dynmaically work out where a mutltilib prefix is needed to be added to a variable. This includes: * SHLIBSDIR and PACKAGE_ARCH fixes from Lianhao Lu. * PACKAGE_DYNAMIC mapping from Yu Ke * PACKAGE_INSTALL mapping from Yu Ke * RPROVIDES mapping from Yu Ke * TARGET_VENDOR fix from Mark Hatle * Ignorning *-native-runtime dependnecies as well as *-native from Yu Ke * Map PKG and ALLOW_EMPTY from Dongxiao Xu * Ensure RCONFLICTS and PKG field dependencies are remapped (from Dongxiao Xu) * Ensure PN and MLPREFIX are set at the same time to ensure consistent BPN values (Yu Ke) (From OE-Core rev: 5d9453049915db48ec4b5972e12287417ebb61a2) Signed-off-by: Yu Ke Signed-off-by: Xu Dongxiao Signed-off-by: Lianhao Lu Signed-off-by: Richard Purdie

Move architecture specific TARGET_OS mangling into tune files

2011-07-25T13:36:30+00:00

(From OE-Core rev: f10a3457cdfbb4a94978da998d178d4254632fa7) Signed-off-by: Richard Purdie

conf/machine/include: Start to fill out architecture specific tune include files and tune features

2011-07-25T13:36:30+00:00

These changes revolve around the idea of tune features. These are represented by 'flag' strings that are included in the TUNE_FEATURES variable. Any string included in TUNE_FEATURES should also add a TUNEVALID[] entry so we can know which flags are available in TUNE_FEATURES and have documentation about what the flags do. We will add sanity code to error if flags are listed in TUNE_FEATURES but are not documented in TUNEVALID. A given tune configuration will want to define one or more predetermined sets of _FEATURE flag lists. These are defined in the form TUNE_FEATURES_tune-. For defined tune configuation, should be added to the AVAILTUNE list so that we can determine what tune configurations are available. Flags cannot be used in this case as with TUNEVALID since its useful to be able to build up tune lists from other TUNE_FEATURES_tune-yyy options. A given tune configuration may also define PACKAGE_EXTRA_ARCHS_tune- and BASE_LIB_tune- to control the multilib location. All options can be overridden by the distro or local user configuration. (From OE-Core rev: 5f9d56bd64997b93ed7e46c117851002a0556654) Signed-off-by: Richard Purdie

bitbake.conf/classes: Variable cleanup

2011-07-25T13:36:30+00:00

This patch removes the variables BASE_PACKAGE_ARCH, BASEPKG_HOST_SYS, BASEPKG_TARGET_SYS and also removes the immediate assignments in several core classes as these are no longer required. This should make it clearer what some of the core variables do and simplfy some overly complex and confusing class code. (From OE-Core rev: d5521be2dcbaf213c140b0d12a4176380874426b) Signed-off-by: Richard Purdie

conf/machine/include: Set TUNE_CCARGS instead of TARGET_CC_ARCH

2011-07-25T11:06:30+00:00

Since we're updating the tune file format, it makes sense to abstract the compiler tune arguments at this point too. This means that should these need to be overridden at any point, the original values can still be obtained in a similar manner to the other TUNE* variables. Whilst this isn't strictly necessary for any current need, its likely good practise to standardise this behaviour. (From OE-Core rev: 3a3c69a1bc3cf0b6f6a3b13d86c12ed21798d48e) Signed-off-by: Richard Purdie

conf/machine/tune: Overhaul tune include file variables

2011-07-25T11:06:30+00:00

There is currently consideradble confusion over how the tune files operate and how these interact with the rest of the build system. This update/overhaul changes things so the tune files are primarily resonsible for setting: TUNE_ARCH - What was formerly set as TARGET_ARCH and is the value that represents the architecture we're targetting. TUNE_PKGARCH - The value that represents the tune confuration that this set of tune parameters results in. This allows the significant improvement that the core can now always determine the target architecture value, even when TARGET_ARCH needs to be reset to something different and likewise, there is one package architecture variable the core can reference allowing simplification of the BASE_PACKAGE_ARCH, PACKAGE_ARCH and FEED_ARCH variables. (From OE-Core rev: a10de4cf8b424ee95c8e283e75d486be5b3b8eac) Signed-off-by: Richard Purdie

bitbake.conf/cross.bbclass: Add ability to dynamically change library location

2011-07-25T11:06:30+00:00

Add the ability to dynamically change the library directory from "lib" to other values. This allows the tune files to specifiy altnerative ABIs which can be dynamically enabled by the multilib BBCLASSEXTEND code. A variety of approaches have been attempted with this, the immediate expansions in cross.bbclass being problematic as they are they are expanded before the bbclass extend event hander runs. This approach ensures the ${baselib} variable is retained in the expressions resolving that complication. Derived from some ideas from Mark Hatle. (From OE-Core rev: aeea22da699b276a97ca1a17e3c53176c9afd9de) Signed-off-by: Richard Purdie