From: Eli Zaretskii <eliz@gnu.org>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: cschol2112@googlemail.com, emacs-devel@gnu.org
Subject: Re: Included libraries in the Windows binary distribution
Date: Sun, 05 Feb 2012 22:54:21 +0200 [thread overview]
Message-ID: <8362flc876.fsf@gnu.org> (raw)
In-Reply-To: <CAAeL0SQbBu5CF3_AQ_W4dCEOGOm6oFZWKEy4rRVKOEXNP_Y7aw@mail.gmail.com>
> From: Juanma Barranquero <lekktu@gmail.com>
> Date: Sun, 5 Feb 2012 20:52:27 +0100
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> On Sun, Feb 5, 2012 at 20:27, Christoph Scholtes
> <cschol2112@googlemail.com> wrote:
>
> > So I successfully compiled with the patch and the libraries, however
> > during bootstrap I got "libxml2 library not found" all over the place
> > during compilation of elisp files. It shows up after compilation of
> > every single .elc file. Is this expected? I don't have the
> > binaries on the path anywhere. Just wondering where this output is
> > generated.
>
> Here.
>
> + if (!(library = w32_delayed_load (libraries, Qlibxml2_dll)))
> + {
> + message ("%s", "libxml2 library not found");
> + return 0;
> + }
>
> Every .el compiled is one instance of emacs (in batch mode) that fails
> to find the library and outputs the message.
The question is: why does it even try to find it? And the answer is
that Emacs unconditionally calls xmlCleanupParser on exit, and that
call tries to load the library.
I will fix that.
> I think the message is not necessary (we don't warn if we don't find
> libpng3 or GnuTLS, for example).
Oh, yes, we do:
static int
init_gnutls_functions (Lisp_Object libraries)
{
HMODULE library;
int max_log_level = 1;
if (!(library = w32_delayed_load (libraries, Qgnutls_dll)))
{
GNUTLS_LOG (1, max_log_level, "GnuTLS library not found");
return 0;
}
> > Also, once I have compiled support in, how can I test it?
>
> Use libxml-parse-(xml|html)-region.
Yes, that's how I tested it.
These functions are slow, btw.
next prev parent reply other threads:[~2012-02-05 20:54 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 23:55 Included libraries in the Windows binary distribution Lars Magne Ingebrigtsen
2012-01-04 1:09 ` Juanma Barranquero
2012-01-04 3:10 ` Lars Magne Ingebrigtsen
2012-01-04 5:10 ` Eli Zaretskii
2012-01-04 5:09 ` Eli Zaretskii
2012-02-04 13:42 ` Eli Zaretskii
2012-02-05 0:37 ` Juanma Barranquero
2012-02-05 16:32 ` Eli Zaretskii
2012-02-05 3:00 ` Christoph Scholtes
2012-02-05 16:32 ` Eli Zaretskii
2012-02-05 19:27 ` Christoph Scholtes
2012-02-05 19:52 ` Juanma Barranquero
2012-02-05 20:54 ` Eli Zaretskii [this message]
2012-02-05 21:21 ` Juanma Barranquero
2012-02-05 21:45 ` Christoph Scholtes
2012-02-06 13:10 ` Ted Zlatanov
2012-02-07 2:48 ` Christoph Scholtes
2012-02-08 4:02 ` Eli Zaretskii
2012-02-08 19:16 ` Stefan Monnier
2012-02-10 10:32 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8362flc876.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cschol2112@googlemail.com \
--cc=emacs-devel@gnu.org \
--cc=lekktu@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).