From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Qt/KDE build system?
Date: Sat, 23 Nov 2019 17:53:38 +0100 [thread overview]
Message-ID: <87eexy5yb1.fsf@gnu.org> (raw)
In-Reply-To: <8fffdfae-c89e-1b82-08f9-396fb1f88666@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 23 Nov 2019 14:12:18 +0100")
Hi!
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> I'm currently packaging some KDE applications and find myself adding
> this to each of the package descriptions:
>
> (arguments
> `(#:modules ((guix build cmake-build-system)
> (guix build qt-utils)
> (guix build utils))
> #:imported-modules (,@%cmake-build-system-modules
> (guix build qt-utils))
> #:phases
> (modify-phases %standard-phases
> (add-after 'install 'wrap-executable
> (lambda* (#:key outputs #:allow-other-keys)
> (let ((out (assoc-ref outputs "out")))
> (wrap-qt-program out "lskat"))
> #t)))))
>
> IMHO it would make sense to have some Qt/KDE build system or a flag for
> the cmake-build-system so these code replication can be avoided.
I agree.
> How shall de approach this?
I think you could come up with a ‘qt-build-system’ (is that an
appropriate name?) that simply adds the things above on top of
‘gnu-build-system’, similar to what ‘glib-or-gtk-build-system’ does.
HTH!
Ludo’.
next prev parent reply other threads:[~2019-11-23 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-23 13:12 Qt/KDE build system? Hartmut Goebel
2019-11-23 16:53 ` Ludovic Courtès [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-11-26 11:09 Hartmut Goebel
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=87eexy5yb1.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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).