This warning is now permanently shown when building without iconv. While understanding the drawbacks, I'd argue that there may be cases/platforms where building against iconv isn't practical or isn't necessary. E.g. on Windows, building iconv is a challenge and even when done, it's a large dependency that needs to be shipped around. In cases where minizip2 is used in a controlled environment with known, or pure-ASCII filenames, it can work well without codepage conversion.
It'd be nice to have a way to avoid this warning and silently fall back to the transparent strncpy() method.
This warning is now permanently shown when building without
iconv. While understanding the drawbacks, I'd argue that there may be cases/platforms where building againsticonvisn't practical or isn't necessary. E.g. on Windows, buildingiconvis a challenge and even when done, it's a large dependency that needs to be shipped around. In cases where minizip2 is used in a controlled environment with known, or pure-ASCII filenames, it can work well without codepage conversion.It'd be nice to have a way to avoid this warning and silently fall back to the transparent
strncpy()method.