On Sun, 2009-03-15 at 23:00 -0400, Isaac Emesowum wrote:
On Sun, 2009-03-15 at 22:36 +, Matt Davey wrote:
Isaac,
Looks like you're heading, and being pointed, in the right direction.
You may want to compile Evolution from source. I found it helpful to
use the Makefile contributed by Patrick Ohly:
http://mad-scientist.us/Makefile
to get started. You'll have to edit it to include gnome-pilot
(let me know if you'd like me to send you my edits)
If you can, keep your changes limited to the Evolution conduits code
(e.g. adding a new conduit but not requiring any changes to evolution
or evolution-data-server components). Otherwise it is likely to take
longer to get commit approval...
Feel free to post patches to this list and I'll certainly help
review and test. There are probably a few other lurkers might
help out too.
Matt
___
gnome-pilot-list mailing list
gnome-pilot-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gnome-pilot-list
Ahh, I see. From what I can tell, the difference between the two
interfaces is simply a few extra fields in the pi-calendar.h version.
From looking at the Evolution calendar conduit, it shouldn't be too hard
to port the existing code to the new interface and replace the used
Struct.
Matt,
I've grabbed Evolutions source from the Ubuntu Intrepid repository. I
used apt-get source evolution and apt-get build-dep evolution.
However, I should probably be using the latest version of Evolution from
svn.
Yes, please send me your edits as they will save me some time.
Isaac,
Just in case you hadn't spotted, the existing conduit code is required
to support devices running older versions of PalmOS. The current
devices have a compatibility layer that maps old fields to the new
databases, allowing us to use a single conduit for all devices. When
you add support for the new calendar database, you will have to ensure
the old code continues to work. The simplest thing to do is to create a
new conduit that registers for the new database, leaving the old conduit
as is. If there is code you can share, or a smart way of using a single
conduit, great, but I don't think that is trivial.
I'm attaching my modified Makefile. I've made very few changes from the
version written by Paul Smith and Patrick Ohly. The main work was
adding support for compiling gnome-pilot. It works by downloading
everything it needs from svn. It's a little while since I used it. I
had some trouble after Evo upgraded some of the libraries it depends on,
as my running system (Ubuntu 8.04) had the older versions. So, I stuck
with the Evo 2.24 branch. You can just blank that variable in the
Makefile to go with trunk.
I'm also attaching a version I hacked to use while offline, and just to
avoid downloading unnecessary updates from svn.
Matt
Matt Davey The Bermuda Triangle: Myth Or Fiction?
mcda...@mrao.cam.ac.uk
#!/usr/bin/make -f
#
# Build (debuggable) Evo from SVN
# Run make help for some help, or see the comments below.
#
# Requires GNU make 3.80 or better.
#
# Author: Paul Smith psm...@gnu.org
# Version: 2.12
# Date: 29 May 2008
#
# --
# Copyright (C) 2007, 2008 Paul Smith
# This Makefile is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License as published by the Free
# Software Foundation; either version 3 of the License, or (at your option)
# any later version.
#
# You should have a copy of the GNU General Public License on your system.
# If not, see http://www.gnu.org/licenses/.
# --
#
# You can look here for more/alternate information:
# http://www.go-evolution.org/Compiling_Evolution_from_SVN
#
# Enhancements/suggestions provided by:
# Patrick Ohly patrick.o...@gmx.de
# ==
# By default we build for Ubuntu (I'm testing on Ubuntu 8.04).
#
# If you want to build for another distro, see if it's listed in the DISTROS
# variable (currently only Debian Ubuntu releases are listed) and, if so,
# change DISTRO to your distro. You can do this in local.mk to avoid
# changing this makefile.
#
# If your distro is not supported, you can set distro to empty and the check
# for prerequisite packages will be skipped. Of course, if you don't have all
# the proper development packages installed the build will fail.
# ==
# v User Customization v
# Feel free to change these if you like
# What branch to work with. If not set, we use the trunk. Close to a
# release, however, you might prefer to use the pending release.
# E.g.:
# BRANCH := 2.20
BRANCH := 2.24
# Where to install Evo. DO NOT use /usr here for any system controlled by a
#
