I look at sources of dev-cpp , i would like ask why is
version of mingw gcc compilers set constantly (version.pas)?
it can bring problems if you want use different version of
mingw ,because include and libs paths are different. I think ,it should be better if dev-cpp check for version during first start.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
IMHO they should be completely removed, because in gcc > 3.2 the compiler finds its include and lib path itself so it's not necessary for Dev-C++ to set include and lib paths, only the bin. which is same for all versions
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
it looks in <path_where_is_gcc.exe>\..\include (lib)
if you have on the root of disk mingw dir it will look there too, no matter where you installed mingw (but specifiing -I doesn't disable this behaviour)
try gcc -print-search-dirs
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I look at sources of dev-cpp , i would like ask why is
version of mingw gcc compilers set constantly (version.pas)?
it can bring problems if you want use different version of
mingw ,because include and libs paths are different. I think ,it should be better if dev-cpp check for version during first start.
those are hardset only when there no devcpp.ini, otherwise they're taken from there - and you can modify it there.
IMHO they should be completely removed, because in gcc > 3.2 the compiler finds its include and lib path itself so it's not necessary for Dev-C++ to set include and lib paths, only the bin. which is same for all versions
doesn't it look in \mingw instead of \dev-cpp ?
it looks in <path_where_is_gcc.exe>\..\include (lib)
if you have on the root of disk mingw dir it will look there too, no matter where you installed mingw (but specifiing -I doesn't disable this behaviour)
try gcc -print-search-dirs