[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: Plasma 5 is awesome...and some help required with build instructions
From:       Siddhartha <sh.siddhartha () gmail ! com>
Date:       2015-05-19 1:22:57
Message-ID: CAErGNGbuVzeLm+CUQUG=kZa+ajiGpfGgPtFmyy=u5ULa1h8qaQ () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 18 May 2015 at 22:58, David Edmundson <david@davidedmundson.co.uk> wrote:

> Just setting up on a new machine and thought I'd try following these
> instructions exactly, the way a new developer would.
>
> I got stuck on something I don't know how to solve.
>
> Under Kubuntu because Qt is compiled with a hardcoded plugindir for some
> reason.
> This means setting QT_PLUGIN_PATH env variables does nothing, which means
> you'll always be loading any plugins from /usr/ rather than the ones we
> just built.
>
> How did you get round that? Any ideas?
>

By using Arch Linux? :P

I did not do anything special in this regard, so I guess on my system
QT_PLUGIN_PATH is being picked up properly.

Btw, you commented out QTDIR in the wiki script, so a few of the later
variables will have weird paths (QTDIR/plugins=/plugins)

[Attachment #5 (text/html)]

<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 18 May 2015 at \
22:58, David Edmundson <span dir="ltr">&lt;<a \
href="mailto:david@davidedmundson.co.uk" \
target="_blank">david@davidedmundson.co.uk</a>&gt;</span> wrote:<br><blockquote \
class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid \
rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><div>Just setting up on a \
new machine and thought I&#39;d try following these instructions exactly, the way a \
new developer would.<br><br></div><div>I got stuck on something I don&#39;t know how \
to solve.<br></div></div><div><br></div>Under Kubuntu because Qt is compiled with a \
hardcoded plugindir for some reason.<br>This means setting QT_PLUGIN_PATH env \
variables does nothing, which means you&#39;ll always be loading any plugins from \
/usr/ rather than the ones we just built. <br><br>How did you get round that? Any \
ideas?<span class=""></span></div></div></blockquote><div><br></div><div>By using \
Arch Linux? :P<br><br></div><div>I did not do anything special in this regard, so I \
guess on my system QT_PLUGIN_PATH is being picked up properly.<br></div><div><br>Btw, \
you commented out QTDIR in the wiki script, so a few of the later variables will have \
weird paths (<span class="">QTDIR</span><span \
class="">/</span>plugins=/plugins)<br><br></div></div></div></div>


[Attachment #6 (text/plain)]

_______________________________________________
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel


[prev in list] [next in list] [prev in thread] [next in thread]