bug-gnulib@gnu.org mirror (unofficial)
 help / color / mirror / Atom feed
From: Reuben Thomas <rrt@sc3d.org>
To: Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib <bug-gnulib@gnu.org>
Subject: Re: 'relocatable' project built without --enable-relocatable
Date: Tue, 23 Apr 2024 21:58:37 +0200	[thread overview]
Message-ID: <CAOnWdogHhe9ArvNsgT1xPFvOUxxP1Vr4r+qGHYGprFZnTsnq8g@mail.gmail.com> (raw)
In-Reply-To: <346536552.tGq8MHzOUc@nimes>

[-- Attachment #1: Type: text/plain, Size: 1055 bytes --]

On Tue, 23 Apr 2024 at 21:46, Bruno Haible <bruno@clisp.org> wrote:

> How does or would the code you are talking about look like, with #ifs?
> And would it be code for a library, or for a program?
>

For a library. For example, from the libpaper commit referenced below,
using #ifdefs:

/* Set the prefix directory for relocation. */
void papersetprefixdir(const char *new_prefix)
{
#ifdef ENABLE_RELOCATABLE
    set_relocation_prefix (INSTALLPREFIX, new_prefix);
#else
    (void)new_prefix;
#endif
}

I'm asking because no package I know of is using set_relocation_prefix
> explicitly [1]

I've been using it in Enchant since 2017[1] and in libpaper since 2021[2]

[1] https://github.com/AbiWord/enchant/commit/a8e771a

(this is definitely in Debian by now)

[2]
https://github.com/rrthomas/libpaper/commit/13bb68b87fdc0b20e08adf58146576fd120d3f3b

(not yet in Debian, sadly, as they don't like me "vendoring gnulib", as FTP
Master calls it, or "using gnulib as other packages like Enchant do, and as
designed", as I call it).

-- 
https://rrt.sc3d.org

[-- Attachment #2: Type: text/html, Size: 3289 bytes --]

  reply	other threads:[~2024-04-23 19:59 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-23 10:27 'relocatable' project built without --enable-relocatable Reuben Thomas
2024-04-23 19:46 ` Bruno Haible
2024-04-23 19:58   ` Reuben Thomas [this message]
2024-04-23 23:24     ` Bruno Haible
2024-04-24 20:36       ` Reuben Thomas
2024-04-25 12:07         ` Bruno Haible
2024-04-25 12:22           ` Reuben Thomas
2024-04-23 23:51     ` Gnulib in Debian Bruno Haible
2024-04-24 11:26       ` Reuben Thomas
2024-04-24 13:56         ` Simon Josefsson via Gnulib discussion list
2024-04-24 19:15           ` Reuben Thomas
2024-04-25 13:29           ` GNULIB_REVISION Bruno Haible
2024-04-25 16:26             ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 17:00               ` GNULIB_REVISION Paul Eggert
2024-04-25 17:43                 ` GNULIB_REVISION Simon Josefsson via Gnulib discussion list
2024-04-25 18:49                   ` GNULIB_REVISION Paul Eggert
2024-04-25 17:48                 ` GNULIB_REVISION Collin Funk

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=CAOnWdogHhe9ArvNsgT1xPFvOUxxP1Vr4r+qGHYGprFZnTsnq8g@mail.gmail.com \
    --to=rrt@sc3d.org \
    --cc=bruno@clisp.org \
    --cc=bug-gnulib@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.
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).