Skip to content

Update qt5 5.15.2 to 5.15.5 incl support #2716

Merged
merged 7 commits into from
Jul 25, 2022

Conversation

thomas
Copy link
Collaborator

@thomas thomas commented Jul 21, 2022

Most notably:

  • Qt5 source is taken from the KDE repo => patches included.
  • Three compat libs are the remains of Qt4. Thanks, and good bye.

Test/install HowTo:

bee update qt5
bee update qwt
bee update QScintilla
bee install QScintilla_designer_plugin
bee remove qt4-4.7.4-0.x86_64
bee install qt4_compat-4.7.4-0
bee remove qtlinks-1.0.1-5.x86_64
bee install qtlinks-1.0.2-0```

This saves some patches, since they are already included.

Preparing the source tree is described here:

  https://wiki.qt.io/Building_Qt_5_from_Git

The helper script is located at:

 /project/admin/tools/qt_source_preparation
Also account for the changed location of the plugins
directory, which is under lib.
Rationale: building the plugin requires QScintilla to
be installed.
QT4 is supposed to be history. Well, very old packages might
need help from .compatlibs, but that is how the cookie crumbles :)

The only dependencies in the system belong to /usr/lib/liblastfm.so.1
and /usr/lib/libpoppler-qt4.so.4.0.0. Better make this a task on
its own to check if they are needed.
Note, bee throws a warning ...

 WARNING: system and image files named '/usr/local/lib/plugins' differ
          image : directory
          system: symbolic link to /usr/local/qt5/lib/plugins

What is correct, so instead of update it is:

 #> bee remove qtlinks-1.0.1-5.x86_64
 #> bee install qtlinks-1.0.2
mee_configure() {
MAKEFLAGS=${BEE_MAKEFLAGS} \
start_cmd ${S}/configure \
${S}/configure \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I’d keep the start_cmd to be in line with bee_configure() and friends.

-prefix ${PREFIX} \
-bindir ${BINDIR} \
-libdir ${LIBDIR} \
-plugindir ${LIBDIR}/plugins \
-headerdir ${INCLUDEDIR} \
-sysconfdir ${SYSCONFDIR} \
-nomake examples \
-opensource \
-confirm-license \
-nomake tests \
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do they fail to be disabled, or were they never used/run in the first place?

@thomas
Copy link
Collaborator Author

thomas commented Jul 22, 2022

As for the comment on start_cmd -- I hardly see any point inhere (better continue it here: mariux64/bee#54)

'nomake tests' -- why build something that isn't used?

@thomas
Copy link
Collaborator Author

thomas commented Jul 22, 2022

I will merge the updated Qt on Monday, accounting for the small risk that the Qt4 removal may yield trouble.

@thomas thomas merged commit 93e77cf into master Jul 25, 2022
@donald donald mentioned this pull request Sep 20, 2022
Sign in to join this conversation on GitHub.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants