Permalink
Browse files

import onig-5.9.2.tar.gz

  • Loading branch information...
0 parents commit 2eeb2788946cd95b641a2e9be08337a2059f0eb4 @sunaku committed Nov 13, 2011
Showing with 88,294 additions and 0 deletions.
  1. +1 −0 AUTHORS
  2. +28 −0 COPYING
  3. +2,052 −0 HISTORY
  4. +236 −0 INSTALL
  5. +94 −0 Makefile.am
  6. +1,238 −0 Makefile.in
  7. +189 −0 README
  8. +195 −0 README.ja
  9. +8,760 −0 aclocal.m4
  10. +1,500 −0 config.guess
  11. +115 −0 config.h.in
  12. +1,616 −0 config.sub
  13. +15,507 −0 configure
  14. +92 −0 configure.in
  15. +584 −0 depcomp
  16. +602 −0 doc/API
  17. +610 −0 doc/API.ja
  18. +37 −0 doc/FAQ
  19. +130 −0 doc/FAQ.ja
  20. +449 −0 doc/RE
  21. +460 −0 doc/RE.ja
  22. +58 −0 enc/ascii.c
  23. +162 −0 enc/big5.c
  24. +200 −0 enc/cp1251.c
  25. +285 −0 enc/euc_jp.c
  26. +158 −0 enc/euc_kr.c
  27. +129 −0 enc/euc_tw.c
  28. +495 −0 enc/gb18030.c
  29. +272 −0 enc/iso8859_1.c
  30. +239 −0 enc/iso8859_10.c
  31. +96 −0 enc/iso8859_11.c
  32. +228 −0 enc/iso8859_13.c
  33. +241 −0 enc/iso8859_14.c
  34. +235 −0 enc/iso8859_15.c
  35. +237 −0 enc/iso8859_16.c
  36. +235 −0 enc/iso8859_2.c
  37. +235 −0 enc/iso8859_3.c
  38. +237 −0 enc/iso8859_4.c
  39. +226 −0 enc/iso8859_5.c
  40. +96 −0 enc/iso8859_6.c
  41. +222 −0 enc/iso8859_7.c
  42. +96 −0 enc/iso8859_8.c
  43. +228 −0 enc/iso8859_9.c
  44. +250 −0 enc/koi8.c
  45. +212 −0 enc/koi8_r.c
  46. +1,162 −0 enc/mktable.c
  47. +318 −0 enc/sjis.c
  48. +11,356 −0 enc/unicode.c
  49. +225 −0 enc/utf16_be.c
  50. +226 −0 enc/utf16_le.c
  51. +184 −0 enc/utf32_be.c
  52. +184 −0 enc/utf32_le.c
  53. +305 −0 enc/utf8.c
  54. +187 −0 index.html
  55. +190 −0 index_ja.html
  56. +507 −0 install-sh
  57. +7,874 −0 ltmain.sh
  58. +367 −0 missing
  59. +78 −0 onig-config.in
  60. +85 −0 oniggnu.h
  61. +169 −0 onigposix.h
  62. +822 −0 oniguruma.h
  63. +6,254 −0 regcomp.c
  64. +902 −0 regenc.c
  65. +189 −0 regenc.h
  66. +387 −0 regerror.c
  67. +3,803 −0 regexec.c
  68. +222 −0 regext.c
  69. +167 −0 reggnu.c
  70. +808 −0 regint.h
  71. +5,552 −0 regparse.c
  72. +351 −0 regparse.h
  73. +98 −0 regposerr.c
  74. +303 −0 regposix.c
  75. +315 −0 regsyntax.c
  76. +76 −0 regtrav.c
  77. +56 −0 regversion.c
  78. +25 −0 sample/Makefile.am
  79. +518 −0 sample/Makefile.in
  80. +127 −0 sample/crnl.c
  81. +298 −0 sample/encode.c
  82. +107 −0 sample/listcap.c
  83. +72 −0 sample/names.c
  84. +93 −0 sample/posix.c
  85. +56 −0 sample/simple.c
  86. +73 −0 sample/sql.c
  87. +74 −0 sample/syntax.c
  88. +578 −0 st.c
  89. +63 −0 st.h
  90. +863 −0 testc.c
  91. +911 −0 testu.c
  92. +200 −0 win32/Makefile
  93. +84 −0 win32/config.h
  94. +863 −0 win32/testc.c
@@ -0,0 +1 @@
+sndgk393 AT ybb DOT ne DOT jp (K.Kosako)
28 COPYING
@@ -0,0 +1,28 @@
+Oniguruma LICENSE
+-----------------
+
+/*-
+ * Copyright (c) 2002-2007 K.Kosako <sndgk393 AT ybb DOT ne DOT jp>
+ * All rights reserved.
+ *
+ * Redistribution and use in source and binary forms, with or without
+ * modification, are permitted provided that the following conditions
+ * are met:
+ * 1. Redistributions of source code must retain the above copyright
+ * notice, this list of conditions and the following disclaimer.
+ * 2. Redistributions in binary form must reproduce the above copyright
+ * notice, this list of conditions and the following disclaimer in the
+ * documentation and/or other materials provided with the distribution.
+ *
+ * THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
+ * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+ * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ * ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
+ * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+ * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+ * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+ * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+ * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+ * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+ * SUCH DAMAGE.
+ */
2,052 HISTORY

Large diffs are not rendered by default.

Oops, something went wrong.
236 INSTALL
@@ -0,0 +1,236 @@
+Installation Instructions
+*************************
+
+Copyright (C) 1994, 1995, 1996, 1999, 2000, 2001, 2002, 2004, 2005 Free
+Software Foundation, Inc.
+
+This file is free documentation; the Free Software Foundation gives
+unlimited permission to copy, distribute and modify it.
+
+Basic 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, and a
+file `config.log' containing compiler output (useful mainly for
+debugging `configure').
+
+ It can also use an optional file (typically called `config.cache'
+and enabled with `--cache-file=config.cache' or simply `-C') that saves
+the results of its tests to speed up reconfiguring. (Caching is
+disabled by default to prevent problems with accidental use of stale
+cache files.)
+
+ 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 you are using the cache, and at
+some point `config.cache' contains results you don't want to keep, you
+may remove or edit it.
+
+ The file `configure.ac' (or `configure.in') is used to create
+`configure' by a program called `autoconf'. You only need
+`configure.ac' 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. Type `make' to compile the package.
+
+ 3. Optionally, type `make check' to run any self-tests that come with
+ the package.
+
+ 4. Type `make install' to install the programs and any data files and
+ documentation.
+
+ 5. You can remove the program binaries and object files from the
+ source code directory by typing `make clean'. To also remove the
+ files that `configure' created (so you can compile the package for
+ a different kind of computer), type `make distclean'. There is
+ also a `make maintainer-clean' target, but that is intended mainly
+ for the package's developers. If you use it, you may have to get
+ all sorts of other programs in order to regenerate files that came
+ with the distribution.
+
+Compilers and Options
+=====================
+
+Some systems require unusual options for compilation or linking that the
+`configure' script does not know about. Run `./configure --help' for
+details on some of the pertinent environment variables.
+
+ You can give `configure' initial values for configuration parameters
+by setting variables in the command line or in the environment. Here
+is an example:
+
+ ./configure CC=c89 CFLAGS=-O2 LIBS=-lposix
+
+ *Note Defining Variables::, for more details.
+
+Compiling For Multiple Architectures
+====================================
+
+You can compile the package for more than one kind of computer at the
+same time, by placing the object files for each architecture in their
+own directory. To do this, you must use a version of `make' that
+supports the `VPATH' variable, such as GNU `make'. `cd' to the
+directory where you want the object files and executables to go and run
+the `configure' script. `configure' automatically checks for the
+source code in the directory that `configure' is in and in `..'.
+
+ If you have to use a `make' that does not support the `VPATH'
+variable, you have to compile the package for one architecture at a
+time in the source code directory. After you have installed the
+package for one architecture, use `make distclean' before reconfiguring
+for another architecture.
+
+Installation Names
+==================
+
+By default, `make install' will install the package's files in
+`/usr/local/bin', `/usr/local/man', etc. You can specify an
+installation prefix other than `/usr/local' by giving `configure' the
+option `--prefix=PREFIX'.
+
+ You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files. If you
+give `configure' the option `--exec-prefix=PREFIX', the package will
+use PREFIX as the prefix for installing programs and libraries.
+Documentation and other data files will still use the regular prefix.
+
+ In addition, if you use an unusual directory layout you can give
+options like `--bindir=DIR' to specify different values for particular
+kinds of files. Run `configure --help' for a list of the directories
+you can set and what kinds of files go in them.
+
+ If the package supports it, you can cause programs to be installed
+with an extra prefix or suffix on their names by giving `configure' the
+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+
+Optional Features
+=================
+
+Some packages pay attention to `--enable-FEATURE' options to
+`configure', where FEATURE indicates an optional part of the package.
+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
+is something like `gnu-as' or `x' (for the X Window System). The
+`README' should mention any `--enable-' and `--with-' options that the
+package recognizes.
+
+ For packages that use the X Window System, `configure' can usually
+find the X include and library files automatically, but if it doesn't,
+you can use the `configure' options `--x-includes=DIR' and
+`--x-libraries=DIR' to specify their locations.
+
+Specifying the System Type
+==========================
+
+There may be some features `configure' cannot figure out automatically,
+but needs to determine by the type of machine the package will run on.
+Usually, assuming the package is built to be run on the _same_
+architectures, `configure' can figure that out, but if it prints a
+message saying it cannot guess the machine type, give it the
+`--build=TYPE' option. TYPE can either be a short name for the system
+type, such as `sun4', or a canonical name which has the form:
+
+ CPU-COMPANY-SYSTEM
+
+where SYSTEM can have one of these forms:
+
+ OS KERNEL-OS
+
+ See the file `config.sub' for the possible values of each field. If
+`config.sub' isn't included in this package, then this package doesn't
+need to know the machine type.
+
+ If you are _building_ compiler tools for cross-compiling, you should
+use the `--target=TYPE' option to select the type of system they will
+produce code for.
+
+ If you want to _use_ a cross compiler, that generates code for a
+platform different from the build platform, you should specify the
+"host" platform (i.e., that on which the generated programs will
+eventually be run) with `--host=TYPE'.
+
+Sharing Defaults
+================
+
+If you want to set default values 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.
+
+Defining Variables
+==================
+
+Variables not defined in a site shell script can be set in the
+environment passed to `configure'. However, some packages may run
+configure again during the build, and the customized values of these
+variables may be lost. In order to avoid this problem, you should set
+them in the `configure' command line, using `VAR=value'. For example:
+
+ ./configure CC=/usr/local2/bin/gcc
+
+causes the specified `gcc' to be used as the C compiler (unless it is
+overridden in the site shell script). Here is a another example:
+
+ /bin/bash ./configure CONFIG_SHELL=/bin/bash
+
+Here the `CONFIG_SHELL=/bin/bash' operand causes subsequent
+configuration-related scripts to be executed by `/bin/bash'.
+
+`configure' Invocation
+======================
+
+`configure' recognizes the following options to control how it operates.
+
+`--help'
+`-h'
+ Print a summary of the options to `configure', and exit.
+
+`--version'
+`-V'
+ Print the version of Autoconf used to generate the `configure'
+ script, and exit.
+
+`--cache-file=FILE'
+ Enable the cache: use and save the results of the tests in FILE,
+ traditionally `config.cache'. FILE defaults to `/dev/null' to
+ disable caching.
+
+`--config-cache'
+`-C'
+ Alias for `--cache-file=config.cache'.
+
+`--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.
+
+`configure' also accepts some other, not widely useful, options. Run
+`configure --help' for more details.
+
@@ -0,0 +1,94 @@
+## Makefile.am for Oniguruma
+encdir = $(top_srcdir)/enc
+sampledir = $(top_srcdir)/sample
+libname = libonig.la
+
+#AM_CFLAGS = -DNOT_RUBY
+AM_CFLAGS =
+INCLUDES = -I$(top_srcdir) -I$(includedir)
+
+SUBDIRS = . sample
+
+include_HEADERS = oniguruma.h oniggnu.h onigposix.h
+lib_LTLIBRARIES = $(libname)
+
+libonig_la_SOURCES = regint.h regparse.h regenc.h st.h \
+ regerror.c regparse.c regext.c regcomp.c regexec.c reggnu.c \
+ regenc.c regsyntax.c regtrav.c regversion.c st.c \
+ regposix.c regposerr.c \
+ $(encdir)/unicode.c $(encdir)/ascii.c $(encdir)/utf8.c \
+ $(encdir)/utf16_be.c $(encdir)/utf16_le.c \
+ $(encdir)/utf32_be.c $(encdir)/utf32_le.c \
+ $(encdir)/euc_jp.c $(encdir)/sjis.c $(encdir)/iso8859_1.c \
+ $(encdir)/iso8859_2.c $(encdir)/iso8859_3.c \
+ $(encdir)/iso8859_4.c $(encdir)/iso8859_5.c \
+ $(encdir)/iso8859_6.c $(encdir)/iso8859_7.c \
+ $(encdir)/iso8859_8.c $(encdir)/iso8859_9.c \
+ $(encdir)/iso8859_10.c $(encdir)/iso8859_11.c \
+ $(encdir)/iso8859_13.c $(encdir)/iso8859_14.c \
+ $(encdir)/iso8859_15.c $(encdir)/iso8859_16.c \
+ $(encdir)/euc_tw.c $(encdir)/euc_kr.c $(encdir)/big5.c \
+ $(encdir)/gb18030.c $(encdir)/koi8_r.c $(encdir)/cp1251.c
+
+libonig_la_LDFLAGS = -version-info $(LTVERSION)
+
+EXTRA_DIST = HISTORY README.ja index.html index_ja.html \
+ doc/API doc/API.ja doc/RE doc/RE.ja doc/FAQ doc/FAQ.ja \
+ win32/Makefile win32/config.h win32/testc.c \
+ $(encdir)/koi8.c $(encdir)/mktable.c \
+ $(sampledir)/encode.c $(sampledir)/listcap.c $(sampledir)/names.c \
+ $(sampledir)/posix.c $(sampledir)/simple.c $(sampledir)/sql.c \
+ $(sampledir)/syntax.c
+
+bin_SCRIPTS = onig-config
+
+onig-config: onig-config.in
+
+dll:
+ $(CXX) -shared -Wl,--output-def,libonig.def -o libonig.dll *.o \
+ $(LIBS)
+ strip libonig.dll
+
+# Ruby TEST
+rtest:
+ $(RUBYDIR)/ruby -w -Ke $(srcdir)/test.rb
+
+# character-types-table source generator
+mktable: $(encdir)/mktable.c $(srcdir)/regenc.h
+ $(CC) -I$(top_srcdir) -o mktable $(encdir)/mktable.c
+
+
+# TEST
+TESTS = testc testp testcu
+
+check_PROGRAMS = testc testp testcu
+
+atest: testc testp testcu
+ @echo "[Oniguruma API, ASCII/EUC-JP check]"
+ @$(top_builddir)/testc | grep RESULT
+ @echo "[POSIX API, ASCII/EUC-JP check]"
+ @$(top_builddir)/testp | grep RESULT
+ @echo "[Oniguruma API, UTF-16 check]"
+ @$(top_builddir)/testcu | grep RESULT
+
+testc_SOURCES = testc.c
+testc_LDADD = libonig.la
+
+testp_SOURCES = testc.c
+testp_LDADD = libonig.la
+testp_CFLAGS = -DPOSIX_TEST
+
+testcu_SOURCES = testu.c
+testcu_LDADD = libonig.la
+
+
+#testc.c: $(srcdir)/test.rb $(srcdir)/testconv.rb
+# ruby -Ke $(srcdir)/testconv.rb < $(srcdir)/test.rb > $@
+
+#testu.c: $(srcdir)/test.rb $(srcdir)/testconvu.rb
+# ruby -Ke $(srcdir)/testconvu.rb $(srcdir)/test.rb > $@
+
+#win32/testc.c: $(srcdir)/test.rb $(srcdir)/testconv.rb
+# ruby -Ke $(srcdir)/testconv.rb -win < $(srcdir)/test.rb | nkf -cs > $@
+
+## END OF FILE
Oops, something went wrong.

0 comments on commit 2eeb278

Please sign in to comment.