User forums > Help

Compiler list...

(1/2) > >>

commontater:
Two quicky questions...

1) How do I hide unused compilers from the dropdown list... (I find it massively annoying have to go through 20+ entries with only 2 compilers installed)

2) Why, when I add a custom compiler to the list, does it prompt me for a default compiler every time I start the program?

gd_on:
I agree with you for this long list.
Nevertheless, I think this long list is normal for settings/compiler menu, because it shows all the compilers which are known in C::B by default But, for a per project configuration, I think, as you, that it could be nice if only compilers configured on a specific machine (correct paths and programs correctly initialized in General Settings) are proposed.
For your second point, I have myself several custom compilers (gfortran, g95), but I have not your problem. It works well. Did you fill correctly the paths and programs in settings ? Is default.conf file correctly updated (within your profile on Windows or in .codeblocks on Linux) ? Have you a correct write access to this file ?

gd_on

commontater:

--- Quote from: gd_on on May 09, 2011, 06:59:39 pm ---I agree with you for this long list.
Nevertheless, I think this long list is normal for settings/compiler menu, because it shows all the compilers which are known in C::B by default But, for a per project configuration, I think, as you, that it could be nice if only compilers configured on a specific machine (correct paths and programs correctly initialized in General Settings) are proposed.

--- End quote ---

I agree it's no problem in the global list.

But a project's settings should reflect only compilers enabled for that particular job.  *Especially* if custom compilers are going to be at the end of the list.

So there's no way to hide the unused ones... Bummer!


--- Quote ---For your second point, I have myself several custom compilers (gfortran, g95), but I have not your problem. It works well. Did you fill correctly the paths and programs in settings ? Is default.conf file correctly updated (within your profile on Windows or in .codeblocks on Linux) ? Have you a correct write access to this file ?

--- End quote ---

Maybe that's just me not being fully up to speed on Code::Blocks just yet... there was some other wierdness as well. 
I'll try a reinstall and see what happens.

stahta01:
Sounds like a good idea to add an Disable option to the Global Compiler List and then only show the compilers that are not disabled on the project list.

The feature request site is
http://developer.berlios.de/account/login.php?return_to=%2Ffeature%2F%3Ffunc%3Daddfeature%26group_id%3D5358

Tim S.

timojaask:
Did you find any solution to that second problem?

Today I also started getting "Compilers auto-detection" window every time I start Code::Blocks, after I tried to add WinARM to the list (which was totally confusing, I couldn't get it to work and in the end went back to using makefiles).

Now I don't want it to use any compiler, but it still asks me every time I open Code::Blocks, no matter which one I set as the default.

So any idea how to get rid of the stupid compiler auto-detection window?

Navigation

[0] Message Index

[#] Next page