*When tests is ok and we are confident that CMake is building all in a
correct way,....


On 23 August 2013 11:53, David Ragazzi <[email protected]> wrote:

> Hi Mark and all,
>
> Finally I converted the entire Autotools code to CMake. Now, we can test
> it from:
> https://github.com/DavidRagazzi/nupic
>
> From tests I did, CMake is parsing with success all files.. :-) But this
> doesnt guarantee that files are being created correctly in /Build folder
> but the syntax is ok.
>
> I also hope convert the Shell files to CMake in order to it can build
> Nupic to non-*nix operating systems like Windows (once we could find the
> equivalent win Python libraries). With CMake we could discard Cygwin,
> virtual machines, etc, in addition to developers can use their own IDE's or
> just command lines...
>
> At moment, I'm perfoming tests in my OSX Lion 10.7.2, and I generated with
> some success XCode solution files. The unique error I found is related with
> "#include "numpy/arrayobject.h" in libsupport library which is a known
> error according to some foruns I visited and I'm trying solve it.
>
> Since tests is ok and we are confident that CMake is building all in a
> correct way, we should remember check any new parameters added to these
> days in official Numenta repository but I believe that those wont cause
> major problems.
>
> To check and build/generate it just download the CMake GUI program it on:
> http://www.cmake.org/cmake/resources/software.html
>
> It is very easy to use. A brief tutorial about CMake GUI:
> http://www.cmake.org/cmake/help/runningcmake.html
>
> An example:
> http://www.cmake.org/cmake/help/examples.html
>
> If anyone want help me, please contact me,
>
> Best regards, David
>
>
>
>
>
>
> On 19 August 2013 05:30, Marek Otahal <[email protected]> wrote:
>
>> Thanks for this, David!
>>
>> will be happy to test on linux and have a look, though no cmake expert.
>> Btw, would you like to put these changes into your git branch? so we can
>> easily pull, test and add changes?
>> Thanks again, Mark
>>
>>
>>
>> On Mon, Aug 19, 2013 at 12:27 AM, David Ragazzi 
>> <[email protected]>wrote:
>>
>>> Hi everyone,
>>>
>>> I have converted most code (by hand) from Autotools to CMake (around
>>> 90%). However it is still need a little more of effort to conclude. So if
>>> someone can help, I appreciate, because this week will be short to me.
>>>
>>> Well, you will note that CMake syntax is easier and number of files is
>>> less than autotools. So to convert them, is need more skills on Autotools
>>> than CMake.
>>>
>>> For Autotools experts, all configuration (configure.ac) and initial
>>> Makefile are in a single file called CMakeLists.txt in root
>>> (\nupic-master\). So it´s just compare these files and perform the
>>> remainder conversion. Non-converted Autotools commands are in TODO
>>> comments.
>>>
>>> I atttached to this message a Zip file with the CMakeFiles located in
>>> their respective subfolders. (AlthoughI still won't pull them because the
>>> code is not stable..)
>>>
>>>
>>> Configuration files
>>> \nupic-master\Configure.ac  =>
>>> \nupic-master\CMakeLists.txt (first part)
>>> (CMake allow configure and make commands in a single file)
>>>
>>> Top MakeFiles:
>>> \nupic-master\MakeFile.am  =>
>>> \nupic-master\CMakeLists.txt (second part)
>>>
>>> Other child MakeFiles:
>>> They are related to respective CMakeLists.txt in same subfolder.
>>>
>>> Include file used for all files:
>>> \nupic-master\build_system\unix\Includes.am =>
>>> \nupic-master\CMakeInclude.txt
>>>
>>> Note that the files used for compile are generated by Setup.py (as far I
>>> understand, it concatenate several files to single ones), so it's
>>> interesting we put all the dirty job of Setup.py on CMake once this is its
>>> role (mainly if you want use IDE derived from CMake).
>>>
>>> Please, reply me for any doubts.
>>>
>>> Cheers, David
>>>
>>>
>>> On 13 August 2013 13:10, Matthew Taylor <[email protected]> wrote:
>>>
>>>> Excellent! https://issues.numenta.org/browse/NPC-300
>>>>
>>>> If anyone else reading this wants this ticket completed, please vote
>>>> for it.
>>>> ---------
>>>> Matt Taylor
>>>> OS Community Flag-Bearer
>>>> Numenta
>>>>
>>>>
>>>> On Tue, Aug 13, 2013 at 8:27 AM, David Ragazzi <[email protected]>
>>>> wrote:
>>>> > Thanks Matt, I did it!
>>>> >
>>>> >
>>>> > On 13 August 2013 11:30, Matthew Taylor <[email protected]> wrote:
>>>> >>
>>>> >> On Tue, Aug 13, 2013 at 7:16 AM, David Ragazzi <
>>>> [email protected]>
>>>> >> wrote:
>>>> >>>
>>>> >>> If you agree, we could create a JIRA item for CMake.
>>>> >>
>>>> >>
>>>> >> David,
>>>> >>
>>>> >> Thanks for the details above. Scott has mentioned CMake in the past,
>>>> and I
>>>> >> don't think it's a bad idea at all. Please create this JIRA, and
>>>> include the
>>>> >> details you posted above. If folks disagree with this issue, we can
>>>> discuss
>>>> >> the reasons why within JIRA.
>>>> >>
>>>> >> ---------
>>>> >> Matt Taylor
>>>> >> OS Community Flag-Bearer
>>>> >> Numenta
>>>> >>
>>>> >> _______________________________________________
>>>> >> 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
>>>> >
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>>
>> --
>> Marek Otahal :o)
>>
>> _______________________________________________
>> 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

Reply via email to