[FEA] Static library builds for nvCOMP
Opened this issue · 1 comments
Is your feature request related to a problem? Please describe.
I'd like to deploy a statically built binary which depends on nvCOMP on both Windows and Linux. Unfortunately, the provided artifacts in the downloads for Windows / Linux only contain dynamic libraries (nvcomp.dll & corresponding import lib nvcomp.lib on Windows, libnvcomp.so on Linux). This makes it impossible to build and deploy a fully static binary.
Describe the solution you'd like
I'd appreciate it if static library targets (nvcomp.lib on Windows, libnvcomp.a on Linux) could be provided. Note that the requested static library nvcomp.lib for Windows is different than the import lib. The import lib on its own is not sufficient for a fully static build, as it'll just add a dependency on the nvcomp.dll for you (and load it properly).
Describe alternatives you've considered
On Windows, it doesn't seem possible to convert a dynamic library to a static library. On Linux, it seems there may be some hacky solutions, but no one-size-fits-all tool. I've also considered using an older version of the library, when all of the source was provided, to just build the static version myself, but I'd really prefer using the latest and greatest.
Additional context
N/A
This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.