unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxime Devos <maximedevos@telenet.be>
To: elaexuotee@wilsonb.com, "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: guix-devel@gnu.org
Subject: Re: Installing a wrapper guile script in <out>/bin
Date: Wed, 03 Feb 2021 11:00:24 +0100	[thread overview]
Message-ID: <6d41cb49f87561620e46f5e8a25946f2fbb927ab.camel@telenet.be> (raw)
In-Reply-To: <2VMUHEHLO03FL.3AF0SWRKGMFZ3@wilsonb.com>

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

> Say I have a script that reads /proc/cpuinfo and runs my executable with the
> correct flags to load the library with the best CPU features possible. How can
> I embed such a script in the package definition (as a gexp?) and install it
> under <out>/bin/?

Let's presume the binary is called $X.

What I would do: add a build phase after the "install" phase that renames
<out>/bin/$X to <out>/bin/.$X-real using the rename-file procedure.  Create
your wrapper script at <out>/bin/.$X-real with call-with-output-file, some
I/O procedures and chmod (to make the wrapper script executable).

I hope that helps, Maxime.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2021-02-03 10:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 11:28 Installing a wrapper guile script in <out>/bin elaexuotee
2021-02-01 16:04 ` Ludovic Courtès
2021-02-03  5:50   ` elaexuotee
2021-02-03 10:00     ` Maxime Devos [this message]
2021-02-03 11:04       ` elaexuotee--- via Development of GNU Guix and the GNU System distribution.
2021-02-03 12:12         ` Maxime Devos
2021-02-03 19:17           ` elaexuotee
2021-02-04  8:56             ` Maxime Devos
  -- strict thread matches above, loose matches on Subject: below --
2021-02-01 12:16 Leo Prikler

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=6d41cb49f87561620e46f5e8a25946f2fbb927ab.camel@telenet.be \
    --to=maximedevos@telenet.be \
    --cc=elaexuotee@wilsonb.com \
    --cc=guix-devel@gnu.org \
    --cc=ludovic.courtes@inria.fr \
    /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/guix.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).