GPE: CVS

Accessing the GPE CVS repository

In short, if you are not (yet?) a developer, you do the following to get an initial copy of the GPE sources:

      $ cd gpe_cvs
      $ export CVSROOT=:pserver:anoncvs@cvs.handhelds.org:/cvs
      $ cvs login
      Logging in to :pserver:anoncvs@cvs.handhelds.org:2401/cvs
      CVS Password: anoncvs
      $ cvs checkout gpe

You only have to do this once. The next time you want to update your copy of the sources, do:

      $ cd gpe_cvs
      $ cvs update

If you are interested in what is going on in GPE CVS check out our CVSTrac site.

For a more detailed description about how to use handhelds.org CVS, please see here.

You can examine the CVS repository directly here.

Building GPE CVS applications

There is no easy recipe for building GPE applications for the ARM architecture yet. For a start, check the GpeCrossCompilation wiki page. However, GPE can be built like any other application for your desktop. A makefile in 'gpe_cvs/base' helps you build (most of) GPE:

      $ make -f Makefile.gpe DESTDIR=`pwd`/tmp-install install

make 3.80 is required, version 3.79.1 has been seen to not work. If this doesn't work for you: prerequisites for building GPE applications are libgpewidget and gpe-icons. Depending on the applications that you build, you may also need the below packages (-dev or -devel according to your distribution):

libsqlite-dev (sources),
dbus-1-dev, dbus-glib-1-dev (sources),
libmimedir (sources: use http://handhelds.org/~pb/libmimedir-20040225.tar.gz, or pull the sources from GNOME's CVS),
libbluetooth1-dev, libsdp2-dev (sources: bluez-libs from the BlueZ project),
libgmp3-dev (sources),
libsasl2-dev (sources).

So do the following before you attempt to compile one of the GPE applications:

      $ cd gpe_cvs/base
      $ cd libgpewidget
      $ make
      $ make install
      $ cd ../gpe-icons
      $ make install