digiKam › digikam-devel

Problems from a Disitrbution End - Build issues - kipi-plugins-0.2.0-beta3.tar.bz2

Classic

List

Threaded

2 messages Options

Mark Purcell

Problems from a Disitrbution End - Build issues - kipi-plugins-0.2.0-beta3.tar.bz2

Hi,

I have an issue building kipi-plugins with KDE 4.1.2 in Debian.

I don't expect the libdraw will be functional as that needs svn TRUNK, which
the build detects, however the build then goes on to try and build anyway and
blows up because the API has changed ;-(

Just to echo Angelo's comments, please make the packages, even in development
releases buildable against the published libs, even if additional
functionality is dropped. In Debian and I presume other distros we don't wish
to backport features from svn TRUNK (to echo Aaron Seigo's blog from a few
days ago.)

In Debian we have a sandbox called experimental where we are assembling KDE4,
that has the published versions of libs in KDE 4.1.2. I too am trying to get
digikam and friends into the Debian KDE4 sandbox, however the last version of
digikam that is buildable against published libs is 0.10.0-beta2. kipi-
plugins for KDE4 has never be buildable against published libs.

I understand that digikam and friends for KDE4 is under heavy development and
isn't ready for prime time, so it is actually a prime candidate for the Debian
experimental sandbox, with the rest of KDE4. But we don't want to backport
various things from TRUNK.

There are a few early adopters in Debian and I think some useful feedback has
come in the past and will continue when we can get digikam into Debian. I
suspect other distros are having difficultly as are early adopter users having
to pull a few things from TRUNK to build a released version of a package. So
in reality digikam is missing number of beta testers that could/ should be
providing valuable feedback during the development cycle for 0.10.0

So enough of the problems from the distribution end. Could I ask you to
discuss during the bug sprint this weekend and potentially ensure that future
versions are buildable/ stable against the published API for libs that are now
part of the KDE release.

Thanks,
Mark

PS.. here is the log failure from kipi-plugins build:

[...]
-- Found LibXml2: /usr/lib/libxml2.so
-- Found LibXslt: /usr/lib/libxslt.so
-- Found X11: /usr/lib/libX11.so
-- checking for module 'libkdcraw>=0.4.0'
-- package 'libkdcraw>=0.4.0' not found
-- Found libksane: /usr/lib/libksane.so
--
--
----------------------------------------------------------------------------------
-- kipi-plugins 0.2.0-beta3 dependencies results <http://www.kipi-
plugins.org>
--
-- libjpeg library found............... YES
-- libtiff library found............... YES
-- libpng library found................ YES
-- libkipi library found............... YES
-- libkexiv2 library found............. YES
-- libkdcraw library found............. YES
-- libksane library found.............. YES (optional)
-- libxml2 library found............... YES (optional)
-- libxslt library found............... YES (optional)
-- libexpat library found.............. YES (optional)
-- native threads support found........ YES (optional)
-- libopengl library found............. YES (optional)
-- libX11 library found................ YES (optional)
-- kipi-plugins will be compiled....... YES
-- AcquireImages will be compiled...... YES (optional)
-- HtmlExport will be compiled......... YES (optional)
-- SlideShow will be compiled.......... YES (optional)
-- ImageViewer will be compiled........ YES (optional)
-- DNGConverter will be compiled....... NO (optional - Look README file for
more details about dependencies)
--
----------------------------------------------------------------------------------
[...]
[ 13%] Building CXX object
rawconverter/CMakeFiles/kipiplugin_rawconverter.dir/batchdialog.o
cd /home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-beta3/obj-i486-
linux-gnu/rawconverter && /usr/bin/g++ -D_BSD_SOURCE -
Dkipiplugin_rawconverter_EXPORTS -g -O2 -g -Wall -O2 -Wnon-virtual-dtor -Wno-
long-long -ansi -Wundef -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-
arith -Wformat-security -fno-exceptions -fno-check-new -fno-common -
Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -fvisibility-
inlines-hidden -O2 -g -fPIC -I/home/mark/src/kde-extras/build-area/kipi-
plugins-0.2.0-beta3/obj-i486-linux-gnu/rawconverter -I/home/mark/src/kde-
extras/build-area/kipi-plugins-0.2.0-beta3/rawconverter -I/home/mark/src/kde-
extras/build-area/kipi-plugins-0.2.0-beta3/common/libkipiplugins -
I/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-beta3/obj-i486-linux-
gnu/common/libkipiplugins -I/usr/include/KDE -I/usr/include/qt4/QtXmlPatterns
-I/usr/include/qt4/QtWebKit -I/usr/include/qt4/QtHelp -
I/usr/include/qt4/QtAssistant -I/usr/include/qt4/QtDBus -
I/usr/include/qt4/QtTest -I/usr/include/qt4/QtUiTools -
I/usr/include/qt4/QtScript -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtXml -
I/usr/include/qt4/QtSql -I/usr/include/qt4/QtOpenGL -
I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtDesigner -
I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -
I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -
I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -o
CMakeFiles/kipiplugin_rawconverter.dir/batchdialog.o -c /home/mark/src/kde-
extras/build-area/kipi-plugins-0.2.0-beta3/rawconverter/batchdialog.cpp
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp: In constructor
'KIPIRawConverterPlugin::BatchDialog::BatchDialog(KIPI::Interface*)':
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:185: error: 'SIXTEENBITS' is not a member
of 'KDcrawIface::DcrawSettingsWidget'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:186: error: 'COLORSPACE' is not a member of
'KDcrawIface::DcrawSettingsWidget'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:187: error: 'POSTPROCESSING' is not a
member of 'KDcrawIface::DcrawSettingsWidget'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:188: error: 'BLACKWHITEPOINTS' is not a
member of 'KDcrawIface::DcrawSettingsWidget'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:191: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'addItem'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:192: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'updateMinimumWidth'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp: In member function 'void
KIPIRawConverterPlugin::BatchDialog::slotSixteenBitsImageToggled(bool)':
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:300: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named
'setEnabledBrightnessSettings'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp: In member function 'void
KIPIRawConverterPlugin::BatchDialog::readSettings()':
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:345: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'setUseWhitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:346: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'setWhitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:347: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'setMedianFilterPasses'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp: In member function 'void
KIPIRawConverterPlugin::BatchDialog::saveSettings()':
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:391: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'useWhitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:392: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'whitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:393: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'medianFilterPasses'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp: In member function 'void
KIPIRawConverterPlugin::BatchDialog::slotStartStop()':
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:454: error: 'class
KDcrawIface::RawDecodingSettings' has no member named 'enableWhitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:454: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'useWhitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:455: error: 'class
KDcrawIface::RawDecodingSettings' has no member named 'whitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:455: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'whitePoint'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:456: error: 'class
KDcrawIface::RawDecodingSettings' has no member named 'medianFilterPasses'
/home/mark/src/kde-extras/build-area/kipi-plugins-0.2.0-
beta3/rawconverter/batchdialog.cpp:456: error: 'class
KDcrawIface::DcrawSettingsWidget' has no member named 'medianFilterPasses'
make[3]: ***
[rawconverter/CMakeFiles/kipiplugin_rawconverter.dir/batchdialog.o] Error 1
make[3]: Leaving directory `/home/mark/src/kde-extras/build-area/kipi-
plugins-0.2.0-beta3/obj-i486-linux-gnu'
make[2]: *** [rawconverter/CMakeFiles/kipiplugin_rawconverter.dir/all] Error 2
make[2]: Leaving directory `/home/mark/src/kde-extras/build-area/kipi-
plugins-0.2.0-beta3/obj-i486-linux-gnu'
make[1]: *** [all] Error 2

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel

Gilles Caulier-4

Re: Problems from a Disitrbution End - Build issues - kipi-plugins-0.2.0-beta3.tar.bz2

2008/10/30 Mark Purcell <[hidden email]>

Hi,

I have an issue building kipi-plugins with KDE 4.1.2 in Debian.

I don't expect the libdraw will be functional as that needs svn TRUNK, which
the build detects, however the build then goes on to try and build anyway and
blows up because the API has changed ;-(

Just to echo Angelo's comments, please make the packages, even in development
releases buildable against the published libs, even if additional
functionality is dropped. In Debian and I presume other distros we don't wish
to backport features from svn TRUNK (to echo Aaron Seigo's blog from a few
days ago.)

In Debian we have a sandbox called experimental where we are assembling KDE4,
that has the published versions of libs in KDE 4.1.2. I too am trying to get
digikam and friends into the Debian KDE4 sandbox, however the last version of
digikam that is buildable against published libs is 0.10.0-beta2. kipi-
plugins for KDE4 has never be buildable against published libs.

I understand that digikam and friends for KDE4 is under heavy development and
isn't ready for prime time, so it is actually a prime candidate for the Debian
experimental sandbox, with the rest of KDE4. But we don't want to backport
various things from TRUNK.

I'm not agree. libkdcraw from trunk is better, faster and fixed against version published in KDE 4.1 branch. This is _why_ digiKam use it. Because i prefer a more stable code, digiKam and kipi-plugins are dumped depency to trunk version of shared libraries (libkdcraw and libkexiv2).

As we cannot touch KDE 4.1 branch fixes are not backported to preserve BC. It' completly stupid from my developper viewpoint...

I don't like static development and wait again and again KDE core release. Time is precious...

Unforget that digiKam 0.10.0 and kipi-plugins 0.2.0 still under development and not yet stable. If you want a stable version suitable in production, use KDE3 branch which can be used with KDE4 without problem....

Gilles Caulier

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel