Is there a C::B command line option support loading a specific plugin

[ollydbg]

I'm debugging C::B in C::B, but it seems by default, it will cause several seconds( more than 30 second ) to let the gdb.exe load the debugee.

I suspect there are too many plugins(compiler, debugger, astyle....)

I found that there is an option to "Disable the whole plugin" command line option, but that not my choice.
I would like to only load one plugin such as "Code Completion plugin".

Can someone help me? thanks.

[MortenMacFly]

Can someone help me? thanks.

You have several options, pick one:
- Disable all plugins other that CC via the settings. This is persistent accross C::B sessions.
- Simply move all non-required libs out of the plugins folder (a batch file / script can handle that easily) and start C::B.
- Start C::B in safe mode (which disables all plugins) and load the plugins needed as desired.

[ollydbg]

- Disable all plugins other that CC via the settings. This is persistent accross C::B sessions.

thanks, I have choose this one, because, the debugger C::B is a portable version, so, only the debugee C::B has the persistent settings.
 

By the way, to debug CC plugin, one need to at least enable compiler plugin, if not, it is really hard to let the parser following the include files.

[mariocup]

Hi ollydbg,

if you invoke C::B the default personality will be used (default.conf) (see right corner of status bar in C::B). If you start C::B with the option -p=<profile_name> then CB stores all settings in <profile_name>.conf. You can configure this profile to disable all unnecessary plugins and store the settings in this profile.
You can even use CB option -p=ask to get a dialog to switch between different profiles.  (See chapter Personalities in http://www.codeblocks.org/docs/main_codeblocks_en.html).

I prefer this solution since it has no persistent effect and it can be used to switch between different configurations easily.

[ollydbg]

Hi ollydbg,

if you invoke C::B the default personality will be used (default.conf) (see right corner of status bar in C::B). If you start C::B with the option -p=<profile_name> then CB stores all settings in <profile_name>.conf. You can configure this profile to disable all unnecessary plugins and store the settings in this profile.
You can even use CB option -p=ask to get a dialog to switch between different profiles.  (See chapter Personalities in http://www.codeblocks.org/docs/main_codeblocks_en.html).

I prefer this solution since it has no persistent effect and it can be used to switch between different configurations easily.

Thanks, ,this is a really good alternative.
By the way CodeBlocks at the command line, I can't find any text about about "-p=ask", so, this option can be added in the next release of Manual.

[mariocup]

Hi,

the manual contains already the info. The option -p is the short option for --personality.

Code

1.10.3  Personalities
....
If you start CodeBlocks from the command line with the additional parameter --personality=ask, a selection box will be displayed for all the available profiles.