Tracking Issue: "One builder to rule them all"

[quentinlesceller]

First mentioned by @yeastplume during 03/03/20 dev meeting:

yeastplume: I wanted a quick discussion on this point, just enough for a yeah or nay on whether it's worth discussing further. Moving all the configuration and startup, etc into a separate project altogether, making 'grin' and 'grin-wallet' library projects. Then we have a top-level project that handles the setup and environment for both and produces the grin-wallet and grin binaries as separate targets. It would also include all integration tests that use both, as well as another binary/lib that starts up servers and wallets quietly and exposes their apis for other consumers (e.g. developers of wallets).

Goal, as cited above, is to have one builder that can build:

• grin (node)
• grin-wallet
• grin-miner

Just by pulling out the different libraries. That would avoid us to have duplicate code and possibly a much cleaner structure. It would also allows us to have all in one integration tests.

Questions which remain to be answered:

• Architecture (one repo for each lib?, one big repo like now?, several repos?)
• [placeholder for futures questions]

[ghost]

One ring to rule them all one ring to find them, One ring to bring them all and in the darkness compile them to web assembly.