| Summary: | native.bbclass: make TOOLCHAIN_OPTIONS empty | ||
|---|---|---|---|
| Product: | [Build System, Metadata & Runtime] OE-Core | Reporter: | Robert Yang <liezhi.yang> |
| Component: | core | Assignee: | Robert Yang <liezhi.yang> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | bluelightning, jessica.zhang, meta.mr.watcher, meta.watcher |
| Version: | 1.2 | ||
| Target Milestone: | 1.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | --- | |
The native pkg doesn't need the TOOLCHAIN_OPTIONS, but it maybe used by native pkgs, for example: The cmake.bbclass uses TOOLCHAIN_OPTIONS: OECMAKE_C_FLAGS ?= "${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} ${CPPFLAGS}" and TOOLCHAIN_OPTIONS is: TOOLCHAIN_OPTIONS = " --sysroot=${STAGING_DIR_TARGET}" If a native pkg inherits cmake.bbclass, then: TOOLCHAIN_OPTIONS = " --sysroot=" and OECMAKE_C_FLAGS would be: ${HOST_CC_ARCH} --sysroot= ${CPPFLAGS} This would cause unexpected errors, I think that we can make TOOLCHAIN_OPTIONS empty in native.bbclass since native pkgs doesn't need it.