User forums > Embedded development

Code::Blocks speed

<< < (3/4) > >>

MortenMacFly:

--- Quote from: davidr on November 22, 2012, 08:54:26 pm ---scintilla/SciTE works better after disable lexer in cpp.properties file. Where can I find this file in codeblocks source code.

--- End quote ---
Lexer files are located in [C::B SHARE folder]\CodeBlocks\lexers\.

davidr:
I have again compiled Scite and scientilla. This time with all CFLAGS needed to armv6 and rpi. Running SciTE editor with .c and .cpp files works fine, no delay. There is some properties-files like SciTEGlobal.properties to change how SciTE works with slower CPU.

When I open a small "Hello World" .cpp file in C::B, CPU works 100% in 5 sec. Why?

Is there any configuration file to tune codeblocks scintilla editor implementation in codeblocks ?

Regards

David
svn 8644 compiled on RaspberryPI v1 (256MB) 850MHz. 2012-10-28-wheezy-raspbian

oBFusCATed:

--- Quote from: davidr on December 07, 2012, 09:39:30 pm ---Is there any configuration file to tune codeblocks scintilla editor implementation in codeblocks ?

--- End quote ---
Probably in the code. What do you need to tune?
Posting some oprofile profile would help probably to pinpoint the problem.

davidr:
When I press i key, i would like to see that character om my monitor immediately not after a second. If codeblocks uses the scientilla/SciTE code, I think it must be fast as SciTE editor.

SciTE editor works very quickly. No delay between key and display.

There must be some parameters to change, when running on a very slow machine like RaspberryPI. I tried to disable .cpp .c lexer (/usr/share/codeblocks/lexers...), but i does not help. Lots of included plugin are disabled.

David
 

Jenna:
Try to disable all plugins and see if it is better then.
If not, try to find out the settings used by scite, and post them here.

The codecompletion-plugin can slow down C::B, especially if "Update parser when typing" is checked.

Navigation

[0] Message Index

[#] Next page

[*] Previous page