From: Juan José Rodríguez (jrodrisa@gobierno.jalisco.gob.mx)
Date: Tue Oct 03 2000 - 19:51:18 EDT
-----Mensaje original-----
De: Daniel Veillard [mailto:Daniel.Veillard@w3.org]
Enviado el: Lunes, 02 de Octubre de 2000 06:20 p.m.
[Daniel]
On Mon, Oct 02, 2000 at 05:46:40PM -0500, Timothee Besset wrote:
>
> Why does the configure script creates a libxml symlink which points to
> the main dir? Are the #include "libxml/*.h" from old code that relied on
> a libxml/ directory? This is causing problems for win32 builds.
This is not a legacy problem it's a current problem
Includes have to be made <libxml/xxx.h> though the .h are in the
same directory as the .c . To cope with the issue I used a symlink
this work on unix, I don't know how you can do this on Windows
[jrod]
In win32 a easy way to handle this --without changing the sources--,
is renaming the directory where the source is to "libxml" and add
".." to the include path.
This works with Visual C++ 6.0 sp4 with a Makefile and I think this
will work with a project (*.dsp) file.
Greetings,
Juan José Rodríguez
---- Message from the list xml@rpmfind.net Archived at : http://xmlsoft.org/messages/ to unsubscribe: echo "unsubscribe xml" | mail majordomo@rpmfind.net
This archive was generated by hypermail 2b29 : Tue Oct 03 2000 - 20:43:15 EDT