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

[Tamas Nepusz]

> Just changing those two files wasn't sufficient. I was getting linking
> errors.  Since defining MSDOS appeared to work, I just used that
> instead of tracking down the linking errors.
There's a related post on Stack Overflow, which might be useful:

http://stackoverflow.com/questions/12747515/installing-compiling-in-cygwin-mingw-how-to-set-the-include-path-symbolic/12766354#12766354

> Are the failed tests somehow using f2c?
Very unlikely. f2c is mostly used to compile the version of BLAS,
LAPACK and ARPACK that ships with igraph. These are, in turn, mostly
used in eigenvector-related functions.

T.

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Szabolcs Horvát]

Just changing those two files wasn't sufficient. I was getting linking
errors.  Since defining MSDOS appeared to work, I just used that
instead of tracking down the linking errors.  I'm going to look at
what else is changed by MSDOS and what's the minimal change required
to make it work.

Then there's the problem with the test failures.

Are the failed tests somehow using f2c?  I get crashes on sparse array
stuff, and no output for some weighted shortest path functions.
Hopefully it's related because then I know where to look to fix the
failures ...

On 14 September 2015 at 11:38, Tamas Nepusz  wrote:
> I'm a bit afraid of simply defining "MSDOS" as it seems to change
> several other things in f2c - for instance, it also defines
> NON_UNIX_STDIO, which in turn changes several IO related things in
> f2c, and I'm not sure about the consequences of those changes. So, I
> think it's okay if you change this for your own purposes, but we
> cannot treat this as an official workaround for compiling igraph on
> MSYS yet.
>
> T.
>
>
> On Sun, Sep 13, 2015 at 2:57 PM, Szabolcs Horvát  wrote:
>> export CFLAGS=-DMSDOS
>> ./bootstrap.sh
>> ./configure --disable-gmp --prefix=...
>
> ___
> igraph-help mailing list
> igraph-help@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/igraph-help

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Tamas Nepusz]

I'm a bit afraid of simply defining "MSDOS" as it seems to change
several other things in f2c - for instance, it also defines
NON_UNIX_STDIO, which in turn changes several IO related things in
f2c, and I'm not sure about the consequences of those changes. So, I
think it's okay if you change this for your own purposes, but we
cannot treat this as an official workaround for compiling igraph on
MSYS yet.

T.


On Sun, Sep 13, 2015 at 2:57 PM, Szabolcs Horvát  wrote:
> export CFLAGS=-DMSDOS
> ./bootstrap.sh
> ./configure --disable-gmp --prefix=...

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Gábor Csárdi]

On Sun, Sep 13, 2015 at 3:01 PM, Szabolcs Horvát  wrote:
> On 7 September 2015 at 19:46, Gábor Csárdi  wrote:
>> Also, I am not sure if MSVC objects and msys objects are binary
>> compatible. In general, can you compile Mathematica extensions with
>> both?
>>
>
> Thanks for the response Gábor ! I don't really understand the source
> of these incompatibilities.

I don't know much about these toolchains, I guess it comes down to
which standard libraries are used in R and in Python.

> I know that both MSVC and mingw32 used to
> work more or less out of the box with Mathematica, and I used the
> latter a lot. MinGW-w64 requires more work, but there is actually a
> usage example in the Mathematica documentation ... of course that
> doesn't mean that there won't ever be any problems ...  It would
> likely be the safest if I could use MSVC as that's the standard
> toolchain on Windows, but at the moment I'll be happy if I can get
> things working at all, with any compiler.
>
> When you compiled with MinGW, did you have any problem with tests
> passing (or rather not passing)?

I only compile the R package with mingw, and that has a separate test
suite, the C tests are never checked.

G.

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Szabolcs Horvát]

On 7 September 2015 at 19:46, Gábor Csárdi  wrote:
> Also, I am not sure if MSVC objects and msys objects are binary
> compatible. In general, can you compile Mathematica extensions with
> both?
>

Thanks for the response Gábor ! I don't really understand the source
of these incompatibilities. I know that both MSVC and mingw32 used to
work more or less out of the box with Mathematica, and I used the
latter a lot. MinGW-w64 requires more work, but there is actually a
usage example in the Mathematica documentation ... of course that
doesn't mean that there won't ever be any problems ...  It would
likely be the safest if I could use MSVC as that's the standard
toolchain on Windows, but at the moment I'll be happy if I can get
things working at all, with any compiler.

When you compiled with MinGW, did you have any problem with tests
passing (or rather not passing)?

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Szabolcs Horvát]

On 7 September 2015 at 21:34, Tamas Nepusz  wrote:
>> I tried installing msys2  to be able to run the
>> configure script, and the mingw-w64 package to be able to compile for 64 bit
>> systems.  Unfortunately the build process stops when the compiler cannot
>> find .
> sys/times.h is not available in MinGW, only in Cygwin (as far as I
> know). The only place where igraph uses it is in f2c, which is a
> third-party library. In particular, the two occurrences are in
> src/f2c/dtime_.c and src/f2c/etime_.c. These files seem to use clock()
> and CLOCKS_PER_SECOND only. clock() is actually also available from
> , so you could try including time.h instead of sys/time.h.
> Also, CLOCKS_PER_SECOND should probably be replaced with
> CLOCKS_PER_SEC because time.h defines CLOCKS_PER_SEC.
>
> Let me know if this worked for you.
>

Thanks for the hints Tamás! They helped me get a working igraph finally.

Looking at those files, it turns out that I need to #define MSDOS in
order to avoid using sys/times.h. Just getting rid of sys/times.h in
these files was not sufficient, but defining MSDOS resulted in a
successful compilation.  For future reference, here's what I did:

First I installed msys2 and the mingw-w64 toolchain based on the
instructions here: https://wiki.qt.io/MSYS2

After mingw-w64 is installed, you'll find a mingw64_shell.bat file in
the msys2 installation directory. Run this to get a shell where the
compiler is already in the PATH.  I used gcc 5.2.0.

Clone the git repo, then as usual,

export CFLAGS=-DMSDOS
./bootstrap.sh
./configure --disable-gmp --prefix=...

(In place of ... write the desired installation location.  I haven't
tried using GMP yet..)

make

This will produce libigraph-0.dll as well as static libraries.

Trying make check will fail unless the above mentioned dll is in the
path.  After fixing that, the following tests still fail:

 32 33 83 84 86 159

I'm still investigating this, but some are due to segfaults, some due
to wrong results and some due to missing headers.

The produced DLL appears to be compatible with MSVC, but depends on
the following due to using this version of MinGW:

libgcc_s_seh-1.dll
libstdc++-6.dll
libwinpthread-1.dll

I do have a (sort of) working igraph for Mathematica, but as you can
see this is not yet the final solution, so still investigating.

Szabolcs

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Tamas Nepusz]

> I tried installing msys2  to be able to run the
> configure script, and the mingw-w64 package to be able to compile for 64 bit
> systems.  Unfortunately the build process stops when the compiler cannot
> find .
sys/times.h is not available in MinGW, only in Cygwin (as far as I
know). The only place where igraph uses it is in f2c, which is a
third-party library. In particular, the two occurrences are in
src/f2c/dtime_.c and src/f2c/etime_.c. These files seem to use clock()
and CLOCKS_PER_SECOND only. clock() is actually also available from
, so you could try including time.h instead of sys/time.h.
Also, CLOCKS_PER_SECOND should probably be replaced with
CLOCKS_PER_SEC because time.h defines CLOCKS_PER_SEC.

Let me know if this worked for you.

T.

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Gábor Csárdi]

On Mon, Sep 7, 2015 at 6:25 PM, Szabolcs Horvát  wrote:
> Hi Gabor,
>
> Thank you for the comments.
>
> Can you give me some hints on how you built igraph using the mingw
> toolchain?

It is R specific, so I don't think it is very useful for you.

> Did you compile a 32 or a 64 bit executable?

Both.

> How did you run the configure script?

I did not, I pre-specify all options, and make sure that the libraries
(libxml2, etc) are available.

But again, this is R specific, so probably not very useful for you.

> I tried installing msys2  to be able to run the
> configure script, and the mingw-w64 package to be able to compile for 64 bit
> systems.  Unfortunately the build process stops when the compiler cannot
> find .  The configure script does correctly find out that this
> header file is not available, but it still sets up a build process that
> requires it.
>
> I don't specifically need MSVC, I just need to somehow compile it for 64-bit
> Windows without needing to rely on a special DLL like the cygwin one.  I got
> stuck with trying to fix up the MSVC project file and I finally gave up on
> it.

The project file should be fine, once you add the missing entries. At
least it was always fine before.
I'll check it as soon as I manage to install windows on a virtual
machine, but this might be several days, as I am on holiday.

Also, I am not sure if MSVC objects and msys objects are binary
compatible. In general, can you compile Mathematica extensions with
both?

I remember that for R you *must* compile with msys/mingw, and for
Python you *must* compile with MSVC, otherwise the shared objects
cannot be loaded dynamically.

Gabor

> Szabolcs
>
> On 5 September 2015 at 21:13, Gábor Csárdi  wrote:
>>
>> 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 
>> 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 
>> > 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 
>> >> 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 so

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

[Szabolcs Horvát]

Hi Gabor,

Thank you for the comments.

Can you give me some hints on how you built igraph using the mingw
toolchain?

Did you compile a 32 or a 64 bit executable?  How did you run the configure
script?

I tried installing msys2  to be able to run the
configure script, and the mingw-w64 package to be able to compile for 64
bit systems.  Unfortunately the build process stops when the compiler
cannot find .  The configure script does correctly find out
that this header file is not available, but it still sets up a build
process that requires it.

I don't specifically need MSVC, I just need to somehow compile it for
64-bit Windows without needing to rely on a special DLL like the cygwin
one.  I got stuck with trying to fix up the MSVC project file and I finally
gave up on it.

Szabolcs

On 5 September 2015 at 21:13, Gábor Csárdi  wrote:

> 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 
> 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 
> 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 
> 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
> > igraph-help@nongnu.org
> > https://lists.nongnu.org/mailman/listinfo/igraph-help
> >
>
> ___
> igraph-help mailing list
> igraph-help@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/igraph-help
>
___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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  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  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  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
> igraph-help@nongnu.org
> https://lists.nongnu.org/mailman/listinfo/igraph-help
>

___
igraph-help mailing list
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Szabolcs Horvát]

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  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  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
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

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

[Szabolcs Horvát]

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  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
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help

[igraph] Easier way to compile igraph on Windows?

[Szabolcs Horvát]

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
igraph-help@nongnu.org
https://lists.nongnu.org/mailman/listinfo/igraph-help