I will submit some extensions (piCore 12.x 32/64 Qt5, scipy, pyqt5, numpy) once I am confident that I have built them correctly
parsing them out is actually the part I'm least confident on, and while I can take cues from prior build logs I won't trust my work unless I understand the what and why of all the fancy bash-fu. There are some head-spinning one-liners in there. I hadn't programmed a line of code beyond data analysis routines until 8 months ago, and have almost exclusively used python, so the ins and outs of compiling and all the postprocessing are new to me. Twice I've started packing up these extensions to submit then stopped, when I realized I'd made a crucial mistake (e.g. that -release flag in Qt that shaves off nearly a gigabyte!
)
This place has been extremely welcoming and helpful with troubleshooting compared to many other communities. And, all the work the team has put into piCore has provided something really valuable to me-- I could write many paragraphs about all the details of it, but the dash I've developed is basically the crown jewel of my top-spec 24-kilowatt ebike and piCore provides a great deal of very welcome stability to it! It's a dash, battery-management system monitor, controller retuner, can limit power to ensure a minimum range either dynamically or via intelligent route-based physics simulation, lowjack, and many other goodies that I don't think anyone has fit into an ebike before. Almost certainly not in any bike that does 0-60mph in 4.3 seconds! Point being, I am indebted
I may not be fast about it but if I can't contribute monetarily, I will pay tribute in extensions