Action Item #572
Update all components and make 1.0 release.
| Status: | Closed | Start date: | 14 Jul 2017 | |
|---|---|---|---|---|
| Priority: | Immediate | Due date: | ||
| Assignee: |  Hammel | % Done: | 100% | |
| Category: | 00 - Basic Build Issues | |||
| Target version: | 1.0 - Atreides | |||
| Severity: | 01 - Critical |
Description
- xcc to 1.23.0
- Buildroot to 2017.02.4
- Kernel to 4.9.y - 4.12.y
This will be the 1.0 release candidate for the core platform.
Associated revisions
RM #572: Bump version to 1.0. Add toolchain config for Crosstool-NG 1.23.0.
RM #572: Add dummy config for 4.9.y.
RM #572: Switch to proper compiler options for gles compiles on RPi2 hardwawre.
RM #572: updated build help reference to KB env var. It's used to reference a GIT tag.
RM #572: Add missing colon suffix to ftp entry in skeleton group file.
RM #572: Fix problems introduced by support for Raspberry Pi Touchscreen to core platfrom UI boot.
RM #572: Add support for Buildroot 2017.02.4 release, which required switch to OpenBox WM.
RM #572: Fix UI to run in windowed (with menu) mode if -e is not used.
RM #572: Fix UI to run in windowed (with menu) mode if -e is not used.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: psplash failed to compiled with updated Linaro compiler toolchain because of the use of an inline
specification to a function in psplash-fb.c. Removing that inline specification fixes the compile time problem
and, I think, should not hurt the splash display since it won't be used for fast screen updates.
RM #572: psplash failed to compiled with updated Linaro compiler toolchain because of the use of an inline
specification to a function in psplash-fb.c. Removing that inline specification fixes the compile time problem
and, I think, should not hurt the splash display since it won't be used for fast screen updates.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Fix pkg-config to properly use staging tree as sysroot when running configure. Add paths to glibconfig.h and gtkconfig.h to CFLAGS because Buildroot's 2017.02.4 .pc files improperly say these are under a lib64 tree instead of a lib tree.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Tie the package version to the version.txt file to make it easier to update the version string automatically with the metabuild.
RM #572: Add missing fixup.sh to packaging build.
RM #572: Add missing fixup.sh to packaging build.
RM #572: Add tgz package for videolib (along with RPM).
RM #572: Add tgz package for videolib (along with RPM).
RM #572: Change default omxplayer command to call the bin instead of the shell script because the shell script requires bash.
RM #572: Bump the default version of Crosstool-NG to 1.23.0, Kernel to 4.9.y and Buildroot to 2017.02.4 for rpi2.
RM #572: Update build for RPI 1 (B+) boards.
History
#1
Updated by Hammel over 1 year ago
- Status changed from New to In Progress
- % Done changed from 0 to 50
xcc and kernel were easy updates, though the kernel has been tested on hardware.
Buildroot issues that need to be resolved:- ipkg has been replaced by opkg. This shouldn't affect any apps as they already used opkg.
- samba has been replaced by samba4. Not sure what this change will require to configs.
- blackbox has been removed. That requires a new default wm in the core platform. Matchbox is already there but isn't appropriate for the core platform.
- Try OpenBox (only option that still seems active) with Onyx Citrus theme,
#2
Updated by Hammel over 1 year ago
- % Done changed from 50 to 70
Port to latest versions of upstream metabuilds has been done and tested. I had to fix a number of minor problems introduced when I added support for the RPi Touchscreen in kiosk mode.
There is one problem the port exposed: pibox-network-config starts in -e mode by default. It should not do that. It should start in windowed mode (not full screen) with a File menu. It's unclear to me if it should show the wifi scan window or not (probably not).
#3
Updated by Hammel over 1 year ago
Pkgconfig changed with Fedora 24 (at least) where the app cross compiles with cross.sh no longer work. The fix is simple enough. Just change this:
PATH=$TOOLCHAIN/bin:$PATH \
CFLAGS="--sysroot=$STAGING_DIR" \
LDFLAGS="$LDFLAGSVAL" \
./configure --host=arm-unknown-linux-gnueabi --prefix=/usr
to this
PKG_CONFIG_SYSROOT_DIR=$STAGING_DIR \
PATH=$TOOLCHAIN/bin:$PATH \
CFLAGS="--sysroot=$STAGING_DIR" \
LDFLAGS="$LDFLAGSVAL" \
./configure --host=arm-unknown-linux-gnueabi --prefix=/usr
The PKG_CONFIG_SYSROOT_DIR variable now changes the prefix path for all .pc files so they are properly rooted by the sysroot directory specified.
Of course this exposed a bug in the Buildroot 2017.02.4 release where the glib-2.0 config puts glibconfig under
-I/home/mjhammel/src/ximba/raspberrypi/bld/buildroot-2017.02.4/output/staging/usr/lib64/glib-2.0/include
when it should be under
-I/home/mjhammel/src/ximba/raspberrypi/bld/buildroot-2017.02.4/output/staging/usr/lib/glib-2.0/include
re: it should be lib instead of lib64.
#4
Updated by Hammel over 1 year ago
The rpi2 port has been completed and tested and the apps tested, with minor fixes applied. All apps needed the cross.sh fix and omxplayer needed it's default player config to use omxplayer.bin instead of the omxplayer shell script which now requires bash.
All changes were pushed and the binaries/packages pushed upstream for a release. I then tagged all the trees using the metabuild's build.sh -t option. However, after doing that I realized I hadn't changed the default versions for xcc, kernel and buildroot to the new versions. So I've done that now and am rebuilding to make sure that came out correct. I'll then rebuild the apps and retest everything. If that's good I can retag the core dev build and the rpi2 1.0 release will be ready.
Then I need to rebuild for rpi B+ and retest again.
#5
Updated by Hammel over 1 year ago
- Subject changed from Update all components to Update all components and make 1.0 release.
- % Done changed from 70 to 100
B+ (re: HW=rpi) build completed and has been tested, with apps, on hardware.
All changes committed and pushed. All trees are tagged. All builds and related files (archives, etc.) have been pushed to the release directory.
The 1.0 release of PiBox is officially out there.
Closing issue.
#6
Updated by Hammel over 1 year ago
- Status changed from In Progress to Closed