Hi all,
please, how you build tdepim / kdepim on other distributions than Debian / Ubuntu? On Debian / Ubuntu we hold in Trinity apt sources OpenSync 0.22. But on newer distributions can swell problems with building. How is this solved on other distros?
Slavek --
please, how you build tdepim / kdepim on other distributions than Debian / Ubuntu? On Debian / Ubuntu we hold in Trinity apt sources OpenSync 0.22. But on newer distributions can swell problems with building. How is this solved on other distros?
I have not been building tdepim with kitchensync/opensync support. For testing purposes, I should. :) I'll download and build opensync and rebuild tdepim.
A quick check indicates that version 0.22 is the current opensync stable version.
With that said, what kind of build problems are you experiencing?
Darrell
On Sunday 14 of October 2012 20:33:22 Darrell Anderson wrote:
please, how you build tdepim / kdepim on other distributions than Debian / Ubuntu? On Debian / Ubuntu we hold in Trinity apt sources OpenSync 0.22. But on newer distributions can swell problems with building. How is this solved on other distros?
I have not been building tdepim with kitchensync/opensync support. For testing purposes, I should. :) I'll download and build opensync and rebuild tdepim.
A quick check indicates that version 0.22 is the current opensync stable version.
With that said, what kind of build problems are you experiencing?
Darrell
When compiling OpenSync 0.22 on Precise I solved removing unused variables - that was not the problem - see patch in:
http://trinity-devel.pearsoncomputing.net/?0::10124
When compiling on Quantal I get:
error: 'g_thread_init' is deprecated error: 'g_private_new' is deprecated
And then there is another thing - in the distribution is OpenSync 0.39. So keeping OpenSync 0.22 is holding another older dependency.
Slavek --
When compiling OpenSync 0.22 on Precise I solved removing unused variables - that was not the problem - see patch in:
http://trinity-devel.pearsoncomputing.net/?0::10124
When compiling on Quantal I get:
error: 'g_thread_init' is deprecated error: 'g_private_new' is deprecated
And then there is another thing - in the distribution is OpenSync 0.39. So keeping OpenSync 0.22 is holding another older dependency.
Sounds similar to other build failures we've had in the past few months with libpng, xine, glibc, etc.
I just finished building opensync 0.22. I am now building tdepim against that. I'll let you know how that goes. I'll try to find time to build a development version of opensync like 0.39.
Darrell
When compiling OpenSync 0.22 on Precise I solved removing unused variables - that was not the problem - see patch in:
http://trinity-devel.pearsoncomputing.net/?0::10124
When compiling on Quantal I get:
error: 'g_thread_init' is deprecated error: 'g_private_new' is deprecated
And then there is another thing - in the distribution
is
OpenSync 0.39. So keeping OpenSync 0.22 is holding another older dependency.
Sounds similar to other build failures we've had in the past few months with libpng, xine, glibc, etc.
I just finished building opensync 0.22. I am now building tdepim against that. I'll let you know how that goes. I'll try to find time to build a development version of opensync like 0.39.
Slavek,
On Slackware 13.1 32-bit, I built opensync 0.22 and tdepim with kitchensync enabled. No build problems with either.
I have not yet tested on Slackware 14.0 64-bit or with a development version of opensync (0.3x).
Darrell
On Sun, 14 Oct 2012 12:48:44 -0700 (PDT) Darrell Anderson humanreadable@yahoo.com wrote:
When compiling OpenSync 0.22 on Precise I solved removing unused variables - that was not the problem - see patch in:
http://trinity-devel.pearsoncomputing.net/?0::10124
When compiling on Quantal I get:
error: 'g_thread_init' is deprecated error: 'g_private_new' is deprecated
And then there is another thing - in the distribution
is
OpenSync 0.39. So keeping OpenSync 0.22 is holding another older dependency.
Sounds similar to other build failures we've had in the past few months with libpng, xine, glibc, etc.
I just finished building opensync 0.22. I am now building tdepim against that. I'll let you know how that goes. I'll try to find time to build a development version of opensync like 0.39.
Slavek,
On Slackware 13.1 32-bit, I built opensync 0.22 and tdepim with kitchensync enabled. No build problems with either.
I have not yet tested on Slackware 14.0 64-bit or with a development version of opensync (0.3x).
The KDE3 version of kitchensync will compile against opensync 0.36 (it may need a patchset whose contents I didn't actually check), but not against 0.38, per https://bugs.gentoo.org/show_bug.cgi?id=262397 . Unless someone has patched this further for Trinity, we may have a problem with opensync 0.39.
On Slackware 13.1 32-bit, I built opensync 0.22 and
tdepim with kitchensync enabled. No build problems with either.
I have not yet tested on Slackware 14.0 64-bit or with
a development version of opensync (0.3x).
The KDE3 version of kitchensync will compile against opensync 0.36 (it may need a patchset whose contents I didn't actually check), but not against 0.38, per https://bugs.gentoo.org/show_bug.cgi?id=262397 .
Unless someone has patched this further for Trinity, we may have a problem with opensync 0.39.
Oh, okay, so now we know the cutoff point. I will try testing with 0.36 and 0.38/0.39.
Darrell
On Sunday 14 of October 2012 23:55:51 Darrell Anderson wrote:
On Slackware 13.1 32-bit, I built opensync 0.22 and
tdepim with kitchensync enabled. No build problems with either.
I have not yet tested on Slackware 14.0 64-bit or with
a development version of opensync (0.3x).
The KDE3 version of kitchensync will compile against opensync 0.36 (it may need a patchset whose contents I didn't actually check), but not against 0.38, per https://bugs.gentoo.org/show_bug.cgi?id=262397 .
Unless someone has patched this further for Trinity, we may have a problem with opensync 0.39.
Oh, okay, so now we know the cutoff point. I will try testing with 0.36 and 0.38/0.39.
Darrell
OpenSync 0.22 is fine - exactly this version is used on Debian / Ubuntu. But on the newer Ubuntu I note problems with build OpenSync 0.22 - as I wrote earlier. Therefore, it would be good if we could support the newer version OpenSync that are included in newer distributions.
Slavek --
OpenSync 0.22 is fine - exactly this version is used on Debian / Ubuntu. But on the newer Ubuntu I note problems with build OpenSync 0.22
- as I wrote earlier. Therefore, it would be good if we could support the
newer version OpenSync that are included in newer distributions.
I discovered part of the problem.
With libopensync 0.22 the following are installed:
/usr/lib/pkgconfig/opensync-1.0.pc /usr/lib/pkgconfig/osengine-1.0.pc
With libopensync 0.39 only the following is installed:
/usr/lib/pkgconfig/libopensync.pc
There are no osengine files installed with 0.39.
The following need patching to support both 0.22 and >=0.30:
tdepim/kitchensync/libqopensync/ConfigureChecks.cmake tdepim/kitchensync/configure.in.in
I'm still testing (and ask others to do likewise), but here is my proposed patch:
========================================= diff -urN tdepim/kitchensync/configure.in.in tdepim.new/kitchensync/configure.in.in --- tdepim/kitchensync/configure.in.in 2012-09-14 18:01:26.000000000 -0500 +++ tdepim.new/kitchensync/configure.in.in 2012-10-14 22:42:40.000000000 -0500 @@ -31,7 +31,11 @@ HAVE_OPENSYNC=0 HAVE_OPENSYNC_ENGINE=0 PKG_CHECK_MODULES(OPENSYNC, opensync-1.0 >= 0.19, HAVE_OPENSYNC=1,HAVE_OPENSYNC=0) -PKG_CHECK_MODULES(OPENSYNCENGINE, osengine-1.0 >= 0.19, HAVE_OPENSYNC_ENGINE=1, HAVE_OPENSYNC_ENGINE=0) +if test "$HAVE_OPENSYNC" = 1; then + PKG_CHECK_MODULES(OPENSYNCENGINE, osengine-1.0 >= 0.19, HAVE_OPENSYNC_ENGINE=1, HAVE_OPENSYNC_ENGINE=0) +else + PKG_CHECK_MODULES(OPENSYNC, libopensync >= 0.19, HAVE_OPENSYNC=1,HAVE_OPENSYNC=0) +fi PKG_CHECK_MODULES(LIBXML, libxml-2.0, , HAVE_OPENSYNC=0) PKG_CHECK_MODULES(GLIB, glib-2.0 >= 2.6, , HAVE_OPENSYNC=0)
diff -urN tdepim/kitchensync/libqopensync/ConfigureChecks.cmake tdepim.new/kitchensync/libqopensync/ConfigureChecks.cmake --- tdepim/kitchensync/libqopensync/ConfigureChecks.cmake 2012-09-14 18:01:26.000000000 -0500 +++ tdepim.new/kitchensync/libqopensync/ConfigureChecks.cmake 2012-10-14 22:39:45.000000000 -0500 @@ -13,10 +13,13 @@
pkg_search_module( OPENSYNC opensync-1.0 ) if( NOT OPENSYNC_FOUND ) - tde_message_fatal( "opensync-1.0 is requested, but was not found on your system" ) -endif( ) - -pkg_search_module( OSENGINE osengine-1.0 ) -if( NOT OSENGINE_FOUND ) - tde_message_fatal( "osengine-1.0 is requested, but was not found on your system" ) + pkg_search_module( OPENSYNC libopensync ) + if( NOT OPENSYNC_FOUND ) + tde_message_fatal( "libopensync is requested, but was not found on your system" ) + endif( ) +else() + pkg_search_module( OSENGINE osengine-1.0 ) + if( NOT OSENGINE_FOUND ) + tde_message_fatal( "osengine-1.0 is requested, but was not found on your system" ) + endif( ) endif( ) =========================================
Darrell
I'm still testing (and ask others to do likewise), but here is my proposed patch:
With opensync 0.39 the build fails because osengine/engine.h no longer exists. Probably we need some preprocessor checks to use the correct includes:
tdepim/kitchensync/libqopensync/callbackhandler.cpp tdepim/kitchensync/libqopensync/engine.cpp tdepim/kitchensync/libqopensync/syncmapping.cpp tdepim/kitchensync/libqopensync/syncupdates.cpp
At this point I'm getting a tad over my head and need some help. :)
Darrell
With opensync 0.39 the build fails because osengine/engine.h no longer exists. Probably we need some preprocessor checks to use the correct includes:
tdepim/kitchensync/libqopensync/callbackhandler.cpp tdepim/kitchensync/libqopensync/engine.cpp tdepim/kitchensync/libqopensync/syncmapping.cpp tdepim/kitchensync/libqopensync/syncupdates.cpp
At this point I'm getting a tad over my head and need some help. :)
Slavek,
I'm not an opensync/kitchensync user, yet the problem deserves attention. I'm willing to help the project by testing patches. To that end I'm filing a bug report where anybody interested has a place to focus attention.
The bug report is 1271.
Darrell
On Monday 15 of October 2012 23:39:59 Darrell Anderson wrote:
With opensync 0.39 the build fails because osengine/engine.h no longer exists. Probably we need some preprocessor checks to use the correct includes:
tdepim/kitchensync/libqopensync/callbackhandler.cpp tdepim/kitchensync/libqopensync/engine.cpp tdepim/kitchensync/libqopensync/syncmapping.cpp tdepim/kitchensync/libqopensync/syncupdates.cpp
At this point I'm getting a tad over my head and need some help. :)
Slavek,
I'm not an opensync/kitchensync user, yet the problem deserves attention. I'm willing to help the project by testing patches. To that end I'm filing a bug report where anybody interested has a place to focus attention.
The bug report is 1271.
Darrell
Thank you,
I also not use KitchenSync + OpenSync. But I try to make Debian / Ubuntu packages were complete - for those who would possibly like to use it :)
I'm going to try to build on Ubuntu Quantal...
Slavek --
On Monday 15 of October 2012 23:39:59 Darrell Anderson wrote:
With opensync 0.39 the build fails because osengine/engine.h no longer exists. Probably we need some preprocessor checks to use the correct includes:
tdepim/kitchensync/libqopensync/callbackhandler.cpp tdepim/kitchensync/libqopensync/engine.cpp tdepim/kitchensync/libqopensync/syncmapping.cpp tdepim/kitchensync/libqopensync/syncupdates.cpp
At this point I'm getting a tad over my head and need some help. :)
Slavek,
I'm not an opensync/kitchensync user, yet the problem deserves attention. I'm willing to help the project by testing patches. To that end I'm filing a bug report where anybody interested has a place to focus attention.
The bug report is 1271.
Darrell
Instead of Quantal I tried build on Precise because on Quantal is OpenSync not part of distribution. Built - in the assumption - ending at the absence osengine/engine.h.
Slavek --
Instead of Quantal I tried build on Precise because on Quantal is OpenSync not part of distribution. Built - in the assumption - ending at the absence osengine/engine.h.
Yes, same failure I experienced. I haven't investigated further.
Darrell