From: "Ara.T.Howard" <Ara.T.Howard@...>
Date: 2004-04-21T04:54:08+09:00
Subject: C ext best practices


rubyists-

i'm wrapped a little libary that already has a full on gnu autotools
installation, call it

  libfoobar-0.0.0.tgz

obviously, this unpacks like

  libfoobar-0.0.0/
  libfoobar-0.0.0/README
  libfoobar-0.0.0/configure
  libfoobar-0.0.0/foobar.c

if i were to wrap this package for ruby, i'd like to be able to

  require 'foobar'

what is the preferred means to make an extenstion like this?

  * foobar.c defines ruby bindings and extconf.rb must be called with
  '--with-foobar-dir' pointing to an install of libfoobar?

  * _foobar.c defines ruby bindings and all libfoobar source files are simply
    dropped in same directory such that

      ruby extconf.rb
      make

    results in a foobar.so containing all required stuff?

thoughts?

-a
-- 
===============================================================================
| EMAIL   :: Ara [dot] T [dot] Howard [at] noaa [dot] gov
| PHONE   :: 303.497.6469
| ADDRESS :: E/GC2 325 Broadway, Boulder, CO 80305-3328
| URL     :: http://www.ngdc.noaa.gov/stp/
| TRY     :: for l in ruby perl;do $l -e "print \"\x3a\x2d\x29\x0a\"";done 
===============================================================================