Consider Docker images for Alpine and Fedora/MinGW builds #476
Labels
No labels
3rdparty
Android
API
Author does not respond
bsd
bug
build system/CI
ci-virtual-device
CMake
Contributions Welcome
Core
dependencies
device-specific
documentation
don't_merge
duplicate
enhancement
Example
Haiku
hidraw
hotplug
info required
invalid
libusb
macOS
Misc
Not an issue
question
Release
Test
Test GUI
Windows
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-libusb/hidapi#476
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As per suggestion: https://github.com/libusb/hidapi/issues/462#issuecomment-1296360252
builds.sr.htand its limitations of only 4 builds at onceFYI this docker image approach can be very fast.
Reference: the following is from Arduino avrdude-packing projects which contains six cross builds (as well as two other actions) at one go.
https://github.com/arduino/avrdude-packing/actions/workflows/release.yml
libusb Linux github action also involves using Docker Container for the umockdev test (simulated USB device).
https://github.com/libusb/libusb/actions/runs/2989246626/jobs/4792835136
I've checked Github Actions Docker Fedora MingGW build - it is insanly fast, i.e. practivally no time/performance overhead because of the Docker image used.
It looks like Github Actions using some caching for Docker images - it takes only ~ 5-6 seconds to initialize.
The Archlinux takes insignificantly longer to initialize - ~10-11 sec.
Alpine Docker build is even faster than Fedora.
If it wasn't for a bug I hit in
musl- it would be so easy to make it work.Anyways - the 3 PRs complete this story.
Good work!