-
Notifications
You must be signed in to change notification settings - Fork 124
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
Buildroot 2020 #400
Comments
Were you previously known as RaspberryPiFan? |
No, but I was in his discord server about a different project, so I knew him. |
There are a number of areas in PINN that could be brought more up to date, such as the build environment, buildroot version and qt framework. But if you want a PR on any of these to be accepted, they need to be done in an incremental manner so I can understand the changes (as I will need to maintain them), following a described roadmap, and each PR needs to be fully tested and working. |
I'll try to switch to buildroot 2018.11, which should at least fix some issues with buildroot, because that's the latest version which supports QT4. If that fully works, I would create a separate branch in my fork, which contains a later version of buildroot, so interested C++ developers can use that to have the latest QT features. I'll submit a PR for buildroot 2018.11 later. |
As I responded elsewhere, switching to a newer buildroot first with the existing Qt4 might be the best solution seeing as Qt5 has dropped QWS and it now needs much more resources (X11 or Wayland compositor etc.) |
PR #249 was mine, I'm a novice when it comes to buildroot, so even though I thought I fixed it up on my system, there were reports of ca-certs not installing properly or at all. I gave it a good try, but it appears I ultimately failed. ^_^;; |
After the old buildroot PR was I deleted, I wanted to continue it and create another PR, but it would use QT5. Because I'm no C/C++ developer, I can't port PINN itself to QT5. I did some research and found this:
I already created a QT5 fork of Arora with some small optimizations.
I'll submit a buildroot only PR if you want, and give you push access (everyone else can open a PR to my repo).
@procount Are you interested in this?
The text was updated successfully, but these errors were encountered: