User forums > Help

Compiler autodetection keeps popping up on startup

(1/2) > >>

rickg22:
After adding a custom compiler (which i called "python checker", I typed in the "py" extension in the advanced options (for "compile single file to object file").

After I closed codeblocks, the next start, I got the autodetection notification for some reason. On compiling a single file,  I got a crash (which later I couldn't reproduce). But after that the compiler autodetection notification keeps popping up.

Help! What's going on and how do I fix it?

(Btw, I submitted the bug here: https://developer.berlios.de/bugs/?func=detailbug&bug_id=14903&group_id=5358 )

Seronis:
Had a similar experience a couplemonths ago when i added a customcompiler option for doingcross compiling.  CB crashed while i was working withthat project and after that -every- time i opened CB it would ask me to choose a default compiler.  i deleted the settings folder for CB to fix it.  Would like to know its actual causethough.

Jenna:
Check if any of the compilers does not have the base path set.

thomas:
It probably crashes before being able to save the settings, or it corrupts the settings. Either of these.

Jenna:

--- Quote from: thomas on December 10, 2008, 10:04:06 am ---It probably crashes before being able to save the settings, or it corrupts the settings. Either of these.

--- End quote ---

A crash might be the reason not to save, but: if any of the base-paths is empty, the autodetect dialog pops up everytime unless the missing path is not empty.

EDIT:

... and autodetect does not set it for a compiler, where the status is "user-defined".

Navigation

[0] Message Index

[#] Next page