unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: qtbase: Add search path specification for 'QMAKEPATH'.
Date: Fri, 19 Aug 2016 11:17:14 +0200	[thread overview]
Message-ID: <20160819091525.GA1341@solar> (raw)
In-Reply-To: <20160814061411.22314-1-iyzsong@gmail.com>

Hello 宋文武,

thanks a lot for solving this blocking problem!

On Sun, Aug 14, 2016 at 02:14:11PM +0800, 宋文武 wrote:
> +               ;; For each Qt module, let `qmake' uses search paths in the
> +               ;; module directory instead of all in QT_INSTALL_PREFIX.
> +               (substitute* qt_config.prf
> +                 (("\\$\\$\\[QT_INSTALL_HEADERS\\]")
> +                  "$$replace(dir, mkspecs/modules, include)")
> +                 (("\\$\\$\\[QT_INSTALL_LIBS\\]")
> +                  "$$replace(dir, mkspecs/modules, lib)")
> +                 (("\\$\\$\\[QT_HOST_LIBS\\]")
> +                  "$$replace(dir, mkspecs/modules, lib)")
> +                 (("\\$\\$\\[QT_INSTALL_PLUGINS\\]")
> +                  "$$replace(dir, mkspecs/modules, plugins)")
> +                 (("\\$\\$\\[QT_INSTALL_LIBEXECS\\]")
> +                  "$$replace(dir, mkspecs/modules, libexec)")
> +                 (("\\$\\$\\[QT_INSTALL_BINS\\]")
> +                  "$$replace(dir, mkspecs/modules, bin)")
> +                 (("\\$\\$\\[QT_INSTALL_IMPORTS\\]")
> +                  "$$replace(dir, mkspecs/modules, imports)")
> +                 (("\\$\\$\\[QT_INSTALL_QML\\]")
> +                  "$$replace(dir, mkspecs/modules, qml)"))

What do you think, would it make sense to file a bug upstream to suggest
the modifications above?

Andreas

      reply	other threads:[~2016-08-19  9:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-14  6:14 [PATCH] gnu: qtbase: Add search path specification for 'QMAKEPATH' 宋文武
2016-08-19  9:17 ` Andreas Enge [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

  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=20160819091525.GA1341@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.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).