Bug 18711

Summary: qmake (Qt5) doesn't point to proper QtOAuth include directory
Product: Mageia Reporter: JanKusanagi <jan-bugs>
Component: RPM PackagesAssignee: Mageia Bug Squad <bugsquad>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: Normal CC: geiger.david68210
Version: Cauldron   
Target Milestone: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Source RPM: qoauth-2.0.1-1.mga6.src.rpm CVE:
Status comment:
Attachments: Tarball with basic example project

Description JanKusanagi 2016-06-14 23:39:19 CEST 
Description of problem:

Qt5's qmake adds -I/usr/lib/include/QtOAuth to the Makefile if "CONFIG += oauth" is present in the .pro file.

That path is non-existant. The libqoauth-qt5-devel package installs headers in /usr/lib/qt5/include/QtOAuth instead.

I guess the oauth.prf file provided by libqoauth-qt5-devel has something wrong, or the headers should actually installed in that other path.

That same thing with Qt 4's qmake and libqoauth-devel, adds -I/usr/include/QtOAuth, which exists, and is where
libqoauth-devel (Qt4 version) installs the headers.


Files in libqoauth-devel: http://sophie.zarb.org/rpms/be1516a9e230d2a050f8e02509726ffe/files

Files in libqoauth-qt5-devel: http://sophie.zarb.org/rpms/c6abde3c41b462856a01ac9f7e132a4c/files



Thanks!!



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

libqoauth-qt5-devel-2.0.1-1.mga6.i586.rpm


How reproducible:

Every time, with a simple qmake-based Qt project that uses QOAuth, and is built with Qt 5.x.


Steps to Reproduce:
1. Create a basic .pro project, with qmake or QtCreator.
2. Add "CONFIG += oauth" somewhere in the .pro file.
3. In main.cpp, add #include <QtOAuth>
4. Generate a Makefile for the project, with Qt5 version of qmake, and
   build it.
5. Compilation fails due to QtOAuth header not found.
Comment 1 JanKusanagi 2016-06-14 23:59:12 CEST 
Created attachment 7996 [details]
Tarball with basic example project

I'm attaching a very simple sample project as demonstration.
Comment 2 David GEIGER 2016-06-15 10:41:23 CEST 
héhé! good catch!

Thanks for your report.

So now it should be fixed in the next qoauth update with qoauth-2.0.1-2.mga6

CC: (none) => geiger.david68210

Comment 3 JanKusanagi 2016-06-15 13:48:40 CEST 
Great! Thanks! \o/
Comment 4 David GEIGER 2016-06-15 14:03:37 CEST 
So closing of this bug as it is fixed!

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