From: Robert Pluim <rpluim@gmail.com>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: What's the right way to detect libxml2?
Date: Tue, 24 Oct 2017 19:04:54 +0200 [thread overview]
Message-ID: <877evkfpe1.fsf@gmail.com> (raw)
In-Reply-To: <vz14lqov9vz.fsf@gmail.com> (Andy Moreton's message of "Tue, 24 Oct 2017 16:33:04 +0100")
[-- Attachment #1: Type: text/plain, Size: 705 bytes --]
Andy Moreton <andrewjmoreton@gmail.com> writes:
> On Tue 24 Oct 2017, Clément Pit-Claudel wrote:
>
>> On 2017-10-24 09:38, Andy Moreton wrote:
>>> For libxml2, try using (shr-render-buffer) on an HTML/XML buffer to get
>>> the library loaded.
>>
>> Is that better than just calling libxml-parse-xml-region and checking for a
>> nil return value? It sounds like shr-render-buffer would do a lot more — do we
>> need that?
>
> No, it was just an example of doing something to force the library to be
> loaded. Your version is simpler, and having (libxml-available-p) would
> be even better.
>
> AndyM
Like thus? Very lightly tested on GNU/Linux only. Might need a NEWS
entry.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Provide-libxml-available-p.patch --]
[-- Type: text/x-diff, Size: 2696 bytes --]
From e74de0a485009918d71d0643bc03195b5fd01761 Mon Sep 17 00:00:00 2001
From: Robert Pluim <rpluim@gmail.com>
Date: Tue, 24 Oct 2017 19:01:28 +0200
Subject: [PATCH] Provide libxml-available-p
* src/emacs.c (main): Call syms_of_xml unconditionally
* src/lisp.h: Provide syms_of_xml prototype even when
HAVE_LIBXML2 is not defined
* src/xml.c (Flibxml_available_p): New function, cloned from
Fgnutls_available_p
(syms_of_xml): Provide Slibxml_available_p
---
src/emacs.c | 2 --
src/lisp.h | 2 +-
src/xml.c | 31 +++++++++++++++++++++++++++++--
3 files changed, 30 insertions(+), 5 deletions(-)
diff --git a/src/emacs.c b/src/emacs.c
index 0fe7d9113b..808abcd9aa 100644
--- a/src/emacs.c
+++ b/src/emacs.c
@@ -1542,9 +1542,7 @@ Using an Emacs configured with --with-x-toolkit=lucid does not have this problem
#endif
#endif /* HAVE_X_WINDOWS */
-#ifdef HAVE_LIBXML2
syms_of_xml ();
-#endif
#ifdef HAVE_LCMS2
syms_of_lcms2 ();
diff --git a/src/lisp.h b/src/lisp.h
index 266370333f..cc8d90cbf1 100644
--- a/src/lisp.h
+++ b/src/lisp.h
@@ -4399,9 +4399,9 @@ extern void syms_of_xterm (void);
extern char *x_get_keysym_name (int);
#endif /* HAVE_WINDOW_SYSTEM */
-#ifdef HAVE_LIBXML2
/* Defined in xml.c. */
extern void syms_of_xml (void);
+#ifdef HAVE_LIBXML2
extern void xml_cleanup_parser (void);
#endif
diff --git a/src/xml.c b/src/xml.c
index d087a34a5e..825d5a0f64 100644
--- a/src/xml.c
+++ b/src/xml.c
@@ -291,16 +291,43 @@ If DISCARD-COMMENTS is non-nil, all HTML comments are discarded. */)
return parse_region (start, end, base_url, discard_comments, false);
return Qnil;
}
+#endif /* HAVE_LIBXML2 */
\f
+
+DEFUN ("libxml-available-p", Flibxml_available_p, Slibxml_available_p, 0, 0, 0,
+ doc: /* Return list of capabilities if LibXML2 is available in this instance of Emacs.*/)
+ (void)
+{
+#ifdef HAVE_LIBXML2
+# ifdef WINDOWSNT
+ Lisp_Object found = Fassq (Qlibxml2, Vlibrary_cache);
+ if (CONSP (found))
+ return XCDR (found);
+ else
+ {
+ Lisp_Object status;
+ status = init_libxml2_functions () ? Qt : Qnil;
+ Vlibrary_cache = Fcons (Fcons (Qlibxml2, status), Vlibrary_cache);
+ return status;
+ }
+# else
+ return Qt;
+# endif /* WINDOWSNT */
+#else
+ return Qnil;
+#endif /* HAVE_LIBXML2 */
+}
+
/***********************************************************************
Initialization
***********************************************************************/
void
syms_of_xml (void)
{
+#ifdef HAVE_LIBXML2
defsubr (&Slibxml_parse_html_region);
defsubr (&Slibxml_parse_xml_region);
+#endif
+ defsubr (&Slibxml_available_p);
}
-
-#endif /* HAVE_LIBXML2 */
--
2.15.0.rc1
next prev parent reply other threads:[~2017-10-24 17:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-22 14:14 What's the right way to detect libxml2? Clément Pit-Claudel
2017-10-22 16:27 ` Phillip Lord
2017-10-24 13:38 ` Andy Moreton
2017-10-24 14:01 ` Clément Pit-Claudel
2017-10-24 15:33 ` Andy Moreton
2017-10-24 17:04 ` Robert Pluim [this message]
2017-10-24 17:46 ` Andy Moreton
2017-10-25 11:24 ` Robert Pluim
2017-10-28 9:10 ` Eli Zaretskii
2017-10-30 8:49 ` Robert Pluim
2017-10-30 18:07 ` Eli Zaretskii
2017-10-30 18:10 ` Eli Zaretskii
2017-11-03 9:36 ` Eli Zaretskii
2017-11-03 17:17 ` Robert Pluim
2017-10-24 21:49 ` Richard Stallman
2017-10-24 22:32 ` John Wiegley
2017-10-25 1:45 ` Stefan Monnier
2017-10-25 22:05 ` Paul Eggert
2017-10-26 3:42 ` Richard Stallman
2017-10-25 4:39 ` Werner LEMBERG
2017-10-25 7:19 ` To Tramp or not to Tramp (was: What's the right way to detect libxml2?) Michael Albinus
2017-10-25 10:56 ` Kaushal Modi
2017-10-26 7:56 ` To Tramp or not to Tramp martin rudalics
2017-10-27 2:44 ` Richard Stallman
2017-10-27 4:01 ` John Wiegley
2017-10-27 20:58 ` Richard Stallman
2017-10-25 22:29 ` What's the right way to detect libxml2? Richard Copley
2017-10-26 10:48 ` Marcin Borkowski
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=877evkfpe1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=andrewjmoreton@gmail.com \
--cc=emacs-devel@gnu.org \
/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).