Viktor Szakats

Maybe late to note but OpenSSL _does_ support UTF-8 in default Windows builds (for filenames notably), in these cases, it'd be useful to keep strings in UTF-8.

Yeah, I've noticed (to my horror) that OpenSSL does have a fallback logic. But, UTF-8 is the primary encoding there and without it, it's only possible to pass non-ASCII strings...

`ssl_paths_use_utf8` is a neat idea! The method may well work for URL strings too.

If adding `src` to the PATH can also resolve this, I'd prefer it. It would be a more universal solution and without introducing a platform- (and build-method) specific build exception....

@orgads - installing is optional (esp on Windows), so there is fair chance some scripts/people do their own thing and expect files to be in certain locations. These would need...

> I'll have to remember setting it every time I build curl, and if I have different build directories, I'll need to set it differently for each one of them....

`make install` is one solution for these cases. Not sure about the exact goal/use-case here, but if libcurl.dll happens to depend on further DLLs, copying/moving it next to curl.exe is...

Bumped into the error below while testing a [wolfSSL build with H3](https://github.com/curl/curl-for-win/commit/5a0efe80eb44a8800607a0e891ad43dde43da0cd): ``` vquic/ngtcp2.c:418:9: error: use of undeclared identifier 'wolfssl_logging' (void)wolfssl_logging; ^ 1 error generated. ``` Deleting the line above...

`CURL_LDFLAG_EXTRAS_EXE` is `Makefile.m32` specific, so it indeed doesn't do anything with `./configure` builds. `CURL_CFLAG_EXTRAS` is also something used only in `Makefile.m32`. This build method doesn't support a `CFLAGS` from the...

I think it'd be best to complete Unicode support in libcurl and then fix the different build systems to enable it correctly. Though these two can be done in any...