Is your feature request related to a problem? Please describe.
#23409 added a feature where we allow to break up a large dynamic library file into chunks (different files) so we can compress and decompress them in a thread pool. This improves startup and build performance.
With that we have a new requirement for someone that is looking to unjar the native resource: they have to know about the layout of our chunks, and how to put it together. I'd like us to consider options to make that easier on a user/developer trying to get to the native bits.
Describe the solution you'd like
@gerashegalov suggested a static util in NativeDepLoader that we can invoke directly from the jar so we can perform this action => reconstitute the dynamic library. He also suggested this allows us to add other metadata queries about the jar/native bits, which sounds awesome.
Describe alternatives you've considered
No alternatives come to mind.
Is your feature request related to a problem? Please describe.
#23409 added a feature where we allow to break up a large dynamic library file into chunks (different files) so we can compress and decompress them in a thread pool. This improves startup and build performance.
With that we have a new requirement for someone that is looking to unjar the native resource: they have to know about the layout of our chunks, and how to put it together. I'd like us to consider options to make that easier on a user/developer trying to get to the native bits.
Describe the solution you'd like
@gerashegalov suggested a static util in
NativeDepLoaderthat we can invoke directly from the jar so we can perform this action => reconstitute the dynamic library. He also suggested this allows us to add other metadata queries about the jar/native bits, which sounds awesome.Describe alternatives you've considered
No alternatives come to mind.