Lunch support for Linaro Android Builds
Android Developers typically use lunch for selecting a build configuration for local development.
Supporting to use lunch will increase ability of working with Linaro builds for developers and community and will eliminate one of the main differences of AOSP developer best practices.
Seems the main feature missing in lunch is selecting a linaro toolchain; lunch overwrites TARGET_TOOLS_PREFIX with the default prebuilt/ toolchain.
Adding feature to lunch to remember TARGET_TOOLS_PREFIX instead of overriding it would probably be the main change needed.
Example: TARGET_
Should remember the tools setting.
This feature should go upstream. Details best to be discussed on AOSP mailing list.
Blueprint information
- Status:
- Not started
- Approver:
- Zach Pfeffer
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for future
- Implementation:
-
Unknown
- Milestone target:
-
nearterm
- Started by
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
Notes:
[asac, Jan 16, 2012]: adding to backlog with medium prio to start with.
[asac, Jan 16, 2012]: < asac_> can we make lunch work? feels for "developers" it's a good tool so they can just type make; without TARGET_...
Meta:
Headline: Linaro Android added support for building it's build using the lunch command
Acceptance: lunch can be used to select a different toolchain; default toolchain selected by lunch will build Linaro Android; "lunch pandaboard; make boottarball usertarball systemtarball" works and produces images installable with lamc
