Proposal: pack all native libraries into a package #3179
Replies: 3 comments 2 replies
-
|
+1 For what it's worth (I haven't been able to dig deep enough yet) platform detection at runtime is required anyway if you need a single jar which can deploy to multiple architectures. I've run into issues discussed in Slack where I worked around the lack of a 'universal' jar by depending on all of them, but glide gets confused while trying to load the correct netty native libraries. |
Beta Was this translation helpful? Give feedback.
-
|
Can someone from AWS look at this request too? This is pretty important feature when simplifying build pipelines for applications using GLIDE client. This would massively ease and speed up the adoption Valkey and the GLIDE Client across multiple organizations. One way to do it is enabling BenefitsSimplified build process: No need to create separate builds for different architectures
Implementation NotesThe runtime selection mechanism in
|
Beta Was this translation helpful? Give feedback.
-
|
We are evaluating this proposal. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Proposal: pack all native libraries into a package. On first access to the library, a proper native library for the current OS/platform.
Procs:
Cons:
Beta Was this translation helpful? Give feedback.
All reactions