home *** CD-ROM | disk | FTP | other *** search
Text File | 2000-04-10 | 3.4 KB | 99 lines | [TEXT/ttxt] |
- * COPYRIGHT
-
- The ici module collection is,
-
- Copyright (C) 1999, A.Newman, All Rights Reserved.
-
- You may freely use the module collection in any program or product as
- long as the author is credited in the documentation accompanying the
- program or product. The code is not guaranteed to operate to any degree
- of robustness and is provided "AS IS" with no support. Blah, blah, blah.
-
- Now that's over...
-
-
- * INTRODUCTION
-
- This is Andy Newman's collection of modules for ici. The modules provide
- ici programs access to common libraries, protocols, etc... or provide
- generally useful functionality for many programs.
-
- See the file NEWS for information on changes and the file TODO for the
- start a list of things that need to be done. The file MODULES gives a
- short list of the available modules and the MANIFEST file lists all the
- files in the collection.
-
-
- * BUILDING
-
- You need the latest ici (2.1.2 at time of writing, 2.1.1 should
- work too) installed before starting. The module collection assumes
- ici gets installed in its "usual" place (/usr/local), the headers
- are in /usr/local/include/ici and modules get installed under
- /usr/local/lib/ici. If that's not true then things may not work
- without changes to makefiles.
-
- To build the collection on supported platforms type "make". The
- top-level makefile configures and build the entire collection. If a
- module is not supported for a particular configuration it is not
- built. The top-level makefile has the following targets:
-
- all Build everything.
- install Install everything.
- uninstall Remove everything "make install" installed.
- clean Clean up object files, etc...
- clobber Remove all generated files.
- config Run the configure program.
- depend Build dependencies.
- manifest Build a list of all the files in the file MANIFEST.
- tar Build a tar file from the files named in the MANIFEST.
- tgz As for tar but gzip it.
-
- Each module makefile also defines the all, install, clean, and depend
- targets. If you plan to do development work its wise to build dependencies.
- I use the BSD mkdep and have an ici clone of it for systems without it.
-
- All targets will perform a "make config" if it hasn't been done. This runs
- the configure program which creates symbolic links to system specific
- Makefiles for each module. It is NOT an autoconf generated configure script
- and is quite dumb by comparison. It should be a lot smarter but does for
- the present time.
-
-
- * INSTALLING
-
- Once built the modules should be installed with "make install". This
- assumes the existence of the /usr/local/lib/ici directory and permission
- to write files there.
-
-
- * PORTING
-
- To configure the system for an unsupported platform the configure
- program will need to be extended to recognise that platform and
- Makefiles written for the platform. Then you build and fix the
- portability bugs. Nothing to it!
-
- If you do port any of the modules to some platform please send the
- changes back so others can share your efforts and not duplicate
- tedious work.
-
-
- * SUPPORT PLATFORMS
-
- RedHat Linux Both libc5 and glibc systems work.
- See */Makefile.linux.
-
- FreeBSD 2.2.8 works. Not known how 3.x behaves.
- I suspect the FreeBSD port of ici lacks
- the -export-dynamic flag to cc which is
- needed for proper module support but I
- can't test this and can't be sure.
- See */Makefile.bsd
-
- Solaris Works with Solaris 2.5.1 with gcc. The
- build requires GNU make. I haven't tried
- the tcl or wings modules as I don't have
- them installed on my Solaris machine.
- See */Makefile.sol2
-