opencog-dev team mailing list archive

[Gustavo Machado Campagnani Gama <gama@xxxxxxxxxxxxx>]

Hi Joel & Ari,

sorry for not answering before. I guess I misunderstood Ari's e-mail --
I did not realize he got stuck (after watching the video, I though he
was merely pointing out dependencies that were missing from our
README.win32 file).

So, if I got everything right, there were two "required" dependencies
that he could not solve: python -- which is an indirect dependency of
cxxtest and, indeed, I forgot to add to the README.win32 file -- and the
GSL library -- which Joel (or someone else working on the pln branch)
added to the CMakeLists.txt file but forgot to add to the READMEs as
well.

So, the "solution" is simply to download and install these
dependencies. :-)

Python for win32 may be downloaded from the official website: 
http://www.python.org/download/releases/

The GSL library may be found at:
http://gnuwin32.sourceforge.net/downlinks/gsl-lib-zip.php

And, theoretically, there's another indirect dependency from the GSL
library:
http://gnuwin32.sourceforge.net/downlinks/libgw32c-lib-zip.php

I said theoretically because I never got to the point of linking the pln
libraries. The build broke when building the Formulas.cc file
(apparently the FormulasIndefinite.h file has some gcc-specific code).

Now, as dhart said we should not have any problems with binaries
distribution, I've uploaded a .zip file with the libraries, headers and
CMakeCache.txt file I'm using. It is available at:

http://www.4shared.com/file/59071788/45536608/opencog-win32-deps.html

(side note: I haven't, however, included the dependencies that use an
installer -- for instance, Python, CMake or Bzr).

Hopefully, this should help ease the process of building opencog on
win32.

-- 
Gustavo


On Thu, 2008-08-14 at 16:42 +1200, Joel Pitt wrote:
> Hi Gustavo,
> 
> Not sure how busy you are with other things, but it'd be immensely
> appreciated if you could assist Ari with the Windows build process s
> that he can help us out with PLN.
> 
> I'd do so myself but unfortunately it's been so long since I developed
> in Windows that I'd as likely steer him wrong than help!
> 
> Thanks,
> 
> J