宋文武 skribis:
>> Andreas Enge skribis:
>>
>>> RUNPATH
>>> /gnu/store/7c30kyzagk84inhnb2nbxcmnh76xgh6c-ktouch-4.14.2/lib:/gnu/store/4k20pkxgvfc22wpcvh6xr26ma4b619ad-glibc-2.20/lib:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3lq8a5n-gcc-4.8.3-lib/lib64:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3l
On Sat, Jan 03, 2015 at 03:20:45PM +0800, 宋文武 wrote:
> We have not change ld-wrapper for this right?
Not yet, but I think we should do it soon.
Andreas
> Andreas Enge skribis:
>
>> RUNPATH
>> /gnu/store/7c30kyzagk84inhnb2nbxcmnh76xgh6c-ktouch-4.14.2/lib:/gnu/store/4k20pkxgvfc22wpcvh6xr26ma4b619ad-glibc-2.20/lib:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3lq8a5n-gcc-4.8.3-lib/lib64:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3lq8a5n-gcc-4.8.3-lib
Andreas Enge writes:
> On Thu, Nov 06, 2014 at 12:46:21PM +0100, Ludovic Courtès wrote:
>> Apologies if this was already mentioned, but why don’t
>> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=TRUE and
>> -DCMAKE_INSTALL_RPATH=$out/lib (in cmake-build-system.scm) lead to
>> binaries with a RUNPATH? As E
On Fri, Nov 07, 2014 at 10:20:15AM +0100, Ludovic Courtès wrote:
> Our ld-wrapper is ineffective when the .so file names are passed
> directly like this. That is, ld-wrapper adds -rpath for any -l switch,
> but it does not add -rpath for libraries whose absolute file name is
> specified.
>
> That
Andreas Enge skribis:
> RUNPATH
> /gnu/store/7c30kyzagk84inhnb2nbxcmnh76xgh6c-ktouch-4.14.2/lib:/gnu/store/4k20pkxgvfc22wpcvh6xr26ma4b619ad-glibc-2.20/lib:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3lq8a5n-gcc-4.8.3-lib/lib64:/gnu/store/k7w7wdpvaqlkwq0ijz9149pqn3lq8a5n-gcc-4.8.3-lib/lib:
On Thu, Nov 06, 2014 at 05:09:35PM -0600, Eric Bavier wrote:
> As I understand things, cmake might relink executables during
> installation with the appropriate rpath for the installation directory.
> It may also patch the executables rpath in place, replacing the
> "..." string above with the
In nixpkgs, the file for ktouch looks like this:
{ kde, kdelibs, libxkbfile }:
kde {
buildInputs = [ kdelibs libxkbfile ];
meta = {
description = "Touch Typing Tutor";
};
}
Where do I find the "definition" of what could probably be called the
kde build system?
Andreas
Andreas Enge writes:
> -Wl,-rpath,:
As I understand things, cmake might relink executables during
installation with the appropriate rpath for the installation directory.
It may also patch the executables rpath in place, replacing the
":
On Thu, Nov 06, 2014 at 11:37:44PM +0100, Andreas Enge wrote:
> Does this mean that this option only honours paths coming from "-l", while
> at the same time using "-l" is unusual with cmake?
Actually I do not know about the second part of the sentence, but the first
one seems to be true. When I a
On Thu, Nov 06, 2014 at 12:46:21PM +0100, Ludovic Courtès wrote:
> Apologies if this was already mentioned, but why don’t
> -DCMAKE_INSTALL_RPATH_USE_LINK_PATH=TRUE and
> -DCMAKE_INSTALL_RPATH=$out/lib (in cmake-build-system.scm) lead to
> binaries with a RUNPATH? As Eric said, this should produce
Andreas Enge skribis:
> On Wed, Nov 05, 2014 at 10:18:18PM +0100, Andreas Enge wrote:
>> It definitely sounds like a good idea. We could add the rpath linker flags
>> for Qt and for KDE via -DCMAKE_SHARED_LINKER_FLAGS and
>> -DCMAKE_EXE_LINKER_FLAGS to the kde build system. I would like to give
>
uld implement, or does anyone have a better idea
or an argument why this would be bad?
Andreas
>From 4c82ecb734da93dbe8d41a0466b1cd20ab52981f Mon Sep 17 00:00:00 2001
From: Andreas Enge
Date: Tue, 4 Nov 2014 21:44:16 +0100
Subject: [PATCH] gnu: kde: Add kdelibs.
* gnu/packages/kde.scm (kd
On Wed, Nov 05, 2014 at 10:00:12PM +0100, Federico Beffa wrote:
> I'm using glib-or-gtk-build-system (which I'm refining). So, it is
> mostly the gnu-build-system. But, in the end of the day, the option is
> just a parameter for the linker and I thought it may help... but maybe
> not.
It definitel
On Wed, Nov 5, 2014 at 9:28 PM, Eric Bavier wrote:
>
> Ludovic Courtès writes:
>
>> Federico Beffa skribis:
>>
>> What build system does dconf use?
I'm using glib-or-gtk-build-system (which I'm refining). So, it is
mostly the gnu-build-system. But, in the end of the day, the option is
just a par
Ludovic Courtès writes:
> Federico Beffa skribis:
>
>> I'm working on dconf and I had the same problem: the produced binaries
>> like dconf-edit, but even shared libraries produced by the build would
>> not find their own companions.
>
> What build system does dconf use?
>
> Usually there’s no p
Federico Beffa skribis:
> I'm working on dconf and I had the same problem: the produced binaries
> like dconf-edit, but even shared libraries produced by the build would
> not find their own companions.
What build system does dconf use?
Usually there’s no problem for packages that use Libtool (
Andreas Enge writes:
> As usual, the libraries and binaries are not explicitly linked with the
> libraries they depend on. So in a context where the input libraries are not
> in /usr/lib, executing binaries fails.
>
> In my private branch I also tried to compile a few KDE packages. The same
> prob
Thanks for your comments!
On Wed, Nov 05, 2014 at 02:18:24PM +0100, Ludovic Courtès wrote:
> Perhaps eventually you’ll find it convenient to have a specific build
> system with those listed as implicit inputs, though.
This sounds like a good idea. I considered a "define" with a list of the
basic
Ludovic Courtès writes:
> Andreas Enge 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 g
Andreas Enge 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
Hello,
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
It looks like all KDE programs require at least kdelibs, qt, phonon a
22 matches
Mail list logo
