Bug 344725 - ktp-call-ui doesn't include phonon qt5 include dirs
Summary: ktp-call-ui doesn't include phonon qt5 include dirs
Status: REPORTED
Alias: None
Product: telepathy
Classification: Frameworks and Libraries
Component: call-ui (show other bugs)
Version: frameworks
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: Future
Assignee: Telepathy Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-02 00:05 UTC by kde
Modified: 2021-03-09 07:26 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2015-03-02 00:05:12 UTC
if qt4 based phonon is not installed, ktp-call-ui fails to build, because it can't find the phonon-qt5 headers, which are installed in /usr/include/phonon4qt5/

This is no problem, when phonon-qt4 is installed, because its headers are in /usr/include, hence in global search paths.

The Cmake files also should explicitly check for phonon-qt5 and include its include paths

Reproducible: Always

Steps to Reproduce:
1. remove phonon-qt4 dev files and install phonon-qt5 dev files
2. try to compile ktp-call-ui

Actual Results:  
build error: "libktpcall/private/phonon-integration.h:28:25: fatal error: phonon/Global: No such file or directory"

Expected Results:  
no build error
Comment 1 Martin Klapetek 2015-03-02 00:09:03 UTC
At this point the ktp-call-ui is not considered "done porting" yet (and there are no near-future plans unfortunately).

Once the porting of call ui happens, there will of course be a step to ensure everything builds and works.
Comment 2 kde 2015-03-02 00:27:53 UTC
yeah, but I thought I would try and point out what may cause trouble later. If stuff like that won't noticed or fixed before "done porting" the issue will come up later anyway.
Comment 3 Justin Zobel 2021-03-09 07:26:25 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.