aboutsummaryrefslogtreecommitdiffstats
path: root/calendar/conduits
Commit message (Expand)AuthorAgeFilesLines
* Update to use gpilotd_get_pilot_basedir and gnome_pilot_conduit_standard_abs...Vadim Strizhevsky2000-01-081-3/+1
* Added an argument to the corba get_number_of_objects, so you can decideEskil Heyn Olsen2000-01-051-52/+30
* Minor unmiportant changes, but my laptop is acting up, so IEskil Heyn Olsen1999-12-301-3/+8
* Capplets now sets first_sync on enable, this should make the conduit copyEskil Heyn Olsen1999-12-081-1/+4
* Check if local store is empty. If, force slow sync.Eskil Heyn Olsen1999-12-073-28/+50
* undef DEBUG_CALCONDUT, suppresses debug output.Eskil Heyn Olsen1999-12-031-2/+2
* Fixed compare bug. Also neated up some of the if's in set_status.Eskil Heyn Olsen1999-11-301-11/+13
* Writes some warning messages when pre_sync fails.Eskil Heyn Olsen1999-11-221-0/+2
* Enabled debug output. Sets a g_log_domain, now version 0.8.5. ConsistentEskil Heyn Olsen1999-11-101-96/+316
* Commented the code out, thus the capplet works again.Eskil Heyn Olsen1999-11-051-0/+2
* Uses the PISOCK_LIBDIR, for people with odd install dirs for theirEskil Olsen1999-11-044-79/+182
* now it doesn't build todo conduit anymore. Since the conduit is just aEskil Heyn Olsen1999-10-225-283/+358
* moved the pilot_status = MOD up, sBasic Installation ================== These are generic installation instructions. The `configure' shell script attempts to guess correct values for various system-dependent variables used during compilation. It uses those values to create a `Makefile' in each directory of the package. It may also create one or more `.h' files containing system-dependent definitions. Finally, it creates a shell script `config.status' that you can run in the future to recreate the current configuration, a file `config.cache' that saves the results of its tests to speed up reconfiguring, and a file `config.log' containing compiler output (useful mainly for debugging `configure'). If you need to do unusual things to compile the package, please try to figure out how `configure' could check whether to do them, and mail diffs or instructions to the address given in the `README' so they can be considered for the next release. If at some point `config.cache' contains results you don't want to keep, you may remove or edit it. The file `configure.in' is used to create `configure' by a program called `autoconf'. You only need `configure.in' if you want to change it or regenerate `configure' using a newer version of `autoconf'. The simplest way to compile this package is: 1. `cd' to the directory containing the package's source code and type `./configure' to configure the package for your system. If you're using `csh' on an old version of System V, you might need to type `sh ./configure' instead to prevent `csh' from trying to execute `configure' itself. Running `configure' takes awhile. While running, it prints some messages telling which features it is checking for. 2. Ty2-36/+135
* better merge of summary/description when doing ical_from_remoteEskil Heyn Olsen1999-09-234-5/+13
* better merge of summary/description when doing ical_from_remoteEskil Heyn Olsen1999-09-231-100/+149
* commented out a g_free that glib reported as being a duplicate free. gotEskil Heyn Olsen1999-09-231-7/+19
* lot of rework, implemented various set_* functions, transmit andEskil Heyn Olsen1999-09-212-168/+402
* About to rehash conduit.Eskil Heyn Olsen1999-09-191-4/+38
* changed to be a .la file instead of .a, this allows lib*_conduit to useEskil Heyn Olsen1999-09-192-43/+180
* added sources to calendar-conduitEskil Heyn Olsen1999-09-151-29/+238
* forgot the .desktop files...`Eskil Heyn Olsen1999-09-082-0/+12
* uses GNOME_PILOT_CHECKEskil Heyn Olsen1999-09-086-5/+1045
* fix this.Jonathan Blandford1999-08-031-0/+3
* add thisJonathan Blandford1999-07-311-0/+205
s for `configure' scripts to share, you can create a site shell script called `config.site' that gives default values for variables like `CC', `cache_file', and `prefix'. `configure' looks for `PREFIX/share/config.site' if it exists, then `PREFIX/etc/config.site' if it exists. Or, you can set the `CONFIG_SITE' environment variable to the location of the site script. A warning: not all `configure' scripts look for a site script. Operation Controls ================== `configure' recognizes the following options to control how it operates. `--cache-file=FILE' Use and save the results of the tests in FILE instead of `./config.cache'. Set FILE to `/dev/null' to disable caching, for debugging `configure'. `--help' Print a summary of the options to `configure', and exit. `--quiet' `--silent' `-q' Do not print messages saying which checks are being made. To suppress all normal output, redirect it to `/dev/null' (any error messages will still be shown). `--srcdir=DIR' Look for the package's source code in directory DIR. Usually `configure' can determine that directory automatically. `--version' Print the version of Autoconf used to generate the `configure' script, and exit. `configure' also accepts some other, not widely useful, options.