Re: [igraph] python 2.5 installer for igraph 5.2?

[Gábor Csárdi]

On Fri, May 29, 2009 at 3:43 AM, Chris Wj <address@hidden> wrote:
> I'm thinking you guys should set up an automated build server that compiles
> nightlies of the latest bzr branch. You can set up VM's for 32 and 64 bit
> oses. If you put out a call for donations, and maybe even maintainers for
> specific versions, you could put together a machine dedicated to the task
> for local build and upload to launchpad or mirror at google code for
> download location.
> I think it could really free you of these tasks and questions.

I am actually setting up such a build server right now using VMWare
Server. It is not completely trivial, because I need to write the
scripts for myself: pulling from bzr if there is something new,
compile this and that, build docs, etc. and then copy the packages to
a web-server.

Even just publishing the packages is not trivial, since most free
development sites (sourceforge, launchpad, etc.) don't support
automated uploads. savannah.gnu.org might work, but they refresh their
mirrors very slowly, maybe once a day, and that is not optimal if you
want to do nightly builds.

So it is a pain in the neck. If you are aware of some ready-to-use
solution to make automated builds for different platforms, please tell
me.

Gabor

> -Chris
>
> On Thu, May 28, 2009 at 6:25 PM, Tamas Nepusz <address@hidden> wrote:
>>
>> Hi Jose,
>>
>>> Is there a python 2.5 installer for igraph 5.2 (latest)?
>>
>> No, there isn't, at least not at the moment. The reason is that Windows XP
>> that's running in my VirtualBox has Visual Studio 2008 Express -- which is
>> unsupported as a Python extension compiler before Python 2.6.
>>
>>> if not, how hard is it to build it on windows?
>>
>> Well, it's not a trivial task but not impossible. We have a lot of
>> experience in that now ;) The first thing is that you should try to stick to
>> Microsoft Visual Studio because Python is also built with MSVC, hence it
>> links to a different version of the Microsoft C Runtime than Cygwin or
>> MinGW. If you try to compile igraph with MinGW or Cygwin, you will end up
>> with mixing different versions of the C runtime and funny things will happen
>> when a FILE* pointer is passed between the C core of igraph and Python
>> (since the internal structure of a file object changed somewhere between the
>> two runtimes). If you have an earlier Visual Studio (2003 or 2005) and you
>> are willing to give it a go, I'm happy to send you the scripts that I use.
>> Otherwise, I might try to set up another VM with an older MSVC and compile
>> igraph with Python 2.5 there, but I can't promise anything.
>>
>> Best,
>> --
>> Tamas
>>
>>
>>
>> _______________________________________________
>> igraph-help mailing list
>> address@hidden
>> http://lists.nongnu.org/mailman/listinfo/igraph-help
>
>
> _______________________________________________
> igraph-help mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/igraph-help
>
>



-- 
Gabor Csardi <address@hidden>     UNIL DGM