Ogre Forums

jacmoe wrote:Are we talking about a complete build of Ogre here?
11 minutes?
That's nothing.

If you throw a frog into a pot of boiling water, he will jump right back out, correct? However, if you put him in a pot of tepid water and gradually turn up the heat, he will happily boil to death.

There's also a "can't see the forest for the trees" saying as well, but you get the point.

To you it's nothing because it's been getting longer and longer, but gradually, so you haven't noticed. For someone new to Ogre, it's very noticeable. Step away a second and watch Ogre build. Ask yourself if you think those files should take as long to compile as they do. If you are being intellectually honest, the answer is "no".

Honestly, it wasn't nearly this bad in 1.4.

jacmoe wrote:Qt Labs has created jom which is an nmake clone with -j parameter support like GCC:
http://qt.gitorious.org/qt-labs/jom/
Worth looking into?

IMO, no. MSBUILD works just fine with /MP.

nullsquared wrote:<offtopic>

Klaim wrote:by using this (now payable) plugin : MPCL to allow .cpp/.c parallel compilation

Payable? As in $$? I don't understand why such primitive functionality isn't included with MSVC. I use Code::Blocks with MSVC's compiler (and debugger, too) and I enjoy my parallel source compilation (from the same project). I also enjoy my simple "goto file" feature which MSVC is also lacking (of course, VAX has it).

As xavier said, VS has it but until recently it was not official and it was limited (not available in Debug mode because not compatible with some typic Debug-mode options).
First this plugin was free (for several months). The author turned it to shareware after that, certainly because he've seen that a lot of people wanted a feature like this. His version worked better than the previous non-official option of VS (because it didn't care about the debug options, making sometime a compilation strangely fail but easy to fix by recomiling the cpp -- the problems were about parrallellism but I don't remember the details).