unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Andy Tai <lichengtai@gmail.com>
To: Leo Prikler <leo.prikler@student.tugraz.at>
Cc: 50054@debbugs.gnu.org
Subject: [bug#50054] [PATCH] gnu: Add bgfx
Date: Sat, 14 Aug 2021 11:24:57 -0700	[thread overview]
Message-ID: <CAJsg1E-vVB8NE=Zd9F_85n_oBwRpTbbn1cXa+kcmmT998Mo21g@mail.gmail.com> (raw)
In-Reply-To: <CAJsg1E-fyZ=vWtt2UXGXbtS07+z3ZxZgmu+09ozzaAhR9jM+2w@mail.gmail.com>

Or your intent is that each repo should be a separate package in guix,
like bgfx with its three git repos shall be three packages in guix?

On Sat, Aug 14, 2021 at 11:07 AM Andy Tai <lichengtai@gmail.com> wrote:
>
> Question: then how in the package definition can I check out
> submpodule repos and make them in the same relative positions for the
> build to work?
>
> On Sat, Aug 14, 2021 at 2:43 AM Leo Prikler
> <leo.prikler@student.tugraz.at> wrote:
> >
> > Hi,
> >
> > Am Samstag, den 14.08.2021, 01:35 -0700 schrieb Andy Tai:
> > > * gnu/packages/graphics.scm (bgfx): New variable
> > > ---
> > >  gnu/packages/graphics.scm | 38
> > > ++++++++++++++++++++++++++++++++++++++
> ...
> > > +         (method git-fetch)
> > > +         (uri
> > > +          (git-reference
> > > +           (url "https://github.com/bkaradzic/bgfx.cmake")
> > > +           (commit commit)
> > > +           ;; Fetch git submodules
> > > +           (recursive? #t)))
> > The use of submodules is discouraged because it's often hard to reason
> > about them.  This is such a case.  bgfx and the other submodules each
> > vendor a bunch of dependencies on top of the binaries that e.g. bx
> > ships as part of their tools repo.
> > > +         (file-name (git-file-name name version))
> > > +         (sha256
> > > +          (base32
> > > +           "1k18230zw3v2l0vgz5xi0l23fa0686yx0jd6hkvvvwp3zlakqp7n")))
> > > )
> > > +
> >
>
>
> --
> Andy Tai, atai@atai.org
> Year 2021 民國110年
> 自動的精神力是信仰與覺悟
> 自動的行為力是勞動與技能



-- 
Andy Tai, atai@atai.org
Year 2021 民國110年
自動的精神力是信仰與覺悟
自動的行為力是勞動與技能




  reply	other threads:[~2021-08-14 18:26 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-14  8:35 [bug#50054] [PATCH] gnu: Add bgfx Andy Tai
     [not found] ` <handler.50054.B.162893018622105.ack@debbugs.gnu.org>
2021-08-14  8:51   ` [bug#50054] Acknowledgement ([PATCH] gnu: Add bgfx) Andy Tai
2021-08-14  9:43 ` [bug#50054] [PATCH] gnu: Add bgfx Leo Prikler
2021-08-14 18:07   ` Andy Tai
2021-08-14 18:24     ` Andy Tai [this message]
2021-08-14 18:48       ` Leo Prikler
2021-08-16 12:42         ` Andy Tai
2021-08-16 12:52           ` Leo Prikler
2021-08-29  3:16             ` Andy Tai
2021-08-29  3:25               ` Andy Tai
2021-08-29  4:29                 ` Andy Tai
2021-08-29 11:41                   ` Leo Prikler
2021-08-29 18:21                     ` Andy Tai
2021-08-29 20:04                       ` Leo Prikler
2021-08-29 23:59                         ` Andy Tai
2021-08-27 17:49 ` [bug#50054] dependency Andy Tai
2021-08-27 18:31   ` Tobias Geerinckx-Rice via Guix-patches via
2024-04-23  5:51 ` [bug#50054] [PATCH v2 0/3] *** Add bgfx and dependencies *** Andy Tai
2024-04-23  5:51   ` [bug#50054] [PATCH v2 1/3] gnu: Add bx Andy Tai
2024-05-13 12:37     ` Ludovic Courtès
2024-04-23  5:51   ` [bug#50054] [PATCH v2 2/3] gnu: Add bimg Andy Tai
2024-04-23  5:51   ` [bug#50054] [PATCH v2 3/3] gnu: Add bgfx Andy Tai
2024-05-13 12:40     ` Ludovic Courtès
2024-05-17  6:17 ` [bug#50054] [PATCH v3 0/3] Add bgfx and dependencies Andy Tai
2024-05-17  6:17   ` [bug#50054] [PATCH v3 1/3] gnu: Add bx Andy Tai
2024-05-17  6:17   ` [bug#50054] [PATCH v3 2/3] gnu: Add bimg Andy Tai
2024-05-17  6:17   ` [bug#50054] [PATCH v3 3/3] gnu: Add bgfx Andy Tai
2024-05-18  6:22 ` [bug#50054] [PATCH v3 0/3] Add bgfx and dependencies Andy Tai
2024-05-18  6:22   ` [bug#50054] [PATCH v3 1/3] gnu: Add bx Andy Tai
2024-05-18  6:22   ` [bug#50054] [PATCH v3 2/3] gnu: Add bimg Andy Tai
2024-05-18  6:22   ` [bug#50054] [PATCH v3 3/3] gnu: Add bgfx Andy Tai
2024-05-27  0:44 ` [bug#50054] ping Andy Tai

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='CAJsg1E-vVB8NE=Zd9F_85n_oBwRpTbbn1cXa+kcmmT998Mo21g@mail.gmail.com' \
    --to=lichengtai@gmail.com \
    --cc=50054@debbugs.gnu.org \
    --cc=leo.prikler@student.tugraz.at \
    /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).