Faisal Al-Humaimidi

> Also for context - if I remember correctly, you've earlier been building in MSYS2, but if you have the generic-w64-mingw32 directory, you're cross compiling. Is that true? Yes, I...

@mstorsjo Ok, so I got, somehow, to the root of this segmentation problem. The problem is that `-m16` flag, which is required to build `roms/openbios/arch/x86` of the QEMU project, for...

> This does not seem an issue with llvm-mingw or clang. APR can be compiled with some patches using mingw-w64 toolchain, see the apr_wtypes.patch in https://github.com/msys2/MINGW-packages/tree/master/mingw-w64-apr Thank you for your...

I will surely upstream my changes once I get it to compile, locally first, then on vcpkg. I can see that APR is built for target `mingw-w64-clang-x86_64` (`mingw-w64-clang-x86_64-apr`). Does MSYS2...

Try creating an example shared library, set the `LIBRARY_PATH` variable to point to the location where the import library is made (in my example it was `libzlib.dll.a`), and then try...

Yes, or just `-cc` (or `-c++` for C++).

But, in that case even `x86_64` target shouldn't work either in Linux cross-compiling to Windows🤷‍♂️? Also, when running your toolchain on Windows natively, at least both `x86_64` and `i686` should...

In the meantime in the project I am building, I have made a Python wrapper that would read and parse the `LIBRARY_PATH` and `CPATH` environment variables, and add the appropriate...

Oh, I see. Now I get the intention behind the disabling of `LIBRARY_PATH` environment variable. I guess I have to file a bug ticket to LLVM then 😀🤷‍♂️.

Great job @DUOLabs333 for this project. I've been looking to make something similar myself. Tell me @DUOLabs333, how difficult is it to make the host code more generic (i.e. cross-platform...