Re: Plasma 5 is awesome...and some help required with build instructions
On Tue, May 19, 2015 at 2:10 AM, Siddhartha sh.siddhar...@gmail.com wrote: On 18 May 2015 at 22:58, David Edmundson da...@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. Yes, it's only a problem on Kubuntu. But someone who wrote this must have been a Kubuntu user, there is a list of dependencies. It's also solvable by compiling Qt, but I don't really want to have to force new devs to do that unless I have to. Btw, you commented out QTDIR in the wiki script, so a few of the later variables will have weird paths (QTDIR/plugins=/plugins) Ah, yes, it's better to have it try to access a folder that doesn't exist. Thanks, fixed. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On Tue, May 19, 2015 at 12:30 PM, David Edmundson da...@davidedmundson.co.uk wrote: But someone who wrote this must have been a Kubuntu user, there is a list of dependencies. That was added by me about 2 weeks ago when I tried to follow that setup as well on a clean system where I had to figure out all the deps. So I thought it might come handy to others and added it there. Nevertheless, I also hit the same problem as you did. I didn't solve it yet because my laptop has other (more severe) issues with Linux currently. Cheers -- Martin Klapetek | KDE Developer ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On 19 May 2015 at 16:00, David Edmundson da...@davidedmundson.co.uk wrote: Yes, it's only a problem on Kubuntu. It's also solvable by compiling Qt, but I don't really want to have to force new devs to do that unless I have to. We should talk to the Kubuntu devs to see why its hardcoded that way, and ask them to remove that config option if possible. If not, the other way would be to use KDE_INSTALL_USE_QT_SYS_PATHS as Alex mentioned and add 'make-install-prefix sudo' to the kdesrc-build config. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
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? David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On Mon, May 18, 2015 at 7:05 PM, Aleix Pol aleix...@kde.org wrote: On Mon, May 18, 2015 at 7:28 PM, David Edmundson da...@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? David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel On Kubuntu, you probably want to enable KDE_INSTALL_USE_QT_SYS_PATHS cmake option. but that will install to /usr Aleix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On Mon, May 18, 2015 at 7:28 PM, David Edmundson da...@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? David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel On Kubuntu, you probably want to enable KDE_INSTALL_USE_QT_SYS_PATHS cmake option. Aleix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On Mon, May 18, 2015 at 8:07 PM, David Edmundson da...@davidedmundson.co.uk wrote: On Mon, May 18, 2015 at 7:05 PM, Aleix Pol aleix...@kde.org wrote: On Mon, May 18, 2015 at 7:28 PM, David Edmundson da...@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? David ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel On Kubuntu, you probably want to enable KDE_INSTALL_USE_QT_SYS_PATHS cmake option. but that will install to /usr Aleix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel That's the downside, yes. Aleix ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On 18 May 2015 at 22:58, David Edmundson da...@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) ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
To me the XDG_DATA_DIRS path looks right..
[friedreb@pollux kde]$ awk -v 'RS=\0' -F= '$1==XDG_DATA_DIRS {print $2}'
/proc/3183/environ
/products/kde/install/share:/usr/share
[friedreb@pollux kde]$ ls -la /products/kde/install/share/ | wc -l
73
[friedreb@pollux kde]$ ls -la /products/kde/install/share/ | head -n 5
insgesamt 0
drwxrwxr-x. 1 friedreb friedreb 1282 30. Mär 20:51 .
drwxrwxr-x. 1 friedreb friedreb66 30. Mär 17:20 ..
drwxrwxr-x. 1 friedreb friedreb 1208 30. Mär 20:51 applications
drwxrwxr-x. 1 friedreb friedreb24 29. Mär 22:43 apps
Any other ideas?
Thanks
Bernhard
2015-03-30 22:22 GMT+02:00 David Edmundson da...@davidedmundson.co.uk:
Any ideas? (attached the output/bt I got from gdb)
it's an assert in could not find any theme
At a guess you XDG_DATA_DIRS are wrong.
cat /proc/PIDOFPLASMASHELL/env will tell you the most
Thanks :)
Bye,
Bernhard Friedreich
2015-03-28 19:23 GMT+01:00 Siddhartha sh.siddhar...@gmail.com:
Hi David,
Thanks a lot for your comments!
On 28 March 2015 at 20:23, David Edmundson da...@davidedmundson.co.uk
wrote:
I don't think we should tell people to download's David Faure's
kdesrc-buildrc file. It has /d hardcoded a lot.
If we make our own we don't need people to change it and can have the
same
directories you use for the rest of this.
Good point. I took this section from Frameworks/Building, didn't think
too much :P
Maybe we should update that page too?
That's installing to /opt/kde5 but we need to create those directories
first
(as root and change permissions)
Instructions already present :)
If this is about plasma change:
include extragear/utils/kdesrc-build/kf5-qt5-build-include
to
include extragear/utils/kdesrc-build/kf5-frameworks-build-include
include extragear/utils/kdesrc-build/kf5-workspace-build-include
this way you won't build apps and pim
Cool. Changed the whole section.
export XDG_CACHE_HOME=/home/user/.kde5/cache
only works if you happen to be called user.
I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever
Ah right, fixed.
Personally I wouldn't change the paths, you lose your firefox
settings, and
with the .xinitrc hack later you're only going to be loading this
session
from now on anyway.
Hmm. I preferred having clean Plasma 5 config paths. These lines are
now commented out by default.
The setup is a bit broken, if you do the login manager way.
yet if you log into your distro session and then start anything dbus
activated it will load from /opt/kde/install which is at best a bit
weird.
Ah right. But logging in to a Plasma 4 seemed to work fine. Ideally
one should remove the dbus config before starting the distro session,
yes.
you need to say login manager way and the .xinit way are mutually
exclusive
(well you can do both, but it'd be weird)
Done.
add a line saying to log out and back in.
Done
Cheers!
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
I finally found the problem - the instructions on the wiki were updated
since my setup and I was lacking some lib64 directories in the
runPlasma5.sh script..
Thanks for the documentation and your help! :)
2015-03-31 20:44 GMT+02:00 Bernhard Friedreich fries...@gmail.com:
To me the XDG_DATA_DIRS path looks right..
[friedreb@pollux kde]$ awk -v 'RS=\0' -F= '$1==XDG_DATA_DIRS {print
$2}' /proc/3183/environ
/products/kde/install/share:/usr/share
[friedreb@pollux kde]$ ls -la /products/kde/install/share/ | wc -l
73
[friedreb@pollux kde]$ ls -la /products/kde/install/share/ | head -n 5
insgesamt 0
drwxrwxr-x. 1 friedreb friedreb 1282 30. Mär 20:51 .
drwxrwxr-x. 1 friedreb friedreb66 30. Mär 17:20 ..
drwxrwxr-x. 1 friedreb friedreb 1208 30. Mär 20:51 applications
drwxrwxr-x. 1 friedreb friedreb24 29. Mär 22:43 apps
Any other ideas?
Thanks
Bernhard
2015-03-30 22:22 GMT+02:00 David Edmundson da...@davidedmundson.co.uk:
Any ideas? (attached the output/bt I got from gdb)
it's an assert in could not find any theme
At a guess you XDG_DATA_DIRS are wrong.
cat /proc/PIDOFPLASMASHELL/env will tell you the most
Thanks :)
Bye,
Bernhard Friedreich
2015-03-28 19:23 GMT+01:00 Siddhartha sh.siddhar...@gmail.com:
Hi David,
Thanks a lot for your comments!
On 28 March 2015 at 20:23, David Edmundson da...@davidedmundson.co.uk
wrote:
I don't think we should tell people to download's David Faure's
kdesrc-buildrc file. It has /d hardcoded a lot.
If we make our own we don't need people to change it and can have the
same
directories you use for the rest of this.
Good point. I took this section from Frameworks/Building, didn't think
too much :P
Maybe we should update that page too?
That's installing to /opt/kde5 but we need to create those
directories first
(as root and change permissions)
Instructions already present :)
If this is about plasma change:
include extragear/utils/kdesrc-build/kf5-qt5-build-include
to
include extragear/utils/kdesrc-build/kf5-frameworks-build-include
include extragear/utils/kdesrc-build/kf5-workspace-build-include
this way you won't build apps and pim
Cool. Changed the whole section.
export XDG_CACHE_HOME=/home/user/.kde5/cache
only works if you happen to be called user.
I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever
Ah right, fixed.
Personally I wouldn't change the paths, you lose your firefox
settings, and
with the .xinitrc hack later you're only going to be loading this
session
from now on anyway.
Hmm. I preferred having clean Plasma 5 config paths. These lines are
now commented out by default.
The setup is a bit broken, if you do the login manager way.
yet if you log into your distro session and then start anything dbus
activated it will load from /opt/kde/install which is at best a bit
weird.
Ah right. But logging in to a Plasma 4 seemed to work fine. Ideally
one should remove the dbus config before starting the distro session,
yes.
you need to say login manager way and the .xinit way are mutually
exclusive
(well you can do both, but it'd be weird)
Done.
add a line saying to log out and back in.
Done
Cheers!
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
___
Plasma-devel mailing list
Plasma-devel@kde.org
https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
On 1 April 2015 at 00:58, Bernhard Friedreich fries...@gmail.com wrote: I finally found the problem - the instructions on the wiki were updated since my setup and I was lacking some lib64 directories in the runPlasma5.sh script.. Ah yes, sorry about that. I have some additional config which installs all library files to the lib folder only. It was only later that I remembered the runPlasma5 script will need additional paths for lib64. Thanks for the documentation and your help! :) Have fun with Plasma 5 :) Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
Good stuff! Here are my comments: sudo chown -R user:group /opt/kde I think this should either use $USER or `whoami` rather than user ? Uncomment the last two lines if you also want to build the Applications and PIM suite. This should probably be inside the kdesrc-buildrc itself. Maybe it could also have a comment inside about the make-options -j4 needing adjusting and possibly should be mentioned outside too. There's also the ignore-kde-structure option, should this perhaps be set to true by default? I honestly see a little point having that structure mirrored on your disk, it's just confusing and takes time to find anything. Should that be the default, then I'd also suggest to skip the mkdir -p extragear/utils in the first steps and just clone directly to the sources dir. It's also a bit cumbersome having to go to /opt/kde/sources/extragear/utils/kdesrc-build each time you want to rebuild things (yeah tab helps but it's still annoying). Maybe the kdesrc-build could/should be linked to /opt/kde/install/bin (which is added to $PATH)? Then the kdesrc-buildrc would have to be in ~/.kdesrc-buildrc I think. Overall I feel the kdesrc-buildrc could be a bit better documented. #install-session-driver true This should be removed altogether or documented why is it there. export QTDIR=/usr/lib/qt As the kdesrc-buildrc mentions that the path should be changed if custom qt is being build, probably it could use a comment here as well (Running Plasma section). You may try going back to a previous code version (git skills required), or wait sometime for the developers to fix the code. ...or try helping with fixing it? ;) Otherwise, thanks for doing that! It rocks. Cheers -- Martin Klapetek | KDE Developer ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
Any ideas? (attached the output/bt I got from gdb) it's an assert in could not find any theme At a guess you XDG_DATA_DIRS are wrong. cat /proc/PIDOFPLASMASHELL/env will tell you the most Thanks :) Bye, Bernhard Friedreich 2015-03-28 19:23 GMT+01:00 Siddhartha sh.siddhar...@gmail.com: Hi David, Thanks a lot for your comments! On 28 March 2015 at 20:23, David Edmundson da...@davidedmundson.co.uk wrote: I don't think we should tell people to download's David Faure's kdesrc-buildrc file. It has /d hardcoded a lot. If we make our own we don't need people to change it and can have the same directories you use for the rest of this. Good point. I took this section from Frameworks/Building, didn't think too much :P Maybe we should update that page too? That's installing to /opt/kde5 but we need to create those directories first (as root and change permissions) Instructions already present :) If this is about plasma change: include extragear/utils/kdesrc-build/kf5-qt5-build-include to include extragear/utils/kdesrc-build/kf5-frameworks-build-include include extragear/utils/kdesrc-build/kf5-workspace-build-include this way you won't build apps and pim Cool. Changed the whole section. export XDG_CACHE_HOME=/home/user/.kde5/cache only works if you happen to be called user. I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever Ah right, fixed. Personally I wouldn't change the paths, you lose your firefox settings, and with the .xinitrc hack later you're only going to be loading this session from now on anyway. Hmm. I preferred having clean Plasma 5 config paths. These lines are now commented out by default. The setup is a bit broken, if you do the login manager way. yet if you log into your distro session and then start anything dbus activated it will load from /opt/kde/install which is at best a bit weird. Ah right. But logging in to a Plasma 4 seemed to work fine. Ideally one should remove the dbus config before starting the distro session, yes. you need to say login manager way and the .xinit way are mutually exclusive (well you can do both, but it'd be weird) Done. add a line saying to log out and back in. Done Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
Hi, At first: thanks for the guide :) It's a nice addition to https://community.kde.org/Frameworks/Building I've got the following problems: 1.) on my fedora 23 (rawhide) I had to set selinux to permissive mode for the custom dbus files to be read (otherwise it wouldn't let dbus access them, maybe it is because I changed paths from /opt to /products?) (yeah I know decreasing selinux security isn't a solution) 2.) I can start the session from sddm but plasmashell and krunner crash instantly.. Any ideas? (attached the output/bt I got from gdb) Thanks :) Bye, Bernhard Friedreich 2015-03-28 19:23 GMT+01:00 Siddhartha sh.siddhar...@gmail.com: Hi David, Thanks a lot for your comments! On 28 March 2015 at 20:23, David Edmundson da...@davidedmundson.co.uk wrote: I don't think we should tell people to download's David Faure's kdesrc-buildrc file. It has /d hardcoded a lot. If we make our own we don't need people to change it and can have the same directories you use for the rest of this. Good point. I took this section from Frameworks/Building, didn't think too much :P Maybe we should update that page too? That's installing to /opt/kde5 but we need to create those directories first (as root and change permissions) Instructions already present :) If this is about plasma change: include extragear/utils/kdesrc-build/kf5-qt5-build-include to include extragear/utils/kdesrc-build/kf5-frameworks-build-include include extragear/utils/kdesrc-build/kf5-workspace-build-include this way you won't build apps and pim Cool. Changed the whole section. export XDG_CACHE_HOME=/home/user/.kde5/cache only works if you happen to be called user. I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever Ah right, fixed. Personally I wouldn't change the paths, you lose your firefox settings, and with the .xinitrc hack later you're only going to be loading this session from now on anyway. Hmm. I preferred having clean Plasma 5 config paths. These lines are now commented out by default. The setup is a bit broken, if you do the login manager way. yet if you log into your distro session and then start anything dbus activated it will load from /opt/kde/install which is at best a bit weird. Ah right. But logging in to a Plasma 4 seemed to work fine. Ideally one should remove the dbus config before starting the distro session, yes. you need to say login manager way and the .xinit way are mutually exclusive (well you can do both, but it'd be weird) Done. add a line saying to log out and back in. Done Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel (gdb) bt #0 0x76674520 in QQmlComponent::status() const () at /lib64/libQt5Qml.so.5 #1 0x7723f832 in KDeclarative::QmlObject::completeInitialization(QHashQString, QVariant const) (this=0xba4640, initialProperties=...) at /products/kde/sources/frameworks/kdeclarative/src/kdeclarative/qmlobject.cpp:264 #2 0x0040cfc5 in View::View(QWindow*) (this=0x7fffde50) at /products/kde/sources/kde/workspace/plasma-workspace/krunner/view.cpp:93 #3 0x0040bb58 in main(int, char**) (argc=1, argv=0x7fffe0c8) at /products/kde/sources/kde/workspace/plasma-workspace/krunner/main.cpp:66 Starting program: /products/kde/install/bin/plasmashell [Thread debugging using libthread_db enabled] Using host libthread_db library /lib64/libthread_db.so.1. kf5.kiconthemes: Theme tree: (Breeze) kf5.kservice.sycoca: Trying to open ksycoca from /home/friedreb/.cache/ksycoca5 populateAddPanelsMenu 1 Failed to load the OSD script file from [New Thread 0x7fffd26bf700 (LWP 2216)] has no desktop group, cannot construct a KPluginInfo object from it. Detaching after fork from child process 2218. kscreen: launcherDataAvailable: org.kde.KScreen.Backend.XRandR kscreen: Launcher finished with exit code 1 , status 0 kscreen: Service for requested backend already running kscreen: Primary output changed from KScreen::Output(Id: 118 , Name: LVDS1 ) ( LVDS1 ) to KScreen::Output(Id: 118 , Name: LVDS1 ) ( LVDS1 ) Error loading plugin plasma_applet_timer Die dynamische Bibliothek konnte nicht gefunden werden. Plugin search paths are (/usr/lib64/qt5/plugins, /products/kde/install/bin) The environment variable QT_PLUGIN_PATH might be not correctly set unversioned plugin detected, may result in instability Error loading plugin plasma_applet_timer Die dynamische Bibliothek konnte nicht gefunden werden. Plugin search paths are (/usr/lib64/qt5/plugins, /products/kde/install/bin) The environment variable QT_PLUGIN_PATH might be not correctly set Could not load applet org.kde.plasma.timer ! reason given: Die dynamische Bibliothek konnte nicht gefunden werden. Falling back to an empty one Constructing a KPluginInfo object from old style JSON. Please use
Re: Plasma 5 is awesome...and some help required with build instructions
Hey Martin, Thanks for all the comments :) On 30 March 2015 at 16:11, Martin Klapetek martin.klape...@gmail.com wrote: sudo chown -R user:group /opt/kde I think this should either use $USER or `whoami` rather than user ? Hmm good point. Also I learned that leaving the group empty after a colon automatically sets it to the primary user group. Nice! Uncomment the last two lines if you also want to build the Applications and PIM suite. This should probably be inside the kdesrc-buildrc itself. Maybe it could also have a comment inside about the make-options -j4 needing adjusting and possibly should be mentioned outside too. Done. There's also the ignore-kde-structure option, should this perhaps be set to true by default? I honestly see a little point having that structure mirrored on your disk, it's just confusing and takes time to find anything. I'm a bit torn over this. While you make a good usability point, having the kde structure groups and separates the modules, thus feels 'cleaner' as compared to everything in a single folder. However, navigating the whole structure for eg. to import a module into kdevelop is truly time taking. Enabling it in my local config and here too :) Should that be the default, then I'd also suggest to skip the mkdir -p extragear/utils in the first steps and just clone directly to the sources dir. It's also a bit cumbersome having to go to /opt/kde/sources/extragear/utils/kdesrc-build each time you want to rebuild things (yeah tab helps but it's still annoying). Done Maybe the kdesrc-build could/should be linked to /opt/kde/install/bin (which is added to $PATH)? Then the kdesrc-buildrc would have to be in ~/.kdesrc-buildrc I think. Hmm. The default config also builds kdesrc-build, so its already in $PATH. But here we first update kdesrc-build git source and then use it. Bit better I feel. Anyways, changed the config path to ~/.kdesrc-buildrc, so either can be used. Overall I feel the kdesrc-buildrc could be a bit better documented. Now its a bit better documented. Please add anything else you feel missing :) #install-session-driver true This should be removed altogether or documented why is it there. I never used this. As we already have manual instructions, removing this. I'll test this sometime and add it back if successful. export QTDIR=/usr/lib/qt As the kdesrc-buildrc mentions that the path should be changed if custom qt is being build, probably it could use a comment here as well (Running Plasma section). Done You may try going back to a previous code version (git skills required), or wait sometime for the developers to fix the code. ...or try helping with fixing it? ;) Haha. Of course :) Otherwise, thanks for doing that! It rocks. Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Plasma 5 is awesome...and some help required with build instructions
Hi everyone, I shifted to Plasma 5 a while back. We all know how awesome it has become. :D One particular moment I want to share was discovering Require password after locking setting for Lock screen. I had been wishing for something like this to quickly recover from unwanted screen locking, and lo and behold, wish granted in Plasma 5. How cool is that! Finding features like this keeps me delighted :) Today I wrote down instructions for installing and running Plasma 5 from source here: https://community.kde.org/Plasma/Building. Please help in improving the page as required. Because this plasma installation is in a custom path, what additional steps need to be taken? For example, pressing PrntScrn gives me an error KDEInit could not launch '/opt/kde5/bin/ksnapshot', even though I can manually start it from Konsole. I'm guessing that is due to something not set in my environment correctly. Cheers, Siddhartha ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
Cool, definitely much needed .Thanks. Review comments -- I don't think we should tell people to download's David Faure's kdesrc-buildrc file. It has /d hardcoded a lot. If we make our own we don't need people to change it and can have the same directories you use for the rest of this. -- That's installing to /opt/kde5 but we need to create those directories first (as root and change permissions) -- If this is about plasma change: include extragear/utils/kdesrc-build/kf5-qt5-build-include to include extragear/utils/kdesrc-build/kf5-frameworks-build-include include extragear/utils/kdesrc-build/kf5-workspace-build-include this way you won't build apps and pim -- export XDG_CACHE_HOME=/home/user/.kde5/cache only works if you happen to be called user. I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever Personally I wouldn't change the paths, you lose your firefox settings, and with the .xinitrc hack later you're only going to be loading this session from now on anyway. -- The setup is a bit broken, if you do the login manager way. yet if you log into your distro session and then start anything dbus activated it will load from /opt/kde/install which is at best a bit weird. -- you need to say login manager way and the .xinit way are mutually exclusive (well you can do both, but it'd be weird) -- add a line saying to log out and back in. ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
Re: Plasma 5 is awesome...and some help required with build instructions
Hi David, Thanks a lot for your comments! On 28 March 2015 at 20:23, David Edmundson da...@davidedmundson.co.uk wrote: I don't think we should tell people to download's David Faure's kdesrc-buildrc file. It has /d hardcoded a lot. If we make our own we don't need people to change it and can have the same directories you use for the rest of this. Good point. I took this section from Frameworks/Building, didn't think too much :P Maybe we should update that page too? That's installing to /opt/kde5 but we need to create those directories first (as root and change permissions) Instructions already present :) If this is about plasma change: include extragear/utils/kdesrc-build/kf5-qt5-build-include to include extragear/utils/kdesrc-build/kf5-frameworks-build-include include extragear/utils/kdesrc-build/kf5-workspace-build-include this way you won't build apps and pim Cool. Changed the whole section. export XDG_CACHE_HOME=/home/user/.kde5/cache only works if you happen to be called user. I'm pretty sure you can do export XDG_CACHE_HOME=$HOME/.whatever Ah right, fixed. Personally I wouldn't change the paths, you lose your firefox settings, and with the .xinitrc hack later you're only going to be loading this session from now on anyway. Hmm. I preferred having clean Plasma 5 config paths. These lines are now commented out by default. The setup is a bit broken, if you do the login manager way. yet if you log into your distro session and then start anything dbus activated it will load from /opt/kde/install which is at best a bit weird. Ah right. But logging in to a Plasma 4 seemed to work fine. Ideally one should remove the dbus config before starting the distro session, yes. you need to say login manager way and the .xinit way are mutually exclusive (well you can do both, but it'd be weird) Done. add a line saying to log out and back in. Done Cheers! ___ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
