Hi Dean, Given the additional feedback from Hideaki, I suggest first try compile using a non-VS compiler (i.e. a commandline like Clang or GCC) and only after you get confident then try adapt the project to VS use (we would love this).
Best, David On 15 January 2014 19:33, Hideaki Suzuki <[email protected]> wrote: > Hi Dean, > > What I did was written in the following mail in details. Please check the > attached file. You can see all steps to reproduce the compilation process > precisely (with the version of Nupic at that time). > http://markmail.org/message/zfoxqb2qepu3p6eq > > Compiling Nupic with VS required considerable effort. The major problems > were: > 1. external libraries Nupic depends on are not contained by Nupic itself > for native windows. > 2. some auxiliary 3rd party codes are not compatible with VS or standard > C++. e.g. Yaml and apr > 3. it contained many unused code for old experiments, producing > compilation errors for VS. > 4. python+swig are bringing difficulties for VS usage. (not fatal though) > > You can see the complete diff of the source code changes I did in the > attached file. > > I think the situation is getting better since then, because there seems to > be improvement on external library infrastructure. 3rd party codes are > updated to the relatively recent versions. You can check JIRA for the > activities mainly done by David. > > As Nupic code is shrinking its core code, I may try the second trial > sometime in the future... > (of course, you can also try before that) > > Best Regards, > Hideaki Suzuki. > > _______________________________________________ > nupic mailing list > [email protected] > http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org > >
_______________________________________________ nupic mailing list [email protected] http://lists.numenta.org/mailman/listinfo/nupic_lists.numenta.org
