-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate toolchain and RPi kernel to current releases #3
Comments
Buildroot will be updated directly to 2020.02 once it's released and 2019.11 will be skipped. |
Buildroot 2020.02 is released! It is a long term support release which will be supported with security and other important fixes until March 2021. |
Created new branch for Buildroot 2020.02:
Edit: I will switch to Buildroot-2020.02.6 and remove the old branch. For documentation purposes, these are the patches required for compiling Node.js with 2020.02.2, which seems to be fixed now in .6: 0001-feat-Update-Buildroot-to-2020.02.2.patch.txt |
Current state:
|
Open Issues:
|
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Initial build change to support multiple Qt versions in remote-os with versioned cross compile action. Relates to YIO-Remote/remote-os#3. Removed debug build since it's nowhere used. Developers requiring debug builds usually build and deploy their own version.
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
Moved cross-compile configuration into matrix build configuration. Targets can be added with additional matrix configuration entries. The rest of the build is now generic. This allows to use the new Buildroot SDK in YIO-Remote/remote-os#3
- wpa_supplicant changes for 2020.02.6: Force using wpa_supplicant daemon instead of dbus. The new wpa_supplicant version or Buildroot 2020.02.6 insist using dbus instead of the templated wpa_supplicant services! They are even deleted just before creating the filesystem image. Might be related to: buildroot/buildroot@c27708e Workaround: replace target service in /etc/systemd/system/wpa_supplicant.service to get the wpa_supplicant control socket back with a fixed wlan0 interface. - Bluetooth console changes for 2020.02.6 With the updated Bluez package the rfcomm serial console was no longer working due to pairing issues. The bt-agent is now required with NoInputNoOutput option to allow automatic pairing. - Buildroot package cleanup: - Removed Bluetooth SAP plugin - Removed wpa_supplicant dbus support - Clean up systemd services Use symlinks in overlay directory instead of creating them in the post build script. - Setting QT env variables in profile.d - Update scripts: Use Qt version in release download Since Qt versions are not always binary compatible, the installed Qt version is now specified in the GitHub release artifact. - Using latest YIO component versions This closes #3
- wpa_supplicant changes for 2020.02.6: Force using wpa_supplicant daemon instead of dbus. The new wpa_supplicant version or Buildroot 2020.02.6 insist using dbus instead of the templated wpa_supplicant services! They are even deleted just before creating the filesystem image. Might be related to: buildroot/buildroot@c27708e Workaround: replace target service in /etc/systemd/system/wpa_supplicant.service to get the wpa_supplicant control socket back with a fixed wlan0 interface. - Bluetooth console changes for 2020.02.6 With the updated Bluez package the rfcomm serial console was no longer working due to pairing issues. The bt-agent is now required with NoInputNoOutput option to allow automatic pairing. - Buildroot package cleanup: - Removed Bluetooth SAP plugin - Removed wpa_supplicant dbus support - Clean up systemd services Use symlinks in overlay directory instead of creating them in the post build script. - Setting QT env variables in profile.d - Update scripts: Use Qt version in release download Since Qt versions are not always binary compatible, the installed Qt version is now specified in the GitHub release artifact. - Using latest YIO component versions This closes #3
Migrate to the current kernel. The 4.19 kernel is planned to be an LTS kernel (long term support) afaik.
This ensures support of newer devices, e.g. using a Pi 4 for development which isn't supported with 4.14.
Main goals:
Open issues:
--> works with provided wpa_supplicant.conf in /boot. Must be an initial configuration issue.
--> Bt pairing doesn't work anymore due to security changes, looks like we need a pairing agent now
--> doesn't work, even though Qt promises backward & forward binary compatibility in patch releases 👎
The text was updated successfully, but these errors were encountered: