This generates a basic skeleton for building C extensions.
Added the --ext option to the gem command. This generates a skeleton …
…for C extensions.
Git ignore build artifacts.
Aren't slashes supposed to turn into modules/directories in the gem naming convention? I'm a hair worried about turning dashes into underscores. :P
I see what you mean, but typically C extensions won't have nested Modules (look at Mysql2, Nokogiri, etc).
If you believe it should behave differently, care to expand on it so I can fix it? ;-)
Maybe just raise an exception if the gem with an extension has a dash in the name? "C extensions don't have namespaces what are you doing go read the rubygems guide about naming" or something like that.
That's a good way of doing it. Let me find some documentation to link to and I'll get it fixed in the next 15 minutes.
Throw an error whenever a gem name does not conform to the C extensio…
…n naming guidelines.
That should do the trick!
Fixed failure in bundle gem command spec due to extra newline added in …
Committed manually by f3321c7
also 3f557a4, 49aa6aa, and 6a04e5b