Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-11 Thread Fernando de Oliveira 
Em 11-11-2015 02:34, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
>> Em 10-11-2015 18:17, Bruce Dubbs escreveu:
>>> Fernando de Oliveira wrote:
>>>
 My preference is linking, not adding this extra line to the packages
 cmake switches.

 Reason: eventually a developer or user will build KF5 and Plasma in the
 same system.
>>>
>>> OK, go ahead and do what you think best.  I was just offering possible
>>> alternatives.
>>
>> Sorry, I forgot to thank you for replying.
>>
>> I liked your idea.
>>
>> I was not closing the discussion. If you really think that it is best to
>> separate the KF5 and Plasma pages and include the build in the LXQt
>> category, I am ready to gratefully accept.
> 
> I'll look at it tomorrow.  There are only four packages AFAIK right now
> that are needed.  If they are the only ones, it might be better to put
> them in /usr/lib instead of /opt/kf5.  However I can't decide until I
> look at the packages in a little more detail.

That is a good idea. Thanks.


-- 
[]s,
Fernando, aka Sísifo
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-11 Thread Bruce Dubbs 

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:

hykw...@sina.com 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
cdbuild

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

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Bruce Dubbs 

hykw...@sina.com wrote:

1. libxkbcommon (required by lxqt-panel) "--disable-static" option can
be removed because this option is included in the XORG_CONFIG variable.
(refer to "Introduction to Xorg-7.7" section)


Right.  I'll fix that.


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.


KWindowSystem has:

-- The following OPTIONAL packages have been found:

 * X11
 * PkgConfig
 * XCB , X protocol C-language Binding , 

-- The following REQUIRED packages have been found:

 * ECM (required version >= 5.15.0) , Extra CMake Modules.
 * Qt5Core (required version >= 5.5.1)
 * Qt5Gui (required version >= 5.5.1)
 * Qt5Widgets
 * Qt5X11Extras
 * Qt5LinguistTools
 * Qt5Test
 * Qt5 (required version >= 5.3.0)

So it appears that the only package really needed is extra-cmake-modules 
if only KWindowSystem is built.  Technically xcb comes after xorg-libs, 
but I don't imagine that anyone builds only part of Xorg other than 
omitting some apps or fonts.


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

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Fernando de Oliveira 
Em 10-11-2015 17:44, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
>> Em 10-11-2015 14:39, Bruce Dubbs escreveu:
>>> hykw...@sina.com 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.
> 

My preference is linking, not adding this extra line to the packages
cmake switches.

Reason: eventually a developer or user will build KF5 and Plasma in the
same system.

-- 
[]s,
Fernando, aka Sísifo
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Fernando de Oliveira 
Em 10-11-2015 14:39, Bruce Dubbs escreveu:
> hykw...@sina.com 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?


-- 
[]s,
Fernando, aka Sísifo
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Bruce Dubbs 

Fernando de Oliveira wrote:


My preference is linking, not adding this extra line to the packages
cmake switches.

Reason: eventually a developer or user will build KF5 and Plasma in the
same system.


OK, go ahead and do what you think best.  I was just offering possible 
alternatives.


  -- Bruce



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

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Fernando de Oliveira 
Em 10-11-2015 18:17, Bruce Dubbs escreveu:
> Fernando de Oliveira wrote:
> 
>> My preference is linking, not adding this extra line to the packages
>> cmake switches.
>>
>> Reason: eventually a developer or user will build KF5 and Plasma in the
>> same system.
> 
> OK, go ahead and do what you think best.  I was just offering possible
> alternatives.

Sorry, I forgot to thank you for replying.

I liked your idea.

I was not closing the discussion. If you really think that it is best to
separate the KF5 and Plasma pages and include the build in the LXQt
category, I am ready to gratefully accept.

-- 
[]s,
Fernando, aka Sísifo
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

[blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread hykwok1 
1. 
libxkbcommon (required by lxqt-panel)
"--disable-static" option can be removed because this option is included in the 
XORG_CONFIG variable. (refer to "Introduction to Xorg-7.7" section)

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.

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.
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Re: [blfs-dev] Suggestion for LXQT 0.10.0 building

2015-11-10 Thread Bruce Dubbs 

Fernando de Oliveira wrote:

Em 10-11-2015 18:17, Bruce Dubbs escreveu:

Fernando de Oliveira wrote:


My preference is linking, not adding this extra line to the packages
cmake switches.

Reason: eventually a developer or user will build KF5 and Plasma in the
same system.


OK, go ahead and do what you think best.  I was just offering possible
alternatives.


Sorry, I forgot to thank you for replying.

I liked your idea.

I was not closing the discussion. If you really think that it is best to
separate the KF5 and Plasma pages and include the build in the LXQt
category, I am ready to gratefully accept.


I'll look at it tomorrow.  There are only four packages AFAIK right now 
that are needed.  If they are the only ones, it might be better to put 
them in /usr/lib instead of /opt/kf5.  However I can't decide until I look 
at the packages in a little more detail.


  -- Bruce

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