Codelite6: Question about Build settings/Compilers

[Morkel]

Any chance to get the "PATH environment variable" setting back which has been removed from "Build settings/Compilers"?
This made it super-easy to switch between different MinGW versions.

Best regards,
Morkel

[eranif]

This made it super-easy to switch between different MinGW versions

This feature was the root cause of countless reports on this forum (usually it was sh.exe in path that caused broken builds)

You can switch between compilers by simply redefining the environment variables:
CXX, CC, AR and AS (these will always take precedence over the defined tools)

Eran

[alexrass88]

Can be codelite will add the path to the compiler to environment variables?
Then switch compiler, codelite change path.

[eranif]

I did a lot of research on this matter before decided that the tools for a compiler will be used with thier full path (this is how other Makefile generators behaves, such as CMake)
Messing up with an environment is a bad idea and often yields an unwanted results

Eran

[alexrass88]

I have 2 mingw installs. mingw-4.8.1-tdm and mingw-w64 4.8.2. If i not set env var, compiler not working...

C:\Windows\system32\cmd.exe /c "D:/mingw32/bin/mingw32-make.exe -j4 -e -f Makefile"
mingw32-make[1]: warning: -jN forced in submake: disabling jobserver mode.
"----------Building project:[ cltest - Debug ]----------"
mingw32-make[1]: Entering directory 'P:/PrjMGW/cltest'
mingw32-make[1]: *** [Debug/main.cpp.o.d] Error 1
mingw32-make.exe: *** [All] Error 2
cltest.mk:96: recipe for target 'Debug/main.cpp.o.d' failed
mingw32-make[1]: Leaving directory 'P:/PrjMGW/cltest'
Makefile:4: recipe for target 'All' failed
1 errors, 0 warnings

After adding compiler path to env var it working normal...