On Sun, Aug 16, 2015 at 01:35:55PM -0300, Fernando de Oliveira wrote:
> Em 16-08-2015 12:20, Ken Moffat escreveu:
> > On Sun, Aug 16, 2015 at 11:19:51AM -0300, Fernando de Oliveira wrote:
> >> Em 15-08-2015 20:40, Ken Moffat escreveu:
> >>
> >> From my searches
> >>
> >>> Perhaps I will try with qt in /opt...
>
> >> Yes, they are all in what seems non-default places. Thus, I have the
> >> impression that a qt5.sh is always necessary. And it was from there that
> >> I got idea of just using the /opt instructions to build at /usr/qt5 (not
> >> sure if this is exactly what I was proposing), instead of what is in the
> >> book, and change correspondingly the qt5.sh and other instructions, if any.
> >>
> > I can't comment on that unless / until I manage to actually build
> > something ;-)
> >
> > I gave it another go overnight, again using /usr but without
> > qtchooser and without the addition of -qt5 to program names (no qt4
> > in that system). Did not help, I will have to try /opt again.
> >
> > Meanwhile, from qt5 I acquired /usr/doc /usr/imports /usr/locale
> > /usr/mkspecs /usr/phrasebooks /usr/plugins /usr/qml and
> > /usr/translations.
>
> Yes. One of the things I dislike in the current /usr "instructions".
>
Agreed.
By going back to /opt/qt5 I've now managed to build
kwindowsystem-5.12.0 and kguiaddons-5.12.0, I'm currently building
lxqt-panel.
After my experience with qupzilla the other night, I won't claim
that things are now ok until I manage to install qupzilla, but it
certainly looks hopeful.
> >> I've searched in other Ubuntu, and what they do seems different from
> >> Arch-Linux. I needed to install:
> >>
> >> qt5-qmake
> >> qt4-qmake
> >> qt4-dev-tools
> >> qttools5-dev-tools
>
> > How do they make the programs (e.g. qmake) available ? Are they
> > using qtchooser and adding -qt4 -qt5 to the program names ?
>
> I can't answer exactly. Don't want to screw up, using qtchooser to
> change to qt5 as default, never used qtchooser. Believe that qtchooser
> not only chooses, but also creates links and delete the unwanted ones.
>
> {{{
> $ find /usr/ -name assistant-\* -o -name assistant | xargs ls -l \
> | cut -d/ -f2- | sed 's:^:/:' | grep -vE 'include|share'
> /usr/bin/assistant -> qtchooser
> /usr/bin/assistant-qt4 -> ../lib/i386-linux-gnu/qt4/bin/assistant
> /usr/lib/i386-linux-gnu/qt4/bin/assistant
> /usr/lib/i386-linux-gnu/qt5/bin/assistant
>
> $ find /usr/ -name qmake-\* -o -name qmake | xargs ls -l \
> | cut -d/ -f2- | sed 's:^:/:'
> /usr/bin/qmake -> qtchooser
> /usr/bin/qmake-qt4 -> ../lib/i386-linux-gnu/qt4/bin/qmake
> /usr/lib/i386-linux-gnu/qt4/bin/qmake
> /usr/lib/i386-linux-gnu/qt5/bin/qmake
> /usr/share/man/man1/qmake-qt4.1.gz
> /usr/share/man/man1/qmake-qt5.1.gz
> /usr/share/qt4/bin/qmake -> ../../../lib/i386-linux-gnu/qt4/bin/qmake
> }}}
>
Since we dropped qtchooser ages ago, I had to look it up in the
systemd book. From memory, the -qt4 and -qt5 links were created
after installing each version. It is then possible to specify one
as the default by symlinking the required conf file to default.conf.
I took the view that it was more appropriate to export QT_SELECT
(with values of qt4 or qt5) in my "driver" scripts (the ones which
build hte individual packages).
Hmm, I wonder if that might be why I could never use kde from sddm ?
Will need to try re-testing later.
> >>
> >> We could just replace the /usr instructions and tell that the
> >> alternative would be to install in /usr/lib/qt{4,5} and, again, show how
> >> to change the corresponding qt5.sh and other instructions, if any.
> >>
I don't use any of the book's scripts for setting PATHs, so I can't
comment on that.
For me, at the moment my normal scripts only build two qt packages:
vlc (needs qt4 for the desktop part) and qupzilla (currently works
with qt5 on those occasions I have managed to install it, but
QtWebKit is going to go sooner or later). I would very much like to
try using sddm, and kde5 (the purely qt5 parts) is something I might
partially use - apart from some instability in the unreleased
packages such as dragon, it's not much worse than kde4.
For kde4, I only see myself building any of it in two circumstances:
to test the book (perhaps), and if I manage to get my low-end AMD
box running again. So, for the moment I think I will keep qt4 in
/usr, but without the -qt4 symlinks and qtchooser.
I haven't got there yet, so this is still tentative.
> >
> > I'm starting to think that I must have changed something else in my
> > scripts which has somehow caused my problem. Will know for certain
> > after I change the scripts to use /opt/qt5. Unfortunately there
> > have been a lot of changes since then (my lxqt script originally did
> > not build qt5 because it was already installed) so I cannot just
> > revert one or two commits.
But contrary to all sane principles, it does appear that Qt-5.5
needs some extra secret-sauce to be able to work in /usr.
ĸen
--
This one goes up to eleven: but only on a clear day, with the wind in
the right direction.
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
