Closed drewmoseley closed 2 days ago
It seems we are adding a ":" at the end of all the packages unconditionally but maybe this should only be done if an arch is not already specified for any given package.
Workaround for anyone who may be having this issue: Manually edit Dockerfile.sdk and add the arch-based package name outside of the VSCode-automation bits.
Also, I suspect this is true of other templates but have not tested that.
This happens because the devDeps
adds the packages to Dockerfile.debug
and Dockerfile.sdk
. But as the Dockerfile.sdk
is a x86 container that compiles the code through cross-compilation this error happens. We should add an extra field like sdkDeps
to separate the packages installed on the Dockerfile.debug
and on the Dockerfile.sdk
@andreriesco I believe that this was fixed in next
, right? If so, please close this one.
Yes, by this commit here. I will close it here, thanks for the reminder.
I am trying to link with a target library (libtirpc3). If I add "libtirpc-dev" to devDeps in torizonPackages.json the build will install the architecture matching my host (x86_64). If I explicitly use "libtirpc-dev:arm64" the build fails with: