Independent Build Process

[david-ragazzi]

This commit includes the compilation of the dynamic/static libraries
that compose nupic.core. They are generated by default on
nupic.core/build/release folder, however any user could change its
destination using cmake -DPROJECT_BUILD_RELEASE_DIR:STRING=… or cmake -DPROJECT_BUILD_TEMP_DIR:STRING=… command line.
Thought this option, Travis at nupic repo will compile the static
libraries and put them on nupic/build/releasefolder.

The output of this library is a static library called nupic.core (I linked with HtmTest, TesteEverything, and all is ok.. :-) ).

This PR replaces this:
#33

fixes #4

[rhyolight]

Alright! I'm going to pull and test this now.

[subutai]

@Davidragazzi This is great and a big step forward! Hopefully we'll be able to test, review and merge soon. Someone should go through the details of what you did as well and see if we can catch any non-obvious issues.

[rhyolight]

@Davidragazzi I updated the README with build instructions: david-ragazzi#1.

It all build locally for me, but I haven't tried it with nupic yet. I'll try it over the weekend. Please @subutai or @scottpurdy, you guys know more about C++ projects than me. If you get time try this out with nupic. I can't wait to get this integrated! 👯

[david-ragazzi]

It all build locally for me, but I haven't tried it with nupic yet. I'll try it over the weekend.

To test locally nupic:

• Clone my nupic fork (https://github.com/DavidRagazzi/nupic);
• Download my nupic.core fork (https://github.com/DavidRagazzi/nupic.core);
• Copy content of nupic.core (except git files) to nupic/nta
• Build my nupic fork using CMake;

(Dont forget this will change your environment variables, i.e. $NUPIC and $NTA will be pointed to my fork directories.. Be carefull when test in machines that already use nupic for several applications such as Grok)

[david-ragazzi]

@Davidragazzi This is great and a big step forward! Hopefully we'll be able to test, review and merge soon. Someone should go through the details of what you did as well and see if we can catch any non-obvious issues.

Thanks @subutai.

Guys, note that now nupic.core is trully stand-alone!! Furthermore, I pulled Windows external static libraries (libapr, libz, etc) in order to someone go ahead to port it to Windows (I believe this job is much easier now.. :-) ).

Also note in CMake file that we simply need specify the source folder for a subproject, not every source file within it.. I.e. CMake transverses the folder and add all the source files found and group them using subfolders hierarchy.. This leaves the project well organized and avoid the creating of additional static libraries to be linked (which leaves the build faster too).

[subutai]

Furthermore, I pulled Windows external static libraries (libapr, libz, etc) in order to someone go ahead to port it to Windows (I believe this job is much easier now.. :-) ).

Wow - didn't realize that! Cool!

[david-ragazzi]

Hi guys,

Have someone reviewing this PR and this http://github.com/numenta/nupic/pull/751?

Please, give attention for them as new PRs are coming and this will bring rework.. :-(

[rhyolight]

Working on it...

[rhyolight]

I don't see a problem with this, but @subutai might. Problem is that he is out of the office with no internet until Monday. Let me think about this today and talk with @scottpurdy first. I will get back with another comment by end of day.

Thank you both for your work! And @utensil it's nice to see another person working on these issues! 😀