summaryrefslogtreecommitdiff
path: root/jni/iconv/libcharset/HACKING
diff options
context:
space:
mode:
authorJari Vetoniemi <jari.vetoniemi@indooratlas.com>2020-03-16 18:49:26 +0900
committerJari Vetoniemi <jari.vetoniemi@indooratlas.com>2020-03-30 00:39:06 +0900
commitfcbf63e62c627deae76c1b8cb8c0876c536ed811 (patch)
tree64cb17de3f41a2b6fef2368028fbd00349946994 /jni/iconv/libcharset/HACKING
Fresh start
Diffstat (limited to 'jni/iconv/libcharset/HACKING')
-rw-r--r--jni/iconv/libcharset/HACKING36
1 files changed, 36 insertions, 0 deletions
diff --git a/jni/iconv/libcharset/HACKING b/jni/iconv/libcharset/HACKING
new file mode 100644
index 0000000..57c744c
--- /dev/null
+++ b/jni/iconv/libcharset/HACKING
@@ -0,0 +1,36 @@
+All you need to know when hacking (modifying) GNU libcharset or when building
+it off the CVS.
+
+
+Requirements
+============
+
+You will need reasonably recent versions of the build tools:
+
+ * A C compiler. Such as GNU GCC.
+ + Homepage:
+ http://gcc.gnu.org/
+
+ * GNU autoconf
+ + Homepage:
+ http://www.gnu.org/software/autoconf/
+
+ * GNU m4
+ + Homepage:
+ http://www.gnu.org/software/m4/
+
+ * Perl
+ + Homepage:
+ http://www.perl.org/
+
+And, of course, the packages listed in the DEPENDENCIES file.
+
+
+Building off the CVS
+====================
+
+Access to the CVS is described at http://sourceforge.net/cvs/?group_id=51585 .
+
+After fetching the sources from the CVS, peek at the comments in autogen.sh,
+then run "./autogen.sh"; then you can proceed with "./configure" as usual.
+