1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
|
If you have unsynced changes sync before installing a newer version of
J-Pilot.
Be sure to read the docs in the doc directory, or if installed from the RPM
in /usr/doc/jpilot-0.97/.
To compile J-Pilot you need to have GTK+1.2 or better.
You can find out what version you have by running "gtk-config --version".
GTK+ requires glib. The glib version probably should match the gtk version.
You can also do a "glib-config --version".
You can get these at http://www.gtk.org
Pilot link must be installed and working.
ftp://ryeham.ee.ryerson.ca/pub/PalmOS/
RedHat users must also have the pilot-link-dev rpm installed for the header
files so that jpilot can compile. You don't need these if you install the
RPM.
To compile and install do the following:
./configure
make
make install
jpilot
For Japanese support, use ./configure --with-japanese, ./configure --help
will list all the options.
See below for compiling plugins.
make uninstall is an option also.
I have included a spec file so if you want to create your own RPM all you
have to do is "rpm -tb jpilot-0.97.tar.gz"
JPilot was written in such a way that it should be very safe to sync.
There is always the possibility of something going wrong though. As with
anything else, backup your data if you cannot afford to lose it. Just make
sure your backup software destroy it first ;)
I have added a couple of example plugins Expense, and SyncTime. To use them
make libplugin
change to the directory (Expense, etc.) and do
./configure
make
make install (installs the plugin system wide)
If you want to install the plugin for just 1 user you can copy the shared
library to ~/.jpilot/plugins/
|
