snappy_ext 0.1.2

data/ext/snappy/extconf.rb

@@ -0,0 +1,36 @@
+require 'mkmf'
+
+# Compile the embedded snappy- lib
+vendor_dir = File.join(File.dirname(__FILE__)), "vendor"
+snappy_dir = Dir[File.join(vendor_dir, "snappy-*")].first
+old_pwd = Dir.pwd
+begin
+  Dir.chdir(snappy_dir)
+  
+  fork {
+    exec("./configure")
+  }; Process.wait; exit(1) unless $?.success?
+  fork {
+    exec("make")
+  }; Process.wait; exit(1) unless $?.success?
+  
+ensure
+  Dir.chdir(old_pwd)
+end
+
+have_header("ruby/st.h") || have_header("st.h")
+
+# Pull in Snappy includes
+$INCFLAGS << " -I#{snappy_dir}"
+
+# Link with the Snappy object files
+Dir["#{snappy_dir}/.libs/*.o"].each { |o|
+  $LOCAL_LIBS << " #{o}"
+}
+
+# Ensure we're linked with CXX, or it all breaks, due to libstdc++ and such
+#CONFIG['LDSHARED'] = '$(CXX) -dynamiclib'
+
+have_library("stdc++")
+dir_config('snappy')
+create_makefile('snappy_ext')

data/ext/snappy/snappy_ext.cc

@@ -0,0 +1,131 @@
+#include <snappy.h>
+#include "version.h"
+
+#include "ruby.h"
+
+#if HAVE_RUBY_ST_H
+#include "ruby/st.h"
+#endif
+#if HAVE_ST_H
+#include "st.h"
+#endif
+
+#include <string.h>
+#include <stdio.h>
+
+#ifdef HAVE_RUBY_ENCODING_H
+#include <ruby/encoding.h>
+int binary_string_encoding;
+#endif
+
+VALUE binary_string_for_buffer(VALUE input, char * buf, size_t len)
+{
+  // Create the string
+  VALUE str = rb_str_new5(input, buf, len);
+  
+#ifdef HAVE_RUBY_ENCODING_H
+  // Set the encoding
+  rb_enc_associate_index(str, binary_string_encoding);
+#endif
+  
+  // Copy taintedness
+  OBJ_INFECT(input, str);
+  
+  return str;
+}
+
+/*
+ * call-seq:
+ *   compress(string) -> string
+ *
+ * returns a Snappy-compressed string
+ */
+extern "C"
+VALUE snappy_ext_compress(VALUE self, VALUE string)
+{
+  string = StringValue(string);
+
+  char * in_buf = RSTRING_PTR(string);
+  size_t in_len = RSTRING_LEN(string);
+  
+  char * out_buf = (char *)malloc(snappy::MaxCompressedLength(in_len));
+  size_t out_len = 0;
+    
+  snappy::RawCompress(in_buf, in_len, out_buf, &out_len);
+  
+  // Shrink the buffer
+  out_buf = (char *)realloc(out_buf, out_len);
+  
+  // Encase the output buffer in a String object without copying
+  return binary_string_for_buffer(string, out_buf, out_len);
+}
+
+/*
+ * call-seq:
+ *   uncompress(string) -> string
+ *
+ * Returns a decompressed string, or raises ArgumentError if the compressed
+ * data is somehow corrupt
+ */
+extern "C"
+VALUE snappy_ext_uncompress(VALUE self, VALUE string)
+{
+  string = StringValue(string);
+
+  char * in_buf = RSTRING_PTR(string);
+  size_t in_len = RSTRING_LEN(string);
+
+  size_t out_len = 0;
+
+  if (!snappy::GetUncompressedLength(in_buf, in_len, &out_len)) {
+    rb_raise(rb_eArgError, "invalid compressed data");
+  }
+  
+  char * out_buf = (char*)malloc(out_len);
+  
+  if (!snappy::RawUncompress(in_buf, in_len, out_buf)) {
+    free(out_buf);
+    rb_raise(rb_eArgError, "invalid compressed data");
+  }
+  
+  return binary_string_for_buffer(string, out_buf, out_len);
+}
+
+extern "C"
+void Init_snappy_ext()
+{
+  VALUE snappy_sym, snappy, snappy_ext;
+  
+  snappy_sym = rb_intern("Snappy");
+  
+#ifdef HAVE_RUBY_ENCODING_H
+  // Look up the BINARY encoding
+  binary_string_encoding = rb_enc_find_index("BINARY");
+#endif
+  
+  // Get or define ::Snappy
+  if (rb_const_defined(rb_cObject, snappy_sym)) {
+    snappy = rb_const_get(rb_cObject, rb_intern("Snappy"));
+  } else {
+    snappy = rb_define_module("Snappy");
+  }
+  
+  // Define Snappy::Ext
+  snappy_ext = rb_define_module_under(snappy, "Ext");
+  
+  // Pass in our version constants
+  rb_define_const(snappy_ext, "Version", rb_str_new2(GEM_VERSION));
+  {
+    char version[16];
+    snprintf(version, sizeof(version), "%u.%u.%u",
+      SNAPPY_VERSION >> 16 & 0xff, SNAPPY_VERSION >> 8 & 0xff, SNAPPY_VERSION & 0xff
+      );
+    rb_define_const(snappy_ext, "SnappyVersion", rb_str_new2(version));
+  }
+  
+  // Add our methods to both Snappy::Ext and Snappy
+  rb_define_module_function(snappy, "compress", RUBY_METHOD_FUNC(snappy_ext_compress), 1);
+  rb_define_module_function(snappy, "uncompress", RUBY_METHOD_FUNC(snappy_ext_uncompress), 1);
+  rb_define_module_function(snappy_ext, "compress", RUBY_METHOD_FUNC(snappy_ext_compress), 1);
+  rb_define_module_function(snappy_ext, "uncompress", RUBY_METHOD_FUNC(snappy_ext_uncompress), 1);
+}

data/ext/snappy/vendor/snappy-1.0.0/AUTHORS

@@ -0,0 +1 @@
+opensource@google.com

data/ext/snappy/vendor/snappy-1.0.0/COPYING

@@ -0,0 +1,28 @@
+Copyright (c) 2011, Google Inc.
+All rights reserved.
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are
+met:
+
+    * Redistributions of source code must retain the above copyright
+notice, this list of conditions and the following disclaimer.
+    * 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.
+    * Neither the name of Google Inc. nor the names of its
+contributors may be used to endorse or promote products derived from
+this software without specific prior written permission.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS 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 COPYRIGHT
+OWNER 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.

data/ext/snappy/vendor/snappy-1.0.0/ChangeLog

@@ -0,0 +1,3 @@
+Snappy v1.0, March 17th 2011:
+
+  * Initial version.

data/ext/snappy/vendor/snappy-1.0.0/INSTALL

@@ -0,0 +1,230 @@
+Copyright 1994, 1995, 1996, 1999, 2000, 2001, 2002 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=PATH'.
+
+   You can specify separate installation prefixes for
+architecture-specific files and architecture-independent files.  If you
+give `configure' the option `--exec-prefix=PATH', the package will use
+PATH 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=PATH' 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
+
+will cause the specified gcc to be used as the C compiler (unless it is
+overridden in the site shell script).
+
+`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.
+

data/ext/snappy/vendor/snappy-1.0.0/Makefile.am

@@ -0,0 +1,24 @@
+ACLOCAL_AMFLAGS = -I m4
+
+# Library.
+lib_LTLIBRARIES = libsnappy.la
+libsnappy_la_SOURCES = snappy.cc snappy-sinksource.cc snappy-stubs-internal.cc
+libsnappy_la_LDFLAGS = $(EXTRA_LIBSNAPPY_LDFLAGS)
+
+include_HEADERS = snappy.h snappy-sinksource.h snappy-stubs-public.h
+noinst_HEADERS = snappy-internal.h snappy-stubs-internal.h snappy-test.h
+
+# Unit tests and benchmarks.
+snappy_unittest_CPPFLAGS = $(gflags_CFLAGS) $(GTEST_CPPFLAGS)
+snappy_unittest_CXXFLAGS = $(GTEST_CPPFLAGS)
+snappy_unittest_SOURCES = snappy_unittest.cc snappy-test.cc
+snappy_unittest_LDFLAGS = $(GTEST_LDFLAGS)
+snappy_unittest_LDADD = libsnappy.la $(gflags_LIBS) $(GTEST_LIBS)
+TESTS = snappy_unittest
+noinst_PROGRAMS = $(TESTS)
+
+EXTRA_DIST = autogen.sh testdata/alice29.txt testdata/asyoulik.txt testdata/baddata1.snappy testdata/baddata2.snappy testdata/baddata3.snappy testdata/cp.html testdata/fields.c testdata/geo.protodata testdata/grammar.lsp testdata/house.jpg testdata/html testdata/html_x_4 testdata/kennedy.xls testdata/kppkn.gtb testdata/lcet10.txt testdata/mapreduce-osdi-1.pdf testdata/plrabn12.txt testdata/ptt5 testdata/sum testdata/urls.10K testdata/xargs.1 
+dist_doc_DATA = ChangeLog COPYING INSTALL NEWS README
+
+libtool: $(LIBTOOL_DEPS)
+	$(SHELL) ./config.status --recheck