unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: elaexuotee@wilsonb.com
To: guix-devel@gnu.org
Subject: Installing a wrapper guile script in <out>/bin
Date: Mon, 01 Feb 2021 20:28:34 +0900	[thread overview]
Message-ID: <3EA9135IVLYXR.223U6JDXT4SSS@wilsonb.com> (raw)

Hello Guix,

Writing package definition, I have need of a non-trivial wrapper script that
decides how to execute the installed binary. How do I accomplish this?

With my vague understanding, I am envisioning writing a gexp directly in the
install phase and would like to somehow reify this into a guile script and
install that file under <out>/bin. Is this correct, at the high level?

More specifically, the package I have builds separate libraries for CPUs with
AVX, AVX2, and no AVX support. Since build-type isn't sufficiently specific to
distinguish such CPU features, I have, so far, opted to just build all three
libs and stuff them under <out>/lib/<foo>.

My idea is to have the linker script check CPU features at runtime (by parsing
/proc/cpuinfo or something) and executing the binary with the parameters to
load the correct binary.

Perhaps there is a better overall approach?

Appreciate your thoughts!


             reply	other threads:[~2021-02-01 11:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-01 11:28 elaexuotee [this message]
2021-02-01 16:04 ` Installing a wrapper guile script in <out>/bin Ludovic Courtès
2021-02-03  5:50   ` elaexuotee
2021-02-03 10:00     ` Maxime Devos
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=3EA9135IVLYXR.223U6JDXT4SSS@wilsonb.com \
    --to=elaexuotee@wilsonb.com \
    --cc=guix-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/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).