Why does mingw-64, or the original mingw for that matter, consistently 
hardcode include and lib search paths in their build for c:\mingw 
instead of searching for include files and libraries relative to its 
installation structure ?

Hardcoding absolute paths makes it so much harder running different 
versions of mingw-64. Using relative paths to the installation would 
make running different versions of mingw-64 a breeze.

I can understand why a build of clang on Windows targeting gcc would use 
absolute paths; clang uses the gcc headers and libraries so it needs 
some absolute path to find those gcc files. But why mingw-64 does this 
is beyond me, since everything needed is already included within its own 
distribution of gcc.


------------------------------------------------------------------------------
_______________________________________________
Mingw-w64-public mailing list
Mingw-w64-public@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mingw-w64-public

Reply via email to