Bug 15125 - Missing dependency for lib64qt5declarative-devel
Summary: Missing dependency for lib64qt5declarative-devel
Status: RESOLVED WORKSFORME
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal minor
Target Milestone: ---
Assignee: Nicolas Lécureuil
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2015-01-24 10:47 CET by Johnny Accot
Modified: 2015-01-28 22:34 CET (History)
0 users

See Also:
Source RPM: qtquick5-5.4.0-1.mga5.src.rpm
CVE:
Status comment:


Attachments

Description Johnny Accot 2015-01-24 10:47:44 CET
Description of problem:

Compiling MuseScore with Qt5 support on an up-to-date cauldron system, I get the following error message:

---

CMake Error at /usr/lib64/cmake/Qt5Declarative/Qt5DeclarativeConfig.cmake:15 (message):
  The imported target "Qt5::Declarative" references the file

     "/usr/lib64/qt5/plugins/qml1tooling/libqmldbg_inspector.so"

  but this file does not exist.  Possible reasons include:

[...]

---

Qt5DeclarativeConfig.cmake belongs to lib64qt5declarative-devel and libqmldbg_inspector.so is provided by qtquick5-qmlviewer.  This problem could be fixed by adding qtquick5-qmlviewer as a required package for lib64qt5declarative-devel.

Qt5Declarative_QTcpServerConnection.cmake, which is also part of lib64qt5declarative-devel, also requires a plugin from qtquick5-qmlviewer.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. install qt5 devel packages, git, cmake, etc., and remove qtquick5-qmlviewer if it is installed
1. $ git clone https://github.com/musescore/MuseScore.git
2. $ cd MuseScore
3. $ make release

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2015-01-24 17:26:28 CET

Keywords: (none) => Triaged
Assignee: bugsquad => mageia

Comment 1 Johnny Accot 2015-01-28 11:19:26 CET
It's fixed.  Thank you!
Comment 2 Manuel Hiebel 2015-01-28 22:34:10 CET
closing then (you can also doing it yourself next time)

Status: NEW => RESOLVED
Resolution: (none) => WORKSFORME


Note You need to log in before you can comment on or make changes to this bug.