RE: [Bug-gnubg] New gnubg-no-gui.exe unable to read MET

[macherius]

I noted Jon last week that after recent patches loading the MET started
having problems. This is true here as well, but for "file not found" reasons
rather than linking issues. However, my suspicion is that even if you linked
libxml successfully there was MET trouble with the current CVS version.

The suspect patch is this one: "Tue Feb  7  17:56:45 2005 GMT  Jon Kinsey
<address@hidden> * gnubg.c: change get install dir to look at path
to exe (windows)." Around that time MET loading broke in my compiles.

Ingo

> -----Original Message-----
> From: address@hidden [mailto:address@hidden 
> Sent: Tuesday, February 15, 2005 11:23 PM
> To: macherius
> Cc: address@hidden
> Subject: Re: [Bug-gnubg] New gnubg-no-gui.exe unable to read MET
> 
> 
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> macherius wrote:
> | Ther new 1.3 release for Windows can not loads METs, libxml2 is not
> linked.
> | To my suprise "show buildinfo" claims XML support, but a look at the
> actual
> | binary using a PE tool shows Python and Glib are the only 
> non-system 
> | libs linked (e.g. no PNG for batch exports).
> 
> It's actually true for the gui version as well. The biggest 
> problem is that I don't understand why? I'll take a look at right now.
> 
> - -Øystein
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (MingW32)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> 
> iD8DBQFCEnZT6kDTFPhwyqYRAjUIAJ9QJX1irkz7WePJM7p80eYXB2fD1QCdEBfP
> YtPuSQgpFsO1rkMVB8ZVEH8=
> =oVO8
> -----END PGP SIGNATURE-----
> 
>