unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Qt/KDE build system?
Date: Tue, 26 Nov 2019 12:09:57 +0100	[thread overview]
Message-ID: <adf89b1f-07cc-6fc0-7c14-57e5b720d1a1@crazy-compilers.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1014 bytes --]

Hi,

Ludo wrote:

> 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.

Many thanks for this valuable hint!

I've build a prototype and found two issues:

1. qt-build-system.scm is basically a copy of cmake-build-system.scm,
with just a few lines changed. IMHO this is not good, esp. in regard to
maintenance. I tried reusing variable using e.g. "(@ (guix build-systm
cmake) default-cmake)", but this said "symbol not found". Any other ideas?

2. The wrapper collects paths from *all* inputs, thus e.g. cmake will
become a dependency of *every* binary packages using qt-build-system.
(The current ((guix build utils) qt-warp) has the same issue.


-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2019-11-26 11:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 11:09 Hartmut Goebel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-23 13:12 Qt/KDE build system? Hartmut Goebel
2019-11-23 16:53 ` Ludovic Courtès

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=adf89b1f-07cc-6fc0-7c14-57e5b720d1a1@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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).