User forums > Using Code::Blocks

Making compiler setting stick in Mac OS X

(1/2) > >>

gib:
I have got CB working with gfortran on a Mac OS X machine.  In the usual way, I created a compiler entry for gfortran by copying the GCC C compiler then setting the installation directory (/usr/local/gfortran) and changing the executable names.  With this I was able to build a .dylib, and an executable that links to it.  I've encountered a small problem, which is that CB doesn't seem to remember some things between invocations.  For example, there are never any "Recent projects", and the settings for gfortran are lost, making it necessary to reenter the info each time.  It's as if some config file is not being written, or not found.

stahta01:
Just change the Compiler Settings and then exit out of Code::Blocks.
IIRC, The compiler settings are save on Code::Blocks exit.
If code::blocks crashes the settings are not saved most of the time.

afb is the main Mac Person on the board; I am a MS Windows user who knows some Linux.

Tim S.

gib:
Yes, I change the settings and exit (without crashing), restart C::B and gfortran is gone from the compiler list.  I'm also using C::B with gfortran on W7 and Linux with no problems - there seems to be a Mac-specific issue.

afb:
The settings should be saved to ~/Library/Application\ Support/CodeBlocks/default.conf

There should be a crash report or a warning dialog, if this config file cannot be saved on quit.

gib:

--- Quote from: afb on September 09, 2010, 08:38:45 am ---The settings should be saved to ~/Library/Application\ Support/CodeBlocks/default.conf

There should be a crash report or a warning dialog, if this config file cannot be saved on quit.

--- End quote ---

Thanks.  I'll check this when I get back onto that machine again.

Navigation

[0] Message Index

[#] Next page