Fernando de Oliveira wrote:
Em 10-11-2015 17:44, Bruce Dubbs escreveu:
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.
Problem is that each release includes new KF5 and/or Plasma5 packages.
This time: solid (KF5) and libkscreen (Plasma5)
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.
OK, these work out OK. I first renamed /opt/kf5 to /opt/kf5-save to make
sure what I already have didn't interfere. Then I built KWindowSystem,
kguiaddons, solid with:
mkdir build
cd build
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_PREFIX_PATH=$QT5DIR \
-DCMAKE_BUILD_TYPE=Release \
-DLIB_INSTALL_DIR=lib \
-DBUILD_TESTING=OFF \
-Wno-dev ..
make
make DESTDIR=/tmp/filename install
and built libkscreen the same way but using:
cmake -DCMAKE_INSTALL_PREFIX=/usr \
-DCMAKE_BUILD_TYPE=Release \
-DLIB_INSTALL_DIR=lib \
-DBUILD_TESTING=OFF \
-Wno-dev ..
All built fine. They do need extra-cmake-modules but we install that in /usr.
Looking at what is installed, they all create libraries, but also add
headers, .cmake files, plugins, and other data files. I think I would
recommend that we still install them in /opt/kf5 because we don't want to
create an inconsistent environment if a user decides to go back later and
install kf5 or plasma.
That would result in adding 4 pages (3 kf5 and 1 plasma) with an
explanation that why they are created separately (not needed if the
scripted install is done).
Do you want me to do that?
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
