Compilation should leverage my quad core laptop power

[ffissore]

ATM every gcc call is done sequentially, but both library and core compilation can run in parallel

[ffissore]

A first implementation is available in parallel branch. It lacks proper output management. At the moment, everything is thrown at stdout, meaning the output is likely to get clutter and logger messages will eventually contain syntax errors

[PaulStoffregen]

Maybe you should come up to speed on Go language? That's probably a shorter & more successful path than trying to convince other people to spend their time implementing a feature they've said they do not intend to create because it doesn't make practical sense.

[xcvista]

@PaulStoffregen Meanwhile would you guys offer some internal documentations?

[PaulStoffregen]

I'm pretty sure the only available documentation, aside from the source code, is this wiki: (notice this is 1 of the 14 pages)
https://github.com/arduino/Arduino/wiki/Build-Process

[xcvista]

@PaulStoffregen So I, being a newbie to the Go language, have to reverse engineer an existing codebase. Yeah like that would help a lot.

[PaulStoffregen]

That's a really creative usage of the term "reverse engineer", which usually means figuring out how something works without access to its source code.

[xcvista]

@PaulStoffregen Backtracking a poorly-documented code base is no less difficult than black box analysis.

[PaulStoffregen]

This arduino-builder repository contains only 7816 lines in all its source files, not including the automated tests, and many of those lines are redundant license headers, comments or white space. It's simply not a huge code base. Almost all files and functions have very descriptive names, like "generate_buildpath_if_missing.go". There is a 14 page wiki which does document the data formats and general ideas of the build process.

Calling this project poorly-documented sounds to me like whining.

[xcvista]

@PaulStoffregen All while I personally have zero days of Go knowledge.

[NicoHood]

I miss @ffissore :(

[andig]

@xcvista imho the discussion is a little inappropriate. As Paul has said: its open source, go fix it or leave it if the developers have other priorities. If thats beyond your skills too bad. You may also have chances offering a bounty to make your contribution to the project.

Or: give platformio a try, it has parallel builds and loads of other things that Arduino doesn't offer.

[xcvista]

Coming to think of it, if moving to using Makefiles as an intermediary step, we need and only need the discovery step to find all the libraries. For my personal preference I would first assemble a pre-build source tree that have all core and library code files linked or copied over, throw a generic portable makefile in there and exec make.