Fernando de Oliveira wrote:
Em 10-11-2015 14:39, Bruce Dubbs escreveu:
[email protected] wrote:


2. My build environment: chroot under Ubuntu LXQT target path:
/opt/lxqt KF5 path: /opt/kf5

In order to build LXQT, I have to add "-DCMAKE_PREFIX_PATH=$KF5_PREFIX"
option otherwise cmake cannot find any KF5 components.

There probably needs to be some additional detail if
/etc/profile.d/kf5.sh is not installed.  I have not yet built lxqt.

3. Add more information about "how to build the required KF5 components
and dependencies" such as KWindowSystem. That's because some KF5
required dependencies is not needed if we only build LXQT. For example,
I did not build Boost and Phonon in my system.

Think I understand, now.

In order to build any needed KF5 you only need that particular
application ans dependencies.

But: you need to do the same thing as if building all KF5 and first, do
what is in "KDE Frameworks 5 Pre-installation Configuration":


http://www.linuxfromscratch.org/blfs/view/svn/kde/kf5-intro.html

hykwok1: did you that? And then, "source profile", before start buildng:

Bruce or Ken: Should these instructions be linked to LXQt? Where would
be the best place: in the pages with KF5 dependencies, in the note about
"just the named package needs to be installed, or in the Pre-Install
instructions?

We could add separate sections for KWindowSystem, kguiaddons, and solid.

Dependencies for KWindowSystem is as I mentioned before.

kguiaddons:
solid:  cmake, Qt5, and cmake-extras

libkscreen: cmake, Qt5, cmake-extras, and xcb-utils

As far as instruction about paths go, I think either setting -DCMAKE_PREFIX_PATH=$KF5_PREFIX in the cmake options or setting paths in the lxqt pre-install instructions would be appropriate.

I'll note that if I was going to install lxqt without kf5 or plasma, I would probably install KWindowSystem, kguiaddons, solid, and libkscreen in the lxqt hierarchy.

  -- Bruce


  -- Bruce


--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to