Skip to content
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

Use explicit library loading rather than relying on JNA #242

Open
garyschulte opened this issue Feb 21, 2025 · 0 comments
Open

Use explicit library loading rather than relying on JNA #242

garyschulte opened this issue Feb 21, 2025 · 0 comments

Comments

@garyschulte
Copy link
Contributor

Description

JNA's Native.register() function is convenient and tidy, but presents problems on platforms that can have non-standard OS_ARCH names. For example, some versions of linux might report arch as linux-x86-64 where others might report that same arch as linux-gnu-x86_64. This causes problems for packaging and auto-loading native libraries across different distributions and operating systems.

besu-native lib loading needs to be more explicit and opinionated in order to ensure native library implementations are available for all supported platforms.

The c-kzg-4844 java wrapper has fairly robust native lib loading. Using a similar strategy would not only be more robust than JNA, but it would also conform the native lib loading behavior across besu's native lib providers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant