Update the build system & QT5 port

[ghost]

Current status

What I'm doing now

Building the system with wayland and QT5 and trying to port PINN to QT5.

What I modified

• Added PINN and rebootp as packages
• Added qt5 port of arora to buildroot
• Update version of Raspberry Pi packages
• GCC update to 9.x.x
• Binutils update to 2.33.1
• Use improved arora
• Modified the rpi-firmware package to support all RPis at once
• Add update-all and update-wifi-firmware to BUILDME.sh

Builds on

• Ubuntu 20.04
• Ubuntu 14.04
• Debian 10
• Debian 9

Works on

• Raspberry Pi Zero
• Raspberry Pi Zero W
• Raspberry Pi Zero WH
• Raspberry Pi A
• Raspberry Pi A+
• Raspberry Pi B
• Raspberry Pi 2B
• Raspberry Pi 2B rev. 1.2
• Raspberry Pi 3A
• Raspberry Pi 3B
• Raspberry Pi 3B+
• Raspberry Pi 4B

Advantages of the new buildroot

• All packages updated, possible bug fixes
• wpa3 is now supported in wpa_supplicant
• pinn will use qt5
• arora will render HTML5 sites better
• Pinn can be built on modern systems

Other information

• I used an existing QT5 version of Arora and added a new feature.
• The buildroot Linux makefiles are only slightly changed to remove a bug, since buildroot is finally able to let the kernel automatically build the dtb.
• The rpi-firmware makefile is changed to install firmware for all Pis (in buildroot 2020.02 you can choose between firmware for either Pi 1-3 and Zero or Pi 4).
• The password is now stored as SHA-256.
• QT5 can't use windows like QT4 since QWS is missing in QT5. I'm currently using wayland instead.
• The new version of PINN requires at least QT 5.12
• I added a guide on how to upgrade buildroot.

The latest test build

Not finished yet...

[lurch]

In #302 you confirmed that "It's only a display bug in QT Linguist." - does that mean that all the changes to the width fields in the .ui files aren't needed?
IMHO the fewer changes each PR contains, the easier it is to review.

[ghost]

In #302 you confirmed that "It's only a display bug in QT Linguist." - does that mean that all the changes to the width fields in the .ui files aren't needed?

No, It works after changing width.

[bovirus]

@raspberrypifan

I suggest to divide the PR from current language file update and system updates.

I will load the current updated language file and in a separate PR proposal for the system update.

[procount]

@raspberrypifan - I'm not sure that creating a new "buildroot-new" folder is the way to go.
In the past, buildroot has been advanced without changing the name of this folder.
Plus, as you are finding, you are having to make changes to other scripts like "make_arch_linux-menuconfig.sh" to take account of this change.

I would prefer that any new buildroot version follows the existing folder structure, then there is less potential for things to break.
If you must maintain the 2 buildroot folders in parallel whilst developing this, I suggest you rename "buildroot" to "buildroot_old" and rename "buildroot_new" back to "buildroot".

[procount]

Can you remove buildroot_old from the PR?
I thought you wanted that for your own personal comparison. It makes no sense to include it in github, because we can use git to look at the differences.

[bovirus]

@raspberrypifan

The German translation is not complete.

Section "OptionsDialog" - Strings translated 41 on 104 - 63 strings untranslated
Section "rerunsetup" - Strings translated 5 on 14 - 9 strings untranslated

For me it's important that you complete the translation.

[ghost]

@raspberrypifan

The German translation is not complete.

Section "OptionsDialog" - Strings translated 41 on 104 - 63 strings untranslated
Section "rerunsetup" - Strings translated 5 on 14 - 9 strings untranslated

For me it's important that you complete the translation.

@lurch want's to fix translations. I can't translate everything because German has another grammer as English.

[bovirus]

@raspberrypifan

Ok if you are talking about strings composed by different single sub-string.
The problem about German language it's the same for Italian because the flow of a sentence is different between English and Italian.

For that I asked to the developer to avoid as much as possible the composed strings.

But many untranslated strings in German language are single sentence/strings.

[procount]

@bovirus I'm happy for @raspberrypifan to complete his porting to the new buildroot first. The translations can wait until @lurch has removed the compound strings, which will make the translation easier anyway.

[ghost]

I don't have enough time now to upload a fix.

[procount]

Take your time.
Updating buildroot is a big change that will require a lot of testing.
I would prefer a version that works properly rather than a quickly delivered one.
Having reverted the previous changes to build under Ubuntu 18.04/10, this issue is not blocking anything, provided PINN is built using Ubuntu 14.04 or equivalent.

[ghost]

I will make 2 pull requests (language and buildroot) after finishing buildroot.

[ghost]

Are buildroot changes needed for #2?

[procount]

Are buildroot changes needed for #2

Probably not, but that's a separate issue.
Each Pull request should fix one issue, which is why Bovirus suggested splitting out your translations from these buildroot changes.

[ghost]

Are buildroot changes needed for #2

Probably not, but that's a separate issue.
Each Pull request should fix one issue, which is why Bovirus suggested splitting out your translations from these buildroot changes.

Yes, I'm going to split my translations from this PR after finishing this.

[ghost]

It doesn't works.

[ghost]

I'm working on it.

[procount]

I admire your persistence

[ghost]

The latest buildroot working with PINN is commit 4b1c0855b321807abdcd737057ae7436547b8001, newer versions don't have QT4. For this, PINN needs to support QT5, but I think this version will work on future ubuntu version.

[ghost]

@lurch @procount @bovirus @XECDesign @ShadowEO
Can someone please test the version I uploaded and compile it.
If you wonder why another account made this, I didn't wanted this, it's my 2nd account.

[ghost]

2nd account

[procount]

@RaspberryPiFan2 - Thanks for persevering with this.
I look forward to testing this out, but I'm afraid it won't be for several weeks yet as I've got something else on.
Have you tried building this version at all yet?

[ghost]

@RaspberryPiFan2 - Thanks for persevering with this.
I look forward to testing this out, but I'm afraid it won't be for several weeks yet as I've got something else on.
Have you tried building this version at all yet?

No, I couldn't, currently I only can build on my Raspberry Pi (my PC is broken), and it's hard to build some host tools like GMP on it.

[ghost]

I will port 3.3.2 later.

[ghost]

I'm still working on it.

[ghost]

Replaced everything. .config file later

[ghost]

Currently testing everything, since this is QT5, PINN probably won't compile, but I will fix it after I know the exact error messages.

[ghost]

I used an existing QT5 arora and improved it, https://github.com/RaspberryPiFan/arora/commit/43000bf2d8b286166234f5ba02cf4219144bf473 (this are not the QT5 changes, but it only works with QT5 since it uses QT5 features, the QT5 port is another commit I didn't make)

[ghost]

This is how arora now renders pages, thanks to qt 5 and webkit 602.1. Screenshot generated in Raspbian)

[ghost]

Making progress with QT5, haven't tested it yet, custom background feature is unavailable, I'm currently trying to bring it back for QT5