bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Bruno Haible <bruno@clisp.org>
To: "Tim Rühsen" <tim.ruehsen@gmx.de>
Cc: bug-gnulib@gnu.org, jemarch@gnu.org
Subject: Re: Unicode support in poke
Date: Mon, 13 Jan 2020 12:01:40 +0100	[thread overview]
Message-ID: <8824791.IuzVZ8UCoK@omega> (raw)
In-Reply-To: <3698f27c-ad25-14f7-09b0-1cb5b1a5cad1@gmx.de>

Hi Tim,

> you could look at libidn2 as an example how to use system libunistring
> if there (or if new enough) and fallback to gnulib unistring.
> (BTW, libunistring is made of the gnulib unistring modules)
> 
> It creates a separate dir / library for gnulib unistring functions,
> *BUT* only uses it when a system libunistring can't be found.
> 
> bootstrap.conf: Call gnulib-tool in bootstrap_post_import_hook() only
> for the needed unistring modules.
> 
> configure.ac: Check for system libunistring (set a conditional
> HAVE_LIBUNISTRING
> 
> Makefile.am: if !HAVE_LIBUNISTRING -> add unistring/ to SUBDIR
> 
> */Makefile.am: if !HAVE_LIBUNISTRING -> add unistring/ to includes in
> AM_CPPFLAGS

A simpler way to achieve the same thing is to include the gnulib module
'libunistring-optional'. It will use the system libunistring if it
exists and is new enough, and otherwise compile the respective modules
from source.

Bruno



  reply	other threads:[~2020-01-13 11:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-13 10:33 Unicode support in poke Bruno Haible
2020-01-13 10:50 ` Tim Rühsen
2020-01-13 11:01   ` Bruno Haible [this message]
2020-01-13 11:08     ` Tim Rühsen
2020-01-13 11:52       ` Bruno Haible

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://lists.gnu.org/mailman/listinfo/bug-gnulib

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8824791.IuzVZ8UCoK@omega \
    --to=bruno@clisp.org \
    --cc=bug-gnulib@gnu.org \
    --cc=jemarch@gnu.org \
    --cc=tim.ruehsen@gmx.de \
    /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.
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).