On Thu, 15 Sep 2011 15:08:26 -0500, Zach Pfeffer <zach.pfef...@linaro.org> wrote: > I'm writing up some notes on building Android from scratch and > replacing the kernel in an Android build from one built locally, and I > realized that's it a bit of a chore to extract the kernel config that > got used. I thought, it may make sense to provide an way in > android-build to control what gets used - which would make finding > this information easier since if would one of the configs that gets > passed to the build like TARGET_PRODUCT. Thoughts?
Hi, We could (fairly easily I imagine) make the actual config an artefact of the build. Then you could go to any build, grab the config, and so build the same thing locally. Passing it in would be ok, but I'm not sure we would want to make every build have the config specified as well as everything else? The only way that it would be universal would be if you had to specify this on every config, which seems to duplicate information inside the tree. Providing the config that was used as an artefact would be universal. I guess we even have a choice between providing the full .config, and just the name of the defconfig, if that's how the Android build system selects them. Thanks, James _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
