kicad-developers team mailing list archive

[Henner Zeller <h.zeller@xxxxxxx>]

There are a lot of dependencies (=timestamps) to be checked, so having
a solid state disk can probably speed up things dramatically.

Also, for incremental re-compile after a make clean, you might want to
look into ccache, that allows to locally cache compiler outputs (not
sure if that is available on Windows proper, but an internet search
suggests as such). ccache speeds up a (make clean ; make) to abot 3:20
minutes. It looks like there is a lot of time wasted in partially
re-building and re-packing the boos library, but I think that is a
separate discussion (apparently it makes sense on some systems)

Compiling things in parallel is always a good idea, and as others
pointed out, the -j option is good for that. In my case, I just set
the environment variable
MAKEFLAGS to '-j6' to make sure I never forget that.

(FWIW, just typing 'make' on an already build KiCAD (I think this is
what you are doing) takes about 3.6 seconds on my ~3 year old Linux
machine (4 core i5 2500k, probably similar to yours) - I do have a
solid state disk, but can't compare what difference that makes)

The rest of the differences might be just Linux/Windows differences,
but you can only really tell if you do the same on your Linux
partition and compare.

On 22 October 2014 06:01, Tim Hutt <tdhutt@xxxxxxxxx> wrote:
> Hi,
>
> I'm trying to do some kicad development on windows. I initially downloaded &
> built it with kicad-winbuilder which went without a hitch. Kicad runs fine.
>
> However, if I perform a null-rebuild (i.e. I don't change anything and just
> run `make` again), it takes about 70 seconds to run. That's quite a while
> isn't it? My PC is pretty fast (quad core 3.3 GHz i5, 16GB RAM), so I
> wouldn't have expected it to take so long. Is this just a feature of cmake?
>
> Build output is below. How long does it take for you guys? Am I doing
> something wrong?
>
> Cheers,
>
> Tim
>
> -----
>
> C:\Users\Tim\Local\kicad-winbuilder-3.4\build\Release>mingw32-make
> [  0%] Built target boost
> [ 30%] Built target bitmaps
> [ 30%] Built target lib-dependencies
> [ 38%] Built target common
> [ 38%] Generating headers containing GLSL source code
> Headers are up-to-date
> [ 38%] Built target shader_headers
> [ 39%] Built target gal
> [ 43%] Built target pcbcommon
> [ 44%] Built target 3d-viewer
> [ 44%] Built target polygon
> [ 45%] Built target pcad2kicadpcb
> [ 46%] Built target openssl
> [ 46%] Built target avhttp
> [ 46%] Built target github_plugin
> [ 47%] Built target cvpcb_kiface
> [ 47%] Built target cvpcb
> [ 57%] Built target eeschema_kiface
> [ 58%] Built target eeschema
> [ 61%] Built target gerbview_kiface
> [ 61%] Built target gerbview
> [ 61%] Built target lib_dxf
> [ 62%] Built target idf3
> [ 64%] Built target pnsrouter
> [ 79%] Built target _pcbnew
> [ 79%] Fixing swig_import_helper in Kicad scripting modules
> swig_import_helper fixed for
> C:/Users/Tim/Local/kicad-winbuilder-3.4/build/Relea
> se/pcbnew/pcbnew.py
> [ 79%] Built target FixSwigImportsModuleScripting
> [ 94%] Built target pcbnew_kiface
> [ 94%] Built target pcbnew
> [ 95%] Built target pl_editor_kiface
> [ 95%] Built target pl_editor
> [ 96%] Built target potrace
> [ 96%] Built target bitmap2component
> [ 98%] Built target pcb_calculator_kiface
> [ 98%] Built target pcb_calculator
> [100%] Built target kicad
> [100%] Built target dxf2idf
> [100%] Built target idf2vrml
> [100%] Built target idfcyl
> [100%] Built target idfrect
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~kicad-developers
> Post to     : kicad-developers@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~kicad-developers
> More help   : https://help.launchpad.net/ListHelp
>