Skip to content

Toolchain tweaks

Richard Purdie openembedded-core 1 version New

Get series with b4
b4 am 1377171968.6762.8.camel@ted

Versions newest first

  1. v1 Latest28 patches 0 repliesNew

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/28package.bbclass: Fix handling of symlinks in debug packagesmeta/classes/package.bbclass+6 -00 replies
2/28crosssdk: Construct target_exec_prefix from prefix_nativesdkmeta/classes/crosssdk.bbclass+1 -10 replies
3/28populate_sdk_base: Allow sdk tar options to be overriddenmeta/classes/populate_sdk_base.bbclass+3 -10 replies
4/28gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianmeta/classes/cross-canadian.bbclass meta/classes/cross.bbclass meta/classes/crosssdk.bbclass +4 more+14 -50 replies
5/28libiconv: Extend to nativesdk and support non-linux targetsmeta/recipes-support/libiconv/libiconv_1.14.bb+4 -00 replies
6/28gcc-cross-canadian-4.8: Enable PARALLEL_MAKEmeta/recipes-devtools/gcc/gcc-cross-canadian_4.8.bb+0 -20 replies
7/28gcc-package-sdk.inc: Use relative symlinks in libexec dirmeta/recipes-devtools/gcc/gcc-package-sdk.inc+4 -10 replies
8/28gcc-package-sdk.inc: Allow executable extension to be overriddenmeta/recipes-devtools/gcc/gcc-package-sdk.inc+5 -20 replies
9/28gcc-configure-sdk.inc: Don't build target-libgccmeta/recipes-devtools/gcc/gcc-configure-sdk.inc+1 -10 replies
10/28gcc: Drop gcc-cross4.inc, its pointless nowmeta/recipes-devtools/gcc/gcc-cross.inc meta/recipes-devtools/gcc/gcc-cross4.inc meta/recipes-devtools/gcc/gcc-cross_4.7.bb +1 more+4 -50 replies
11/28gcc-cross-canadian-4.8: Allow elfutils to be a configurable dependencymeta/recipes-devtools/gcc/gcc-cross-canadian_4.8.bb+3 -20 replies
12/28gcc-cross-canadian-4.8: Add missing dependency on nativesdk-zlibmeta/recipes-devtools/gcc/gcc-cross-canadian_4.8.bb+1 -10 replies
13/28gcc-cross-canadian: Merge 4.7 and 4.8 recipes into common includemeta/recipes-devtools/gcc/gcc-cross-canadian.inc meta/recipes-devtools/gcc/gcc-cross-canadian_4.7.bb meta/recipes-devtools/gcc/gcc-cross-canadian_4.8.bb+19 -430 replies
14/28Revert "nativesdk: inherit relocatable"meta/classes/nativesdk.bbclass+0 -20 replies
15/28bitbake.conf/classes/gcc: Don't hardcode -nativesdkmeta/classes/cross-canadian.bbclass meta/classes/crosssdk.bbclass meta/classes/nativesdk.bbclass +4 more+22 -210 replies
16/28gcc-cross: Fold common configuration into gcc-cross.incmeta/recipes-devtools/gcc/gcc-cross.inc meta/recipes-devtools/gcc/gcc-cross_4.7.bb meta/recipes-devtools/gcc/gcc-cross_4.8.bb+12 -220 replies
17/28gcc-cross-initial: Fold common configuration into gcc-cross-initial.incmeta/recipes-devtools/gcc/gcc-cross-initial.inc meta/recipes-devtools/gcc/gcc-crosssdk-initial_4.7.bb meta/recipes-devtools/gcc/gcc-crosssdk-initial_4.8.bb+2 -20 replies
18/28gcc-runtime: Fold common configuration into gcc-configure-runtime.incmeta/recipes-devtools/gcc/gcc-configure-runtime.inc meta/recipes-devtools/gcc/gcc-runtime_4.7.bb meta/recipes-devtools/gcc/gcc-runtime_4.8.bb+5 -80 replies
19/28libgcc: Move common code to libgcc.incmeta/recipes-devtools/gcc/libgcc.inc meta/recipes-devtools/gcc/libgcc_4.7.bb meta/recipes-devtools/gcc/libgcc_4.8.bb+145 -2870 replies
20/28gcc-target: Combine gcc-target-configure.inc, gcc-target-package.inc and other common codemeta/recipes-devtools/gcc/gcc-configure-target.inc meta/recipes-devtools/gcc/gcc-package-target.inc meta/recipes-devtools/gcc/gcc-target.inc +2 more+155 -1580 replies
21/28gcc-*-cross.inc: Fold common configuration into gcc-cross.incmeta/recipes-devtools/gcc/gcc-configure-cross.inc meta/recipes-devtools/gcc/gcc-cross.inc meta/recipes-devtools/gcc/gcc-package-cross.inc+81 -820 replies
22/28gcc-*-runtime.inc: Fold configuration into gcc-runtime.incmeta/recipes-devtools/gcc/gcc-configure-runtime.inc meta/recipes-devtools/gcc/gcc-package-runtime.inc meta/recipes-devtools/gcc/gcc-runtime.inc +2 more+147 -1480 replies
23/28gcc-cross-canadian: Fold configure-sdk and package-sdk into the main .incmeta/recipes-devtools/gcc/gcc-configure-sdk.inc meta/recipes-devtools/gcc/gcc-cross-canadian.inc meta/recipes-devtools/gcc/gcc-package-sdk.inc+125 -1270 replies
24/28gcc-cross.inc: Clean up after mergemeta/recipes-devtools/gcc/gcc-cross.inc+18 -300 replies
25/28gcc-common.inc: Drop unused LIBGCCS_VAR variablemeta/recipes-devtools/gcc/gcc-cross.inc+0 -30 replies
26/28bitbake.conf: Work around dev symlink problems on darwinmeta/conf/bitbake.conf+9 -60 replies
27/28Drop darwin8/darwin9 usagemeta/conf/bitbake.conf meta/recipes-core/packagegroups/nativesdk-packagegroup-sdk-host.bb meta/recipes-devtools/e2fsprogs/e2fsprogs_1.42.8.bb+1 -60 replies
28/28chrpath: Add support for relocating darwin binariesmeta/classes/chrpath.bbclass+88 -500 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 00/28] Toolchain tweaks

Playing with meta-mingw, it was clear that there were some simple changes we could make to the core that would improve things for non-linux SDKs. This series includes those changes. Since I like pain, I also attempted a darwin build and have included some tweaks for that too.

When looking at the gcc recipes, it also became clear that we have way too many include files and the whole thing was a bit of a maze. The series has some changes in to combine various files together and simplify things.

I appreciate this may complicate moving things into meta-oe such as gcc 4.7. I would propose when we do that, we put them into recipes-gcc-<version> and include a snapshot of the .inc files at that time. The alternative is the continual copy and paste growth of the .bb files (libgcc being a more extreme example) which I don't think lends itself to future maintenance of the recipes.

There are some layers which for example use gcc-cross4.inc, they should just be able to switch directly to gcc-cross.inc. I think this applies to meta-arago-extras.

This also leads the way to possibly further unify and clean up some of the configuration (e.g. the do_configure_prepends) but I will leave that for another series when someone has some further time to spend on it.

Cheers,

Richard