Slow compilation on MacOSX

[Woweur]

Hi, i have a little "problem" when i compile MaNGOS on MacOSX with gcc (i have try with gcc 4.2, 4.3 & 4.5). In fact, the compilation of the project game is very slow (20-30 mins). On debian, i haven't that problem with the similary hardware.

My hardware config :

I7 2.66 GHZ

SSD

4 GO

I don't understand because on debian, the compilation of the game project is 2-3 mins

Thx.

[darkstalker]

compiling outside windows doesn't use precompiled headers, so there is a speed loss

[Woweur]

I use precompiled patch for GCC, and i don't save a lot of time ...

And i compare with debian, on GCC.

[Toinan67]

make -j2 (dual core)

make -j4 (quad core)

?

[ciphercom]

The speed difference is in my opinion too huge... Maybe you're don't cache the results and every time do a complete recompile? Or do you mean an complete recompile?

I could time my compile if it help's?... but I think it's about 10min for game and I have only an MacBook "13.

[Woweur]

I already use make -j 8 (I7)

[darkstalker]

try using ccache

[jahangames]

for one CPU core i7 witch one i need to use ?

make -j 2

make -j 4

make -j 8

[darkstalker]

make -jN

where N is the number of cores you have

[freghar]

The problem with precompiled headers in GCC is either

• * in the g++ itself (well, it's optimization), since almost nobody uses precompiled headers on *nix
  * in the mangos build system (hosed automake build system / messed up dependencies)
  * in the precompiled headers automake patch (I know, it's maybe the one made by me with performance gain like 5-7%)
  

Another way to speed up build process is to avoid using superlarge .h files (Player.h, Unit.h, ...) and split those, along with the .cpp files itself, into many smaller parts, so other .cpp files can include only the parts they're interested in. This actually saves quite a lot of time (at least on a C project using gcc, but - in theory - all compilers should benefit).