all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: brettg@posteo.net
Cc: help-guix <help-guix@gnu.org>
Subject: Re: checking out a shebang-patched package source
Date: Fri, 29 Mar 2019 20:27:25 +0100	[thread overview]
Message-ID: <87sgv5zdk2.fsf@elephly.net> (raw)
In-Reply-To: <e76c7dae4117c84e4bbfbd68e9f01865@posteo.net>


brettg@posteo.net writes:

> I am trying to compile the newest Chez Scheme locally from a git
> checkout. There are a number of shebang patches that have to be done
> for it to compile "traditionally" (not using the guix build
> --with-source) so I can generate a .compile_commands for my lsp to
> know how to reference headers and such.

I don’t know what a “lsp” and “.compile_commands” is.

> Is there a way to get guix to modify those files that it patches on my
> local checkout so I dont have to go through manually modifying it
> myself?

No, there isn’t.  Generally, patches that are applied in a snippet are
performed before the build starts, so that you can get the modified
source code with “guix build -S the-package”, but patching shebangs is
done as part of the gnu-build-system build phases.

You can attempt to execute the procedures that make up the
gnu-build-system manually, but there’s no quick way to do this
automatically.

--
Ricardo

      parent reply	other threads:[~2019-03-29 19:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-23  4:27 checking out a shebang-patched package source brettg
2019-03-27  1:56 ` Brett Gilio
2019-03-28 21:06   ` Jack Hill
2019-03-29 19:27 ` Ricardo Wurmus [this message]

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

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

  git send-email \
    --in-reply-to=87sgv5zdk2.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=brettg@posteo.net \
    --cc=help-guix@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.