Modular repo structure

[breznak]

How to make the repos more modular for rapid development...

https://discourse.numenta.org/t/re-organisation-of-the-c-py-community-repos/

And old issue in nupic.core

[mattheiler]

Can we get a design document for this?
A bit more detailed in the forum topic, but...
For module design, I'd propose:

nupic.core    // -> [] C++ core
nupic.core.cs // -> [nupic.core] C++ core C# bindings
nupic.core.py // -> [nupic.core] C++ core Python bindings
nupic         // -> [nupic.core] C++ client 
nupic.cs      // -> [nupic.core, nupic.core.cs] C# client 
nupic.py      // -> [nupic.core, nupic.core.py] Python client

[breznak]

I'm for a more specialized/isolated repo structure!
...will talk more in the forum

[breznak]

I'm considering this successfully finished!
Thanks to @dkeeney 's porting to pybind and introduction of modules/bindings 👍

We now support:

• cmake downloads and configures external dependencies
• hierarchical cmake files (standalone, if for src/, tests/, bindings/py/, external/)
• separation of (language) bindings into optional modules (bindings/py)