Vgft.h:35:22: fatal error: ft2build.h: No such file or directory Here’s what make -C /opt/vc/src/hello_pi/libs/vgfont ends up with: make: Entering directory '/opt/vc/src/hello_pi/libs/vgfont'Ĭc -DSTANDALONE -D_STDC_CONSTANT_MACROS -D_STDC_LIMIT_MACROS -DTARGET_POSIX -D_LINUX -fPIC -DPIC -D_REENTRANT -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -U_FORTIFY_SOURCE -Wall -g -DHAVE_LIBOPENMAX=2 -DOMX -DOMX_SKIP64BIT -ftree-vectorize -pipe -DUSE_EXTERNAL_OMX -DHAVE_LIBBCM_HOST -DUSE_EXTERNAL_LIBBCM_HOST -DUSE_VCHIQ_ARM -Wno-psabi -I/usr/include/freetype2 -I/usr/include -I/usr/include/arm-linux-gnueabi -I/opt/vc/include/ -I/opt/vc/include/interface/vcos/pthreads -I/opt/vc/include/interface/vmcs_host/linux -I./ -I/opt/vc/src/hello_pi/libs/ilclient -I/opt/vc/src/hello_pi/libs/vgfont -g -c font.c -o font.o -Wno-deprecated-declarations
Thank you, The git push resin master:resin-emulated trick worked!īut there is still a quirk left, both on remote emulated and local inside-container compilation: compiling /opt/vc/src/hello_pi/libs/vgfont doesn’t work. dev image), but filesystem is read-only, so I couldn’t. I tried to compile docker image on host raspberry OS (on. RUN # I comment this out to compile manually inside container
RUN apt-get update & apt-get install -yq cmake build-essential Here’s the failing cloud compilation from resin.io cloud:Īnd here’s my Dockerfile.template: FROM resin/%%RESIN_MACHINE_NAME%%-debian
Here’s the successful manual compilation from inside container: Particularly, in case of “cloud” compilation, /opt/vc folder misses include, share and src folders.
But if I put RUN /usr/src/userland/buildme in Dockerfile, compilation goes with a bunch of warnings, and while it ends kind of successfully, what’s left on the disk is not what I expect of it. I place it in /usr/src/userland and if I run /usr/src/userland/buildme manually from within the container, it compiles as expected.