User forums > Using Code::Blocks
ubuntu C::B questions
Game_Ender:
--- Quote from: mandrav on March 05, 2006, 10:21:59 am ---C::B full rebuild (added "-O2 -ffast-math" in project to match make options):
--- End quote ---
Didn't watch the compile options close enough to see the differences.
takeshimiya:
--- Quote from: thomas on March 05, 2006, 10:25:58 am ---
--- Quote from: Takeshi Miya on March 05, 2006, 01:28:19 am ---If you're going to test it, just make sure to disable all plugins except the Compiler plugin (CodeCompletion esp. is known to make the build slower).
--- End quote ---
Your tips amaze me every day anew... :lol:
--- End quote ---
Taken from Ogre Wiki :wink: http://www.ogre3d.org/wiki/index.php/Building_From_Source#GCC_.26_Code::Blocks
--- Quote ---Performance Tip: It is suggested to disable Code::Blocks code completion plugin, before opening the Ogre workspace. This workspace contains ~40 projects which will be parsed.
--- End quote ---
My own tests shows the same, maybe we are missing something?
Regards,
Takeshi Miya
thomas:
Well, they were measuring the time to compile Code::Blocks, not Ogre.
This particular project is parsed in well under 10 seconds on an average PC if you have all parsing options turned on (2-3 seconds otherwise). After that, code completion takes zero CPU and is entirely irrelevant.
If you either run a batch build or wait a moment before hitting the gear (which is usually the case anyway), the build takes the exact same time with or without that plugin.
takeshimiya:
--- Quote from: thomas on March 05, 2006, 09:39:49 pm ---Well, they were measuring the time to compile Code::Blocks, not Ogre.
This particular project is parsed in well under 10 seconds on an average PC if you have all parsing options turned on (2-3 seconds otherwise). After that, code completion takes zero CPU and is entirely irrelevant.
If you either run a batch build or wait a moment before hitting the gear (which is usually the case anyway), the build takes the exact same time with or without that plugin.
--- End quote ---
Ok, my tests didn't show near the same, but it's because I'm low on RAM, which with CodeCompletion enabled and when parsing a Workspace with more than 1 project, and compiling at the same time rendered the pc in a unuseable state, because of swapping to disk.
This didn't happen with a Workspace with 1 project, neither with CodeCompletion disabled.
Anyways, this was before Rev.2121, I have to test if still happens (don't think so).
So the tale is that to compile the Contribs Workspace I always had to disable the CodeCompletion plugin.
Probably if you have 1GB or more of RAM never noticed any of this.
thomas:
If you are low on physical memory, then precompiled headers are the first thing you want to turn off.
While precompiling the SDK, gcc can easily eat up 350 megabytes of RAM.
Personally, I'd advise to get more RAM though, it's not like RAM is expensive these days. Every ElCheapo PC from a supermarket has a gigabyte these days.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version