File:  [ELWIX - Embedded LightWeight unIX -] / embedaddon / libiconv / HACKING
Revision 1.1.1.1 (vendor branch): download - view: text, annotated - select for diffs - revision graph
Tue Feb 21 22:57:48 2012 UTC (12 years, 4 months ago) by misho
Branches: libiconv, MAIN
CVS tags: v1_14p0, v1_14, v1_13_1, HEAD
libiconv

    1: All you need to know when hacking (modifying) GNU libiconv or when building
    2: it off the CVS.
    3: 
    4: 
    5: Requirements
    6: ============
    7: 
    8: You will need reasonably recent versions of the build tools:
    9: 
   10:   * A C compiler. Such as GNU GCC.
   11:     + Homepage:
   12:       http://gcc.gnu.org/
   13: 
   14:   * GNU automake
   15:     + Homepage:
   16:       http://www.gnu.org/software/automake/
   17: 
   18:   * GNU autoconf
   19:     + Homepage:
   20:       http://www.gnu.org/software/autoconf/
   21: 
   22:   * GNU m4
   23:     + Homepage:
   24:       http://www.gnu.org/software/m4/
   25: 
   26:   * GNU gperf
   27:     + Homepage:
   28:       http://www.gnu.org/software/gperf/
   29: 
   30:   * GNU groff 1.17 or newer
   31:     + Homepage:
   32:       http://www.gnu.org/software/groff/
   33: 
   34:   * Perl
   35:     + Homepage:
   36:       http://www.perl.org/
   37: 
   38:   * Either an internet connection or a recent copy of GNU gnulib.
   39:     + Homepage:
   40:       http://www.gnu.org/software/gnulib/
   41: 
   42: And, of course, the packages listed in the DEPENDENCIES file.
   43: 
   44: 
   45: Building off the CVS
   46: ====================
   47: 
   48: Access to the CVS is described at http://sourceforge.net/cvs/?group_id=51585 .
   49: 
   50: After fetching the sources from the CVS, peek at the comments in autogen.sh,
   51: then run "./autogen.sh"; then you can proceed with "./configure" as usual.
   52: 
   53: 
   54: Adding new encodings
   55: ====================
   56: 
   57: For an indication which encodings are acceptable in the official version of
   58: GNU libiconv, take a look at NOTES.
   59: 
   60: For an indication which files need to be modified when adding a new encoding,
   61: look for example at the 2007-05-25 ChangeLog entry for RK1048.  The lib/*.h
   62: file for an encoding is usually generated by one of the tools in the tools/
   63: directory.  All you need to provide is the conversion table in the format of
   64: the many *.TXT files.

FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>