The keypoints of the build:
- upstream Qt-5.9.6
- Q_OS_SAILFISH platform [1]
- Sailfish Theme added as a plugin instead of direct
QGenericUnixTheme patching [2]
- _qt5_version re-defined in the OBS project config [3] (default value
defined in qt5 macros).
- qt5 macros [4] extended and moved to own repository [5]. The added
macros fix installations conflicts, improve compatibility with fedora
specs and let us flexibly define Qt installation layout from the
outside of qtbase.
- qtchooser-config is built as a part of qtbase.
[1]
https://git.merproject.org/Kaffeine/qtbase/commit/7b8850fc9df17384a8cf53dc8b1d1e435e806794
[2]
https://git.merproject.org/Kaffeine/qtbase/commit/816d9f7fe4fac0208d672086ae910cae772dcd32
[3] https://build.merproject.org/project/prjconf/home:Kaffeine:qt:prefix:5.9
[4]
https://git.merproject.org/mer-core/qtbase/blob/mer-5.6/rpm/macros.qt5-default
[5] https://git.merproject.org/Kaffeine/qt5-rpm-macros/blob/master/macros.qt5
Just try quickcontrols2/gallery and you'll see what's the problem
(maliit keyboard doesn't show up and the window doesn't appear in
lipstick home screen).
On Sun, Feb 10, 2019 at 1:07 PM rinigus <rinigus....@gmail.com> wrote:
>
> Nice work,
>
> so, there is already something similar done. Can't find where do you define
> _qt_prefix for your SPEC
> (https://git.merproject.org/Kaffeine/qtbase/blob/sailfish-platform-5.9/rpm/qtbase.spec).
> There are also bunch of conflicts defined there, no idea whether they
> interfere.
>
> Which issues did you have with Wayland and keyboard (which of them, maliit or
> qtvirtualkeyboard?).
>
> @tortoisedoc: Sounds like this upgrade (5.6->5.9) is as much political as it
> is technical. As for 5.12, I don't know if there are some bugs there that
> have to be fixed. When using flatpak platform with 5.12, I have issues with
> QML Audio and some strange scaling of the map (latter could be also my bug in
> mapbox gl qml plugin). On 5.11, all performed as it was expected. So, either
> flatpak platform has still some issues at 5.12 or 5.12 itself has some bugs.
>
> To sum up, no idea how much we can help with 5.9 transition and what's
> holding it back specifically.
>
> Rinigus
>
> On Sun, Feb 10, 2019 at 11:17 AM Alexander Akulich
> <akulichalexan...@gmail.com> wrote:
>>
>> Hi,
>>
>> I experimented with a build in prefix in March 2018. I changed MER Qt
>> build configuration to make it trivial to install an arbitrary number
>> of versions simultaneously. I'll make PRs on git.merproject.org once
>> Qt-5.9 support will be merged to master.
>> There are two issues — wayland and virtual keyboard. I posted
>> instruction in Sailfish OS Fan Club group in Telegram, here it is:
>>
>> >// Qt 5.9 for Sailfish OS (installed to /usr/lib/qt5.9 simultaneously to
>> >the system Qt)
>> >// To install (root or privileged):
>> >ssu ar qt-prefix-5.9
>> >http://repo.merproject.org/obs/home:/Kaffeine:/qt:/prefix:/5.9/latest_armv7hl
>> >zypper ref qt-prefix-5.9
>> >zypper in qt5.9-qtquickcontrols2-examples qt5.9-qtwayland
>> >
>> >// To remove (root or privileged):
>> >zypper rm qt5.9*
>> >
>> >// To try out (nemo):
>> >QT_SCALE_FACTOR=2 LD_LIBRARY_PATH=/usr/lib/qt5.9/lib
>> >/usr/lib/qt5.9/examples/quickcontrols2/gallery/gallery
>> >
>> >This is a very first success build, please do not expect much :).
>> >
>> >P.S.: Select Material style in the settings at the right top corner to make
>> >the demo a bit nicer.
>>
>> I also mostly built Qt-5.11, but it is not an LTS and IMO not as big
>> step forward as 5.9, so I didn't evolve it.
>>
>> On Sat, Feb 9, 2019 at 8:44 PM rinigus <rinigus....@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > sounds like there are porting and licensing issues on the way of getting
>> > qt 5.9 for SFOS (see logs from the last #mer-meeting). Its all
>> > understandable, but it would be great to get a way forward. Not sure
>> > whether it has been considered by others and I wonder whether we can make
>> > a separate Qt 5.12 packages for /opt/qt512?
>> >
>> > From a quick test, it is possible to run non-silica applications as well
>> > (tested with qmlscene and QML with plain Window). In that test, even
>> > keyboard worked as expected. Look was non-native, but let it be for now.
>> >
>> > So, I wonder, whether its possible to get Qt 5.12 compiled with /opt/qt512
>> > prefix and then use it for development using the latest libs (new web
>> > browser?) and collaborate with other mobile Linux'es out there. As far as
>> > I remember, Wayland was rather old and, maybe, it will preclude Qt 5.12
>> > compilation. @mal, though, had a newer version around and it may serve a
>> > purpose for such project. Is there anything else that should be considered?
>> >
>> > Cheers,
>> >
>> > Rinigus
>> >
>> > PS: Please consider it as request-for-comment and not as any kind of
>> > statement nor call-for-action :)
>> > _______________________________________________
>> > SailfishOS.org Devel mailing list
>> > To unsubscribe, please send a mail to
>> > devel-unsubscr...@lists.sailfishos.org
>> _______________________________________________
>> SailfishOS.org Devel mailing list
>> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
>
> _______________________________________________
> SailfishOS.org Devel mailing list
> To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
_______________________________________________
SailfishOS.org Devel mailing list
To unsubscribe, please send a mail to devel-unsubscr...@lists.sailfishos.org
