Feature #1025
closed
Test pisentry build on RPi 4
Added by Hammel about 1 year ago.
Updated about 1 year ago.
Description
Check that the PiSentry apps, built against the RPi 4 staging tree and toolchain, run on the RPi 4.
- % Done changed from 0 to 10
Failure: appmgr fails to build.
gnu/stubs-soft.h: No such file or directory
This is because the toolchain prefix is hardcoded in the cross.sh script. It needs to be extracted from the $TC directory from the *-gcc.
This change will need to be applied to ALL apps, which will be quite a bit of work.
The cross.sh script should identify the toolchain prefix like so:
TCPREFIX=$(cd ${TC}/bin && ls -1 *gcc | sed 's/-gcc//')
Then use that in the configure command.
PKG_CONFIG_PATH="" \
PKG_CONFIG_LIBDIR=${STAGING_DIR}/usr/lib/pkgconfig:${STAGING_DIR}/usr/share/pkgconfig \
PKG_CONFIG_SYSROOT_DIR=$STAGING_DIR \
PATH=$TOOLCHAIN/bin:$PATH \
CFLAGS="-g --sysroot=$STAGING_DIR -I$STAGING_DIR/usr/lib/glib-2.0/include -I$STAGING/usr/lib/gtk-2.0/include" \
LDFLAGS="-L$STAGING_DIR/usr/lib -L$STAGING_DIR/lib --sysroot=$STAGING_DIR/" \
./configure --host="${TCPREFIX}"
Tested this against appmgr and it appears to work for RPi4. Need to verify it works for RPi2 and RPi.
Verified - works with all three hw builds.
Now to verify it works with the meta build.
- Related to Bug #1026: cross.sh in app builds has hard coded toolchain prefix added
- Related to deleted (Bug #1026: cross.sh in app builds has hard coded toolchain prefix)
- Blocked by Bug #1026: cross.sh in app builds has hard coded toolchain prefix added
- Status changed from In Progress to Closed
- % Done changed from 10 to 100
Tested on RPi4 hardware with TFT display. Works perfectly.
All updates have been committed and pushed.
Closing issue.
Also available in: Atom
PDF
Updated by