News:

Accounts with zero posts and zero activity during the last months will be deleted periodically to fight SPAM!

Main Menu

Codeblocks starting is too slow? can anybody make it faster?

Started by aosp, July 31, 2007, 03:11:35 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions

aosp

July 31, 2007, 03:11:35 PM
I had used CodeBlocks many times. I think CodeBlocks is too slow when it starting. The VC6 IDE is faster than it. I found CodeBlocks will load many plugins, templates and compiler configurations. I had disabled some plugins and deleted some templates. But the compiler configurations seems can not be deleted. I just use GCC compiler only. So can I delete the other compiler configuration to make CodeBlocks start faster?

MortenMacFly

#1
July 31, 2007, 04:44:18 PM
Quote from: aosp on July 31, 2007, 03:11:35 PM
So can I delete the other compiler configuration to make CodeBlocks start faster?
The only way to achive this is to compile C::B yourself. The compiler plugin is "monolitic" thus it includes all compilers. When compiling yourself you can disable compilation/linkage of individual compilers by removing the relevant implementation files from the compiler plugin target if you like. Hence I don't think this will make things a lot faster. What type of computer / OS you have? Cause for me C::B is *much* fatser than VC6...?!
With regards, Morten.
Compiler logging: Settings->Compiler & Debugger->tab "Other"->Compiler logging="Full command line"
C::B Manual: [url="https://www.codeblocks.org/docs/main_codeblocks_en.html"]https://www.codeblocks.org/docs/main_codeblocks_en.html[/url]
C::B FAQ: [url="https://wiki.codeblocks.org/index.php?title=FAQ"]https://wiki.codeblocks.org/index.php?title=FAQ[/url]

JGM

#2
August 01, 2007, 01:45:54 AM
Quote from: aosp on July 31, 2007, 03:11:35 PM
start faster?

MinGW Developer Studio is fast but very limited.

rickg22

#3
August 01, 2007, 05:23:05 AM
I've been trying to tackle the issue. After a bit of experimentation, I realized that the second time you start up C::B, it's much faster. It seems that the loading of projects depends on disk access - i think it's related to the wxFilename class, it might try to access the directory entries or something.

There has been a discussion about the slowness of project loading around the forums, but I forgot where.

Regarding resources, perhaps some of them (i.e. the lexers) could be zipped. But that can wait for a later version. "If it ain't broke..."

CPF

#4
August 01, 2007, 05:36:12 AM
Well.. for me..
the normally, it takes around 15-20 seconds to start it up..
but to start it the second time, it takes just 5 seconds..

XP 3.2G 512MB ram

thomas

#5
August 01, 2007, 10:20:54 AM
Quote from: rickg22 on August 01, 2007, 05:23:05 AMRegarding resources, perhaps some of them (i.e. the lexers) could be zipped. But that can wait for a later version. "If it ain't broke..."
No, Rick, no, no, no.
"We should forget about small efficiencies, say about 97% of the time: Premature quotation is the root of public humiliation."

rickg22

#6
August 04, 2007, 06:57:52 AM
OK, won't even try then :)
Print
Go Up Pages1
User actions