Every time I start up CodeBlocks it asks me for the (default) compiler. As if it doesn't save the setting.
I'm running this on Win7 x86, does anyone have a solution for this problem?
What version of CB?
Quote from: Decrius on September 15, 2010, 08:43:40 PM
Every time I start up CodeBlocks it asks me for the (default) compiler. As if it doesn't save the setting.
I'm running this on Win7 x86, does anyone have a solution for this problem?
One of the compilers does not have a master-path-entry (most likely LLVM D, because it's newly added), you can find out which one it is, if it has an empty status in the window you get when starting C::B.
Open "Settings -> Compiler and debugger -> Global compiler settings -> [the invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]] -> Toolchain executables" and run "Auto detect", it will tell you that it can not find a valid installation and whether it should use the default directory, answer yes and the error should go.
Quote from: jens on September 15, 2010, 09:45:32 PM
Quote from: Decrius on September 15, 2010, 08:43:40 PM
Every time I start up CodeBlocks it asks me for the (default) compiler. As if it doesn't save the setting.
I'm running this on Win7 x86, does anyone have a solution for this problem?
One of the compilers does not have a master-path-entry (most likely LLVM D, because it's newly added), you can find out which one it is, if it has an empty status in the window you get when starting C::B.
Open "Settings -> Compiler and debugger -> Global compiler settings -> [the invalid compiler [YOUR ANSWER IS ALREADY THERE. SEARCH THE FORUMS!]] -> Toolchain executables" and run "Auto detect", it will tell you that it can not find a valid installation and whether it should use the default directory, answer yes and the error should go.
Excellent, works like a charm!
devs: Probably C::B could be made to spit some message what has gone wrong...
Last days I'm experiencing this problem too and it is a bit random. Also on windows it happens far more often.