RFC Per-package SDK and target directories
Get series with b4
b4 am 20171107205558.315ce04c@windsurfVersions newest first
- v1 RFC Latest0 of 4 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 4 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [RFCv1 0/4] Per-package SDK and target directories
Hello,
Quoted 7 lines · Arnout Vandecappelle
Quoted 3 lines
in
package/pkg-generic.mk. But of course, we need to exclude the host-ccache package from this, otherwise we would have a circular dependency. Do you want to try something like this?Ha, I didn't understand the original problem but now I see. The issue is that
ccache is part ofDEPENDENCIES_HOST_PREREQ, andDEPENDENCIES_HOST_PREREQis *not* added to each package's DEPENDENCIES,
Exactly.
Quoted 7 lines
instead it is added to the
core-dependencies target and each package depends on that. It's an easy way to avoid circular dependencies, I guess.So I think the proper solution would be to add
DEPENDENCIES_HOST_PREREQto the
dependencies of all packages except themselves, similar to how it's done for toolchain.
Isn't this DEPENDENCIES_HOST_PREREQ thing a bit crappy in the first place? Why isn't host-ccache simply added as a dependency of all packages, except itself?
Another example is that today, host-lzip is always built at the beginning of build, even if you're not building any package that needs the lzip "decompressor".
So perhaps this calls for a little bit of rework in this area, no?
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com