When turning on BIT7Z_USE_NATIVE_STRING I get a LNK2019 unresolved external symbol "public: __cdecl bit7z::Bit7zLibrary::Bit7zLibrary(class std::basic_string<wchar_t,struct std::char_traits,class std::allocator > const &)" .....
for a "bit7z::Bit7zLibrary lib(L"7z.dll");"
using bit7z-v4.0.0-rc-msvc2022_mt_x64 and linking the 64bit (debug/release) lib of that package.
not using a wstring and not specifying BIT7Z_USE_NATIVE_STRING works fine of course....
so....any plans to provide wstring based libs, too?
Steps to reproduce
No response
Expected behavior
No response
Relevant compilation output
No response
Code of Conduct
[X] By submitting this issue, I agree to follow bit7z's Code of Conduct
bit7z version
4.0.x RC
Compilation options
BIT7Z_USE_NATIVE_STRING
7-zip version
v22.01
7-zip shared library used
7z.dll / 7z.so
Compilers
MSVC
Compiler versions
No response
Architecture
x86_64
Operating system
Windows
Operating system versions
Windows 11
Bug description
When turning on BIT7Z_USE_NATIVE_STRING I get a LNK2019 unresolved external symbol "public: __cdecl bit7z::Bit7zLibrary::Bit7zLibrary(class std::basic_string<wchar_t,struct std::char_traits,class std::allocator > const &)" .....
for a "bit7z::Bit7zLibrary lib(L"7z.dll");"
using bit7z-v4.0.0-rc-msvc2022_mt_x64 and linking the 64bit (debug/release) lib of that package.
not using a wstring and not specifying BIT7Z_USE_NATIVE_STRING works fine of course....
so....any plans to provide wstring based libs, too?
Steps to reproduce
No response
Expected behavior
No response
Relevant compilation output
No response
Code of Conduct