Bug 345321 - Build errors on Mac OS X: Missing required packages in CMakeLists.txt
Summary: Build errors on Mac OS X: Missing required packages in CMakeLists.txt
Status: REPORTED
Alias: None
Product: marble
Classification: Applications
Component: general (show other bugs)
Version: 1.8 (KDE 4.13)
Platform: Other Other
: NOR grave
Target Milestone: ---
Assignee: marble-bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-19 00:59 UTC by Jessica Leigh
Modified: 2021-03-09 22:51 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Jessica Leigh 2015-03-19 00:59:03 UTC 
When building with CMake 3.2.1, build fails with the following error:

/marble/download/path/marble/sources/src/lib/marble/AbstractDataPlugin.cpp:36:12: fatal error: 'QQmlComponent' file not found
  #include <QQmlComponent>
           ^
1 error generated.

Dependencies on QtQml and QtQuick were apparently not being scanned by CMake. I added two lines to CMakeLists.txt (in the toplevel source directory) and resolved the issue:

  find_package(Qt5Quick REQUIRED)
  find_package(Qt5Qml REQUIRED)


Reproducible: Always

Steps to Reproduce:
1. Download latest 4.13 Marble sources
2. Run cmake in a build directory: cmake -DCMAKE_BUILD_TYPE=release -DQTONLY=ON -DCMAKE_INSTALL_PREFIX=/Applications/ ../sources
3. Run make

Actual Results:  
Compilation halts with an error when it gets to AbstractDataPlugin.cpp

Expected Results:  
Compilation should have completed
Comment 1 hardik beladiya 2015-03-19 12:33:40 UTC 
you should install qt5qml -dev package
Comment 2 Jessica Leigh 2015-03-19 20:49:21 UTC 
(In reply to hardik beladiya from comment #1)
> you should install qt5qml -dev package

I'm not sure what this package is (it sounds like a Debian package... I was referring to a problem building Marble on Mac OS X).
Comment 3 Justin Zobel 2021-03-09 22:51:28 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.