Remove native libraries and simplify code base#615
Remove native libraries and simplify code base#615
Conversation
|
@FDelporte Frank, you can use my changes on CI flows from here https://github.com/Pi4J/pi4j/pull/539/changes#diff-ffc5a51e3c0c30ff89670916d7bfd5a86b132b62831532905182b28601cac8eaR17 |
@DigitalSmile, should be done, can you validate please? |
Looks good to me, thanks |
There was a problem hiding this comment.
Pull request overview
This PR removes native library dependencies and simplifies the Pi4J codebase by eliminating several libraries and build configurations.
Changes:
- Removed the pi4j-library-pigpio native library wrapper and all associated test code
- Removed the pi4j-library-linuxfs native library wrapper
- Removed the pi4j-library-gpiod native library wrapper
- Updated CI/CD workflows to remove Docker-based native compilation
- Simplified README and release documentation to remove native build instructions
Reviewed changes
Copilot reviewed 90 out of 190 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| libraries/pi4j-library-pigpio/* | Removed entire PIGPIO library wrapper including Java classes, native code, and test files |
| libraries/pi4j-library-linuxfs/* | Removed entire LinuxFS library wrapper including JNI bindings and native implementations |
| libraries/pi4j-library-gpiod/* | Removed entire GpioD library wrapper including native build scripts and Java wrappers |
| .github/workflows/* | Updated CI workflows to remove Docker builds and add direct dependency installation |
| README.md | Removed native library build instructions |
| RELEASE.md | Simplified release documentation removing native build profile references |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
I was expecting this as something we'd do after 1-2 months -- it will make it quite a bit harder to check at head if an issue is related to the new providers....? EDIT I mean I am not strictly opposed, was just hoping we'd let the dust settle a bit after 4.0 before we embark on 4.1 |
|
That's what release branches are for =)) |
See issue #614