A new version of libgda has been released. It is 2.99.2. They have
bumped the ABI version to 3.0. Consequently, libgda-2.0.pc is now
libgda-3.0.pc. Therefore, after upgrading to libgda 2.99.2, the build
in gda-dev branch fails.
Further feedback on gda-dev:
configure did not fail when libgda-2.0.pc was not present. The
configure.in should be updated to have an option to enable/disable this
backend (like the --enable-sql option for postgresql). When the libgda
is not present and the option is enabled, the configure should fail
rather than the build.
I've attached a trivial (stop-gap) patch to illustrate what I am
currently testing (i.e. simply to see if gnucash gda-dev builds with
libgda-3.0). This is not what I am suggesting as the mod to
configure.in. I'll work on that later.
So far gnucash gda-dev is still building, which is a good sign, but it
will be morning before I know if the build succeeded.
Mark
--- gda-dev/configure.in 2006-12-27 19:50:31.000000000 -0700
+++ mj-dev/configure.in 2006-12-27 19:50:12.000000000 -0700
@@ -538,7 +538,7 @@
### -----------------------
### LIBGDA
-LIBGDA_PACKAGE_NAME=libgda-2.0
+LIBGDA_PACKAGE_NAME=libgda-3.0
AC_ARG_WITH( libgda,
[ --with-libgda=PATH specify where to look for libgda],
[ LIBGDA_PACKAGE_NAME=$with_libgda/lib/pkgconfig/${LIBGDA_PACKAGE_NAME}.pc ])
_______________________________________________
gnucash-devel mailing list
[email protected]
https://lists.gnucash.org/mailman/listinfo/gnucash-devel
