all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: 宋文武 <iyzsong@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andreas Enge" <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: kde: Add kdelibs.
Date: Wed, 05 Nov 2014 21:49:39 +0800	[thread overview]
Message-ID: <871tphbvv0.fsf@gmail.com> (raw)
In-Reply-To: <87d2917plr.fsf@gnu.org>

Ludovic Courtès <ludo@gnu.org> writes:

> Andreas Enge <andreas@enge.fr> skribis:
>
>> thanks to Ludovic's help with debugging Qt and dbus, I finally have a working
>> recipe for kdelibs that allows me to compile the KDE "Hello, world"
>> tutorial at
>>   https://techbase.kde.org/Development/Tutorials/First_program
>
> This is good news.  :-)
>
>> It looks like all KDE programs require at least kdelibs, qt, phonon and
>> automoc4 to compile; but as these are not needed for running the program,
>> it seems inappropriate to make them propagated inputs.
>
> Right, this is not a reason to propagate them.
>
> Perhaps eventually you’ll find it convenient to have a specific build
> system with those listed as implicit inputs, though.
>
>> The configure flags
>>    "-DCMAKE_SHARED_LINKER_FLAGS=-lQtNetwork -lQtXml"
>>    "-DCMAKE_EXE_LINKER_FLAGS=-lQtCore"
>> look like bugs in kdelibs to me; but I wonder if reporting them makes sense.
>
> What does it fix?  Would be nice to leave a comment above it.
Hi, when packaging libqtxdg(using cmake and qt5), I find out that I have
to set CMAKE_SHARED_LINKER_FLAGS too to get qt5 into output's rpath.
Then I do a similar build for libqtxdg in nix for comparision, which do not
need to set this variable.

  reply	other threads:[~2014-11-05 13:50 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-04 21:37 [PATCH] gnu: kde: Add kdelibs Andreas Enge
2014-11-05 13:18 ` Ludovic Courtès
2014-11-05 13:49   ` 宋文武 [this message]
2014-11-05 19:22   ` Andreas Enge
  -- strict thread matches above, loose matches on Subject: below --
2014-11-05 19:50 Federico Beffa
2014-11-05 20:15 ` Ludovic Courtès
2014-11-05 20:28   ` Eric Bavier
2014-11-05 21:00     ` Federico Beffa
2014-11-05 21:18       ` Andreas Enge
2014-11-05 23:20         ` Andreas Enge
2014-11-06 11:46           ` Ludovic Courtès
2014-11-06 22:37             ` Andreas Enge
2014-11-06 22:54               ` Andreas Enge
2014-11-06 23:12                 ` Andreas Enge
2014-11-06 23:09               ` Eric Bavier
2014-11-06 23:24                 ` Andreas Enge
2014-11-07  9:20               ` Ludovic Courtès
2014-11-07 14:51                 ` Andreas Enge
2014-11-07 14:59               ` 宋文武
     [not found] <641d5f5d.31e3.14aaea456bc.Coremail.iyzsong@163.com>
2015-01-03  7:20 ` 宋文武
2015-01-03 11:06   ` Andreas Enge
2015-01-04 21:29   ` 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

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

  git send-email \
    --in-reply-to=871tphbvv0.fsf@gmail.com \
    --to=iyzsong@gmail.com \
    --cc=andreas@enge.fr \
    --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 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.