I'm used to using gcc -I flag to specify include dirs. I was wondering if msys2 provided any automatic assistance related to include dirs. Specifically, any way msys2 gcc or clang might "know" which dirs to include, based on 32-bit vs 64-bit, or based on which packages are installed.
Interestingly, there is no difference between the two versions of cairo-pdf.h
I'm not sure if this was ever asked and/or answered on another channel. Both gcc and clang should know their respective system include directories. You need to use the correct toolchain though. For mingw64 it would be mingw-w64-x86_64-toolchain and use it from a mingw64 shell.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm used to using gcc -I flag to specify include dirs. I was wondering if msys2 provided any automatic assistance related to include dirs. Specifically, any way msys2 gcc or clang might "know" which dirs to include, based on 32-bit vs 64-bit, or based on which packages are installed.
Interestingly, there is no difference between the two versions of cairo-pdf.h
$ diff /mingw64/include/cairo/cairo-pdf.h /mingw32/include/cairo/cairo-pdf.h
$
So in this case it doesn't matter. I assume in other cases it matters?
Is a good method for me to use lowercase version of MSYSTEM environmental var to help build include path?
Thanks,
Daniel
I'm not sure if this was ever asked and/or answered on another channel. Both
gccandclangshould know their respective system include directories. You need to use the correct toolchain though. For mingw64 it would bemingw-w64-x86_64-toolchainand use it from a mingw64 shell.