Re: [igraph] Cygwin -> Windows compilation?

[Chris Wj]

A weird thing happened to me when compiling with Cygwin and then installing the python module in the local Windows Python25 installation: when I 'import igraph' python just hangs forever. I think this is a cygwin issue with system calls. As I have read, you should be able to compile python extensions in Python > 2.5 with free tools. I think it may be a cygwin issue. Although, on the plus side, when I install in the cygwin Python install, it works just fine. The down side to that is that you have to use cygwin's python (I wonder if it is less efficient and take a performance hit).

If you are successful via any method, please post your results to the mailing list.

-Chris

On Fri, Mar 6, 2009 at 4:32 AM, Tamas Nepusz <address@hidden> wrote:

As I understand it, gnu compiler tools under Cygwin are
recommended for building the igraph library and compiling
programs that call the library.  Must programs built this
way be used in the Cygwin environment?

Nope, the executables that Cygwin create are perfectly legitimate Windows executables - all they need is cygwin1.dll (and of course igraph's DLL if you use igraph). You can use Dependency Walker to check the DLL requirements of your executable. If you don't want to depend on cygwin1.dll (Cygwin's POSIX emulation layer), you can also try compiling igraph in MinGW + MSYS (a minimalistic GNU environment for Windows), or you can compile your program in Cygwin with -mno-cygwin.

See this URL for more details:

http://www.cygwin.com/faq/faq.programming.html#faq.programming.win32-no-cygwin


--
Tamas



_______________________________________________
igraph-help mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/igraph-help