JavaCAN 2.x has automatic architecture detection to select the right native component during runtime. The implementation was limited, but at least for common architectures (x86, common arm versions) it worked good enough.
I could imagine bringing the architecture detection back as separate module that can be used instead of the core/epoll + arch dependencies directly. that module could produce a jar that contains the native libraries for several architectures and robust logic to select the correct one. Some minor core changes might be necessary to facilitate loading libraries from different paths or some other trickery in the module could be applied.
JavaCAN 2.x has automatic architecture detection to select the right native component during runtime. The implementation was limited, but at least for common architectures (x86, common arm versions) it worked good enough.
I could imagine bringing the architecture detection back as separate module that can be used instead of the core/epoll + arch dependencies directly. that module could produce a jar that contains the native libraries for several architectures and robust logic to select the correct one. Some minor core changes might be necessary to facilitate loading libraries from different paths or some other trickery in the module could be applied.