Bug 328818 - 4.0.0-beta1 - Build Errors (kevix2.h)
Summary: 4.0.0-beta1 - Build Errors (kevix2.h)
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Compilation (show other bugs)
Version: 4.0.0
Platform: Debian unstable Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-14 23:30 UTC by Mark Purcell
Modified: 2017-08-19 21:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.0.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mark Purcell 2013-12-14 23:30:57 UTC
Do we need to build with a specific version of kexiv2?

Do we needs something newer than kexiv2 4.3.11?
 
Mark

Reproducible: Always

Actual Results:  

/tmp/buildd/digikam-4.0.0~beta1/core/libs/widgets/metadata/exifwidget.cpp: In 
member function 'virtual bool Digikam::ExifWidget::decodeMetadata()':
/tmp/buildd/digikam-4.0.0~beta1/core/libs/widgets/metadata/exifwidget.cpp:115:45: 
error: no matching function for call to 
'Digikam::DMetadata::getExifTagsDataList()'
     setMetadataMap(data.getExifTagsDataList());
                                             ^
/tmp/buildd/digikam-4.0.0~beta1/core/libs/widgets/metadata/exifwidget.cpp:115:45: 
note: candidate is:
In file included from 
/tmp/buildd/digikam-4.0.0~beta1/core/libs/dmetadata/dmetadata.h:38:0,
                 from /tmp/buildd/digikam-4.0.0~beta1/obj-i486-linux-
gnu/core/digikam/../../../core/libs/widgets/metadata/metadatawidget.h:38,
                 from /tmp/buildd/digikam-4.0.0~beta1/obj-i486-linux-
gnu/core/digikam/../../../core/libs/widgets/metadata/exifwidget.h:33,
                 from /tmp/buildd/digikam-4.0.0~beta1/obj-i486-linux-
gnu/core/digikam/exifwidget.moc:9,
                 from 
/tmp/buildd/digikam-4.0.0~beta1/core/libs/widgets/metadata/exifwidget.cpp:24:
/usr/include/libkexiv2/kexiv2.h:600:25: note: KExiv2Iface::KExiv2::MetaDataMap 
KExiv2Iface::KExiv2::getExifTagsDataList(const QStringList&, bool) const
     KExiv2::MetaDataMap getExifTagsDataList(const QStringList& 
exifKeysFilter, bool invertSelection=false) const;
                         ^
/usr/include/libkexiv2/kexiv2.h:600:25: note:   candidate expects 2 arguments, 
0 provided





Expected Results:  
If 4.0.0-beta1 requires kexiv2 > 4.11.3 then CMakeLists.txt should check for the relevant version, rather than allowing it to fail during compile time.

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.11-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages digikam depends on:
ii  kde-runtime           4:4.11.3-1
ii  libc6                 2.17-97
ii  libgcc1               1:4.8.2-10
ii  libgphoto2-2          2.4.14-2.4
ii  libgphoto2-port0      2.4.14-2.4
ii  libkdcraw22           4:4.11.3-1
ii  libkdecore5           4:4.11.3-2
ii  libkdeui5             4:4.11.3-2
ii  libkexiv2-11          4:4.11.3-1
ii  libkhtml5             4:4.11.3-2
ii  libkio5               4:4.11.3-2
ii  libkipi11             4:4.11.3-1
ii  libknotifyconfig4     4:4.11.3-2
ii  libkparts4            4:4.11.3-2
ii  libphonon4            4:4.7.1-1
ii  libqt4-dbus           4:4.8.5+git192-g085f851+dfsg-2
ii  libqt4-sql            4:4.8.5+git192-g085f851+dfsg-2
ii  libqt4-sql-sqlite     4:4.8.5+git192-g085f851+dfsg-2
ii  libqt4-xml            4:4.8.5+git192-g085f851+dfsg-2
ii  libqtcore4            4:4.8.5+git192-g085f851+dfsg-2
ii  libqtgui4             4:4.8.5+git192-g085f851+dfsg-2
ii  libsolid4             4:4.11.3-2
ii  libstdc++6            4.8.2-10
ii  libthreadweaver4      4:4.11.3-2
ii  perl                  5.18.1-5
ii  phonon                4:4.7.1-1
Comment 2 caulier.gilles 2013-12-15 07:03:26 UTC
This problem is already fixed for next 4.0.0-beta2

Gilles Caulier
Comment 3 Mark Purcell 2013-12-15 07:05:16 UTC
On Sun, 15 Dec 2013 07:03:26 Gilles Caulier wrote:
> This problem is already fixed for next 4.0.0-beta2

Thanks,

Great news.

Mark