1 See README for dependencies.
3 If you get code from VCS, you will need Autotools (automake, autoconf,
4 libtool) and gettext in addition and you must prepare build system with
5 `autoreconf --install'.
7 Then run `./configure && make && make install' to build and install library
10 If you want to change installation directory use appropriate configure
11 argument (see `./configure --help' for more details).
13 Additional configure options:
17 Build example client. You can run and study example clients in `client'
22 Build and run library internal tests. You can run tests by
23 `make check'. You can run and study each test in `test' subdirectory.
27 Build and run library internal tests that require Internet access in
28 addition. --enable-test must be supplied too. You can run tests by
29 `make check'. You can run and study each test in `test/online'
34 Switch on debugging mode, compile in debugging code.
36 --disable-fatalwarnings
38 Switch off compile mode when compiler raises error on warning. This is
39 enabled to catch all code ambiguities by default.
43 Disable network operations by omitting cURL library. It disables
44 on-line tests too. Library will keep capability to process local
45 messages and delivery details. Library will not be able to connect to
46 ISDS server in this mode.
48 Large File Support (LFS) Notice: libisds uses GPGME, and GPGME is compiled
49 with LFS on usually. You need to keep LFS compatibility on reverse dependencies
50 (libisds library, your application using libisds), otherwise strange things
51 can happen (e.g. file/message/document sizes can mismatch). libisds switches
52 LFS on too. Use --disable-largefile to switch it off if you think it's more
53 appropriate. However recall this tweak when building your application.
55 Example clients and tests are not installed by `make install'.