RPI3b:-sh: apt-get: not found about build

[jbech-linaro]

Although you in theory could do optee_client development on the RPi3 itself, that's not something that is supported in our RPi3 setup. I.e., you do all development on your host machine and then put the (cross)compiled binaries on the RPi3.

apt is a Debian package manager, the root fs in our Rpi3 setup is custom build using Buildroot. So if/when you need to add packages to the root fs, you have to enable them in the Buildroot configuration and rebuild. Remember, this is a development setup, which is heavily stripped down. It's not a normal Linux distro.

[mlhh1103]

Although you in theory could do optee_client development on the RPi3 itself, that's not something that is supported in our RPi3 setup. I.e., you do all development on your host machine and then put the (cross)compiled binaries on the RPi3.

apt is a Debian package manager, the root fs in our Rpi3 setup is custom build using Buildroot. So if/when you need to add packages to the root fs, you have to enable them in the Buildroot configuration and rebuild. Remember, this is a development setup, which is heavily stripped down. It's not a normal Linux distro.

Oh, I see, should I bulid TEE-Supplicant in optee_client on the host machine, and put the compiled binaries on the RPI3 via NFS(which I already set)?

[jbech-linaro]

Oh, I see, should I bulid TEE-Supplicant in optee_client on the host machine, and put the compiled binaries on the RPI3 via NFS(which I already set)?

Yes, that's one way to do it. For people how hasn't configured NFS, they have to pull out the micro-SD card and repopulate the filesystem. Just make sure that you move all files produced when compiling optee_client, the library, tee-supplicant etc.