Eric Biggers
Eric Biggers
So you'd like `__attribute__((visibility("hidden")))` to be used when building a static library. Why? I didn't think it made a difference for static libraries.
Please read the installation directions: https://github.com/ebiggers/wimlib?tab=readme-ov-file#installing-distro-package
Don't the compression functions in libwim already do this? This is what they are for. See: https://wimlib.net/apidoc/group__G__compression.html > These functions are already used by wimlib internally when appropriate for reading...
You need to use the wimlib_* API functions, not internal functions that you found in the source. Please see the API documentation I linked to -- this is what it...
Well, it is still part of libwim, so you have to use the correct flags for linking to libwim. For static linking which you seem to want, use `pkg-config --libs...
FYI @nibrunieAtSi5, @kdockser
A maintainer needs to approve the workflow.
> Well....I mentioned the changes we made for the AVX2 version to the BoringSSL developers and they immediately started removing all of the analogous encoding hacks from BoringSSL about 2...
Sorry, I've been busy. I'm taking a look at this again. If I understand correctly, removing support for empty passwords is actually unnecessary to fix the issue. Would you mind...
> So I created a wrapper called wimlib_realpath, which in case of the NULL parameter, after realpath returns reallocates and copies the buffer over with wimlib's allocator hook (memdup). Note...