Bug 162964

Summary: Header-file: missing forward-declaration. Programs using libkexif-devel won't compile
Product: [Fedora] Fedora Reporter: Christian Nolte <ch.nolte>
Component: libkexifAssignee: Aurelien Bompard <gauret>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 4Keywords: EasyFix, Patch
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: 0.2.1-4.fc4 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-08-11 09:40:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 162161    
Attachments:
Description Flags
Patch which fixes the compile-problem. Can be directly included into SRPM none

Description Christian Nolte 2005-07-11 21:17:20 UTC 
Description of problem:

The File /usr/include/libkexif/kexifdialog.h defines the Class KExifDialog. When
compiling against this file (like for example with digikam-0.7.3), the Class
QComboBox is not known in line 54 of kexifdialog.h. This problem occurs because
no forward-declaration of QComboBox is given.

Perhaps this bug should be forwarded to the implementors of libkexif.

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

libkexif-devel-0.2.1-3

How reproducible:

Include the mentioned header-file into a cpp-file and compile it.
Or compile digikam version 0.7.3 with installed libkexif-devel-0.2.1-3 before
starting configure.

Additional Info:

A patch for the header-file is applied. So it could be integrated into the SRPM
of libkexif.

kdelibs-devel-3.4.1-0
qt-devel-3.3.4-15.1
libkexif-devel-0.2.1-
Comment 1 Christian Nolte 2005-07-11 21:17:20 UTC 
Created attachment 116625 [details]
Patch which fixes the compile-problem. Can be directly included into SRPM
Comment 2 Aurelien Bompard 2005-08-11 09:40:26 UTC 
Fixed in version 0.2.1-4.fc4, thanks. I contacted upstream, and it's fixed in CVS.