[OpenWrt-Devel] [PATCH 12/14] target/sdk: Fix handling of already built packages

Felix Fietkau nbd at openwrt.org
Sun Jan 3 11:21:18 EST 2016

On 2016-01-03 16:36, Daniel Dickinson wrote:
> Actually, in keeping with your comment about rather having a fork of the 
> source in SDKs, I'm thinking it would be better to rework all of this, 
> so that SDK's automatically ship the source, and figure out a better 
> mechanism for managing the recording of what is already built (probably 
> just a plain text file) which can be easily 'overridden' by removing the 
> record (or taking an approach similar to feeds.conf.default, only with a 
> generated file instead of one in the source tree).
> I hadn't thought of the issue of people shipping binary-only SDK's and 
> think that having the SDK have a copy of the source (but that doesn't 
> get in the way easy updates to the source) would be preferrable; my 
> object with the SDK was to build only what's needed, when it's needed, 
> rather than as means to ship binaries.  I was thinking more in terms of 
> internal common code, but see how it could easily get abused, in it's 
> current form.
I think the SDK should behave just like the normal build system. The
problem with relying on prebuilt stuff in the staging dir (or even the
build dir) is that quite often absolute path names leak into various
places of the build, making it impossible to relocate.

IMHO the only sane way to deal with that is to stop relying on prebuilt
stuff in build_dir or staging_dir/target-* entirely.

- Felix
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list