msys2 and headers in the 'wrong' place

MSYS2 provides a Unix-like development environment for Windows, but the way headers are organized might be different from what you're used to on other platforms. MSYS2 aims to keep a more consistent structure with Linux-like systems, which can sometimes lead to header files being in different locations than you might expect on a native Windows system.

When working with MSYS2, here are some tips for handling header files:

1. Package Management:
   Use the package manager (pacman) provided by MSYS2 to install libraries and headers. This ensures that libraries and headers are placed in the appropriate directories for the MSYS2 environment.

2. Compiler Flags:
   When compiling code using MSYS2, ensure you're using the appropriate compiler flags and include paths. MSYS2 provides environment variables like PKG_CONFIG_PATH that can help locate libraries and headers installed via the package manager.

3. Include Paths:
   MSYS2's mingw-w64-x86_64 environment usually includes headers in paths like /mingw64/include. When including headers, use paths relative to the mingw64 environment.

4. MinGW-w64 Compiler:
   If you're using MSYS2 with the MinGW-w64 compiler, headers are usually located in /mingw64/include. Use -I flags in your compilation commands to specify include paths.

For example, to compile a C program that uses headers from a library installed via MSYS2's package manager:

bashCopy code
gcc -o myprogram myprogram.c -I/mingw64/include -L/mingw64/lib -lmylib

Here, /mingw64/include is used as an example. Adjust it based on your library's installation location and the specific library you're using.

Remember that MSYS2's approach may be different from what you're used to on Windows, but it helps provide a consistent and compatible development environment with Linux-like systems.