Toolchain tweaks
Get series with b4
b4 am 1377171968.6762.8.camel@tedVersions newest first
- v1 Latest28 patches 0 repliesNew
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/28 | package.bbclass: Fix handling of symlinks in debug packagesmeta/ | +6 | 0 replies | |
| 2/28 | crosssdk: Construct target_exec_prefix from prefix_nativesdkmeta/ | +1 | 0 replies | |
| 3/28 | populate_sdk_base: Allow sdk tar options to be overriddenmeta/ | +3 | 0 replies | |
| 4/28 | gettext: Improve USE_NLS handling for nativesdk/crosssdk/cross-canadianmeta/ meta/ meta/ +4 more | +14 | 0 replies | |
| 5/28 | libiconv: Extend to nativesdk and support non-linux targetsmeta/ | +4 | 0 replies | |
| 6/28 | gcc-cross-canadian-4.8: Enable PARALLEL_MAKEmeta/ | +0 | 0 replies | |
| 7/28 | gcc-package-sdk.inc: Use relative symlinks in libexec dirmeta/ | +4 | 0 replies | |
| 8/28 | gcc-package-sdk.inc: Allow executable extension to be overriddenmeta/ | +5 | 0 replies | |
| 9/28 | gcc-configure-sdk.inc: Don't build target-libgccmeta/ | +1 | 0 replies | |
| 10/28 | gcc: Drop gcc-cross4.inc, its pointless nowmeta/ meta/ meta/ +1 more | +4 | 0 replies | |
| 11/28 | gcc-cross-canadian-4.8: Allow elfutils to be a configurable dependencymeta/ | +3 | 0 replies | |
| 12/28 | gcc-cross-canadian-4.8: Add missing dependency on nativesdk-zlibmeta/ | +1 | 0 replies | |
| 13/28 | gcc-cross-canadian: Merge 4.7 and 4.8 recipes into common includemeta/ meta/ meta/ | +19 | 0 replies | |
| 14/28 | Revert "nativesdk: inherit relocatable"meta/ | +0 | 0 replies | |
| 15/28 | bitbake.conf/classes/gcc: Don't hardcode -nativesdkmeta/ meta/ meta/ +4 more | +22 | 0 replies | |
| 16/28 | gcc-cross: Fold common configuration into gcc-cross.incmeta/ meta/ meta/ | +12 | 0 replies | |
| 17/28 | gcc-cross-initial: Fold common configuration into gcc-cross-initial.incmeta/ meta/ meta/ | +2 | 0 replies | |
| 18/28 | gcc-runtime: Fold common configuration into gcc-configure-runtime.incmeta/ meta/ meta/ | +5 | 0 replies | |
| 19/28 | libgcc: Move common code to libgcc.incmeta/ meta/ meta/ | +145 | 0 replies | |
| 20/28 | gcc-target: Combine gcc-target-configure.inc, gcc-target-package.inc and other common codemeta/ meta/ meta/ +2 more | +155 | 0 replies | |
| 21/28 | gcc-*-cross.inc: Fold common configuration into gcc-cross.incmeta/ meta/ meta/ | +81 | 0 replies | |
| 22/28 | gcc-*-runtime.inc: Fold configuration into gcc-runtime.incmeta/ meta/ meta/ +2 more | +147 | 0 replies | |
| 23/28 | gcc-cross-canadian: Fold configure-sdk and package-sdk into the main .incmeta/ meta/ meta/ | +125 | 0 replies | |
| 24/28 | gcc-cross.inc: Clean up after mergemeta/ | +18 | 0 replies | |
| 25/28 | gcc-common.inc: Drop unused LIBGCCS_VAR variablemeta/ | +0 | 0 replies | |
| 26/28 | bitbake.conf: Work around dev symlink problems on darwinmeta/ | +9 | 0 replies | |
| 27/28 | Drop darwin8/darwin9 usagemeta/ meta/ meta/ | +1 | 0 replies | |
| 28/28 | chrpath: Add support for relocating darwin binariesmeta/ | +88 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
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