[Buildroot] [PATCH] core/sdk: generate the SDK tarball ourselves

Peter Korsgaard peter at korsgaard.com
Fri Jun 15 18:12:12 UTC 2018

>>>>> "Trent" == Trent Piepho <tpiepho at impinj.com> writes:


 > So having extracted an SDK, in an automated CI script, how does one use
 > it?  I'll add it to the Docker container:

 > ARG sdk_file
 > ENV SDK=/mnt/sdk
 > ADD --chown=user:user ${sdk_file} ${SDK}

 > Now it needs to be relocated.  Something like:

 > RUN cd ${SDK}/buildroot-sdk.arm-buildroot-linux-gnueabihf-2018.02-00035-ge588bdd3e8 && ./relocate-sdk.sh

 > Is the problem with using this tarball apparent?  The dockerfile needs
 > to be hand edited on every single build to use the correct path to the
 > SDK.

Why not use a wildcard? E.G. cd ${SDK}/buildroot-sdk* && ./relocate-sdk.sh?

Nothing else should match the wildcard inside the container.

Bye, Peter Korsgaard

More information about the buildroot mailing list