Help !! cannot save path settings for compiler

[pkemmer]

Hi all,
i have several different compilers for several embedded targets installed (WinXP). They all are mingw based crosscompilers. Now i m creating some basic projects, clone the "gcc" compiler settings (copy), adjust the pathes and everything works fine. After closing C::B , opening my "mini-test project" again and trying to build it, C::B tells me, not being able to run "xyz-gcc" . Again i go to global compiler settings and ajust the path for this "xyz gcc" compiler and in addition reselect every single of its executables with the supplied common dialog file select box ("..."-button). Running build again works fine.
After closing C::B and open it again, it seems the configuration is lost, although the conf-file under the  applicaion data directory contains my changes (i copied the compiler directories to several places, to ensure it is reproducable).
The nightly build im using is 4639 (s15th nov 2007).
I really tried to press every menu item , button and icon that looks like "save something" ;-)...
Can anyone please tell me, what i m doing wrong or where to find some more infos on this...
Thanks in advance
Peter

[mariocup]

Hi pkemmer,

sounds strange. When you close CB it asks if you want to save your configuration. This is the configuration file default.conf in your APP_DATA\codeblocks directory. Under Linux it is the home directory and under windows  Document and Settings\Application Data (I guess). Just open the default.conf in an editor and look if the settings/paths of your copied compiler are saved here.

Bye,

Mario

[thomas]

When you close CB it asks if you want to save your configuration. This is the configuration file default.conf

No, it doesn't ask. You have no option not to save settings. The only thing you can opt not to save is the layout.

The likely cause of the problem that you are facing is that the version you're using (15th Nov) is one of the versions having the double delete bug in the TODO plugin which causes a crash at exit, and which thus prevents any configuration from being saved. Either disabling the TODO plugin or using a more recent version should fix the problem for good.