This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM64X: Yocto build offline

Part Number: PROCESSOR-SDK-AM64X

Tool/software:

Hello,

i am able to build the SDK with Yocto on a host machine with internet access, considering this manual: https://software-dl.ti.com/processor-sdk-linux/esd/AM64X/09_02_01_10/exports/docs/linux/Overview_Building_the_SDK.html

Now i want to build the SDK on a machine without internet access.

For the bitbake process i know i can set  BB_GENERATE_MIRROR_TARBALLS = "1"  which works quite well.

But what has to be done with the first build steps, espcially:


./oe-layertool-setup.sh -f configs/processor-sdk/<oeconfig-file>

This script also connect to internet and clones repositories? Furthermore some more action is done in this script.
What do i have to do to use this script on an offline machine?

  • Hi Sec,

    This script also connect to internet and clones repositories? Furthermore some more action is done in this script.
    What do i have to do to use this script on an offline machine?

    This script is pretty simple, it just clones a set of repositories and checks out specific revisions of those repositories, and sets up some config scripts. If you want to do offline builds the easiest would be to just run this `oe-layertool-setup.sh` script to let its do it's job, inside a clean folder, and then archive the entire directory structure into a tarball. You can then store this tarball or transfer it to another machine, and use it together with your mirror tarballs to do the builds.

    Note that some (few) recipes do some network access during the build phase, which is considered a bad practice but this is how those recipes where written, so you may run into this. See here for some more pointers on this: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1318189/sk-am62p-lp-failed-to-build-the-sdk-with-yocto-in-offline-environment You can mitigate some of those issues by leveraging Yocto's share state cache feature.

    Regards, Andreas