igraph-help
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[igraph] Re: igraph, visual studio c++ and libxml2


From: Francois Bastardie
Subject: [igraph] Re: igraph, visual studio c++ and libxml2
Date: Tue, 14 Dec 2010 14:18:58 +0100

Hello,
Thank you for your help. Indeed I had to modify config.h to set up HAVE_LIBXML 
to 1.
Nevertheless this is still not enough to run the graphml.c example with msvc 
2010 because it failed to compile with these hereafter message errors: 
"unresolved external symbols", and despite every indication to the contrary, it 
does not seems to be a problem of linkage to the dependent libraries. Actually 
I did a search over all the files of igraph and libxml2 and indeed these 
symbols are nowhere defined while they are required by foreign-graphml.c. Is 
that normal? What is missing? Am I wrong?
Best regards,

2>foreign-graphml.obj : error LNK2001: symbole externe non résolu 
_xmlGetPredefinedEntity
2>foreign-graphml.obj : error LNK2001: symbole externe non résolu _xmlStrEqual
2>foreign-graphml.obj : error LNK2001: symbole externe non résolu _xmlStrdup
2>foreign-graphml.obj : error LNK2001: symbole externe non résolu 
_xmlFreeParserCtxt
2>foreign-graphml.obj : error LNK2001: symbole externe non résolu _xmlParseChunk
2>foreign-graphml.obj : error LNK2001: symbole externe non résolu 
_xmlCreatePushParserCtxt


I put also hereafter the command lines in msvc when compiling igraph if anybody 
is used to:

1- for the Includes

/I"C:\igraph-0.5.5-msvc\src" /I"C:\igraph-0.5.5-msvc\winclude" 
/I"C:\libxml2-2.7.7.win32\include\libxml" 
/I"C:\igraph-0.5.5-msvc\winclude\libxml" /nologo /W3 /WX- /O2 /Oy- /D "Win32" 
/D "WIN32" /D "_WINDOWS" /D "_USRDLL" /D "IGRAPH_EXPORTS" /Gm- /EHsc /MD /GS 
/fp:precise /Zc:wchar_t /Zc:forScope /Fp"Release\igraph.pch" /Fa"Release\" 
/Fo"Release\" /Fd"Release\vc100.pdb" /Gd /analyze- /errorReport:queue

2- for the linker

/OUT:"Release\igraph.lib" /LIBPATH:"C:\libxml2-2.7.7.win32\lib" /NOLOGO

In that way I can produce the igraph.lib but then another project trying to use 
it (e.g. with the graphml.c example) will fail and return the fatal errors 
mentioned above.

-----Original Message-----
From: address@hidden [mailto:address@hidden On Behalf Of address@hidden
Sent: 11 December 2010 18:02
To: address@hidden
Subject: igraph-help Digest, Vol 53, Issue 11

Send igraph-help mailing list submissions to
        address@hidden

To subscribe or unsubscribe via the World Wide Web, visit
        http://lists.nongnu.org/mailman/listinfo/igraph-help
or, via email, send a message with subject or body 'help' to
        address@hidden

You can reach the person managing the list at
        address@hidden

When replying, please edit your Subject line so it is more specific
than "Re: Contents of igraph-help digest..."


Today's Topics:

   1. Re: igraph, visual studio c++ and libxml2 (Tamas Nepusz)


----------------------------------------------------------------------

Message: 1
Date: Fri, 10 Dec 2010 21:16:36 +0100
From: Tamas Nepusz <address@hidden>
Subject: Re: [igraph] igraph, visual studio c++ and libxml2
To: Help for igraph users <address@hidden>
Message-ID: <address@hidden>
Content-Type: text/plain; charset=us-ascii

> What I did is to set the PATH in msvc to C:\libxml2-2.7.7.win32\bin so that 
> the compiler would be able to find the libxml2.dll when needed, and I also 
> refer to the header files C:\igraph-0.5.5-msvc\winclude\libxml because 
> actually I have the header files already included in igraph-0.5.5-msvc (this 
> confuses me) ,  but this is obviously the wrong way or not enough...
It is the right way, but you also need one more step. Open up config.h and set 
the value of the HAVE_LIBXML macro to 1 instead of 0 which is the default on 
Windows (I guess).

-- 
Tamas




------------------------------

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


End of igraph-help Digest, Vol 53, Issue 11
*******************************************





reply via email to

[Prev in Thread] Current Thread [Next in Thread]