I myself am particularly knowledgeable in Ruby C extensions (yet?!?),
so I figured I'd send this around for input.
As far as gemspecs go, I think it really only cares about 'extconf.rb'
files. By convention, it looks like these live somewhere under 'ext'.
So, I'd propose having jeweler have this default:
gemspec.extensions = FileList["ext/**/extconf.rb"]
This seems pretty reasonable and straightforward.
And since we're on the subject, I'm sure the next thing people would
ask is about generating a project which includes the basic stuff for
doing a C extension. I haven't looked enough C extension libraries to
know what is considered good practices. For example, I've seen
extconf.rb as `ext/extconf.rb` or `ext/my-library/extconf.rb`. I'm
also not sure if there's any special rake tasks that are needed. Like,
do you need to compile the extensions before running tests?
Anyways, what are people's thoughts on this?
- Josh
---------- Forwarded message ----------
From: GitHub <nor...@github.com>
Date: Thu, Oct 29, 2009 at 6:24 PM
Subject: [GitHub] rdp sent you a message
To: jo...@technicalpickles.com
rdp sent you a message.
--------------------
Subject: jeweler extensions?
Might be nice to add
s.extensions = ["ext/extconf.rb"]
if ext/*.rb throw them in there :)
Thanks!
-r
--------------------
Reply on GitHub: http://github.com/inbox/299088#reply
http://github.com/luislavena/rake-compiler/
This seems pretty straightforward, and is probably easy to generate a
Rakefile setup for this.
Relatedly, I came across rake-tester, which is an extension to
rake-compiler for running C tests.
http://github.com/karottenreibe/rake-tester
That's cool, but even cooler was an example using both of these AND jeweler:
http://github.com/karottenreibe/joker
- Josh
If so, that'd make sense to look for mkrf_conf.rb as well.
- Josh