Re: [igraph] Easier way to compile igraph on Windows?

[Gábor Csárdi]

The "correct" way is to run `make msvc`, but not from cygwin. In fact
we do not use cygwin for anything.

However, we only test this for releases, so between releases some
source or include files might be missing from the project files.

The R interface has a completely separate compilation process which
uses mingw, so that does not help you at all.

The solution here is to add the missing source/include files to the
project file. Pull requests are welcome, especially because I do not
have access to windows right now, so I cannot test this.

Gabor

On Sat, Sep 5, 2015 at 6:44 PM, Szabolcs Horvát <address@hidden> wrote:
> It seems the way to build the MSVC source package is to use "make msvc"
> after ./configure.
>
> For some reason this builds an incorrect package when I run it in cygwin. I
> get "file names" such as "include\make[1]" in the generated .vcproj file, so
> something seems to go very wrong with the project generation.
>
> If I run "make msvc" on OS X instead of cygwin, it does generate a _valid_
> project file, but trying to build it throws errors about several missing
> include files, such as "amd_internal.h" and "cholmod_internal.h" (I guess
> the include directories are missing from the project file?), as well as
> several other problems such as M_PI not being defined.
>
> Since R/igraph 1.0 seems to be based on the development verison of C/igraph,
> I assume there must be a better way to compile igraph for Windows than
> trying to fix all these manually.  Has anyone compiled the 0.8 series for
> Windows already?  What is the right way to do it?
>
> Using the cygwin compiler is not an option because it introduces
> dependencies on cygwin DLLs.  Using the MinGW compiler doesn't seem to be
> possible because it doesn't have sys/times.h, which igraph wants to use.
>
> Is there any alternative solution?
>
> On 5 September 2015 at 13:17, Szabolcs Horvát <address@hidden> wrote:
>>
>> My mistake was that I was looking at the sources on GitHub.  If I download
>> the 0.7.1 package from http://igraph.org/c/#downloads, it (sort of) works
>> with MSVC.  The 0.8.0 nightly packages for MSVC do not work.
>>
>> I had to do this:
>> http://stackoverflow.com/questions/26579997/igraph-c-compiling-link-errors-in-visual-studio
>> and also make sure the macro snprintf was not defined (for Visual Studio
>> 2015).
>>
>> Now my question is:  How is the MSVC source package created?  How can I
>> create such a package from the sources on GitHub, so I can used the weighted
>> layout algorithms that were added since 0.7.1?
>>
>> On 4 September 2015 at 15:40, Szabolcs Horvát <address@hidden> wrote:
>>>
>>> Dear All,
>>>
>>> Are there any precompiled packages available for Windows, usable for C
>>> development with igraph?
>>>
>>> Or is there at least something that avoids having to install all of
>>> cygwin, automake, autoconf2.5, libtool, flex, bison, etc. as described in
>>> the INSTALL.WINDOWS file and allows compiling with the free Microsoft
>>> compiler?  I'm assuming some of these tools generate source code (I might be
>>> wrong) and that perhaps some of this code can be pre-generated.
>>>
>>> I don't have a Windows machine, and I would like to minimize the amount
>>> of stuff that need to be installed to compile something with igraph on
>>> another machine.
>>>
>>> Szabolcs
>>
>>
>
>
> _______________________________________________
> igraph-help mailing list
> address@hidden
> https://lists.nongnu.org/mailman/listinfo/igraph-help
>