I’m creating a ‘gem’ package for a ruby extension written in C.
I have a little problem:
First, let’s suppose the package is called “Mambo”.
Now, the “.so” (or “.dll”, or whatever) is called “mambo.so”.
In addition to “mambo.so”, I also have a “mambo.rb” which adds some
finishing touches to the Mambo module defined in “mambo.so”.
The problem is this:
If the user does “require ‘mambo’” in his code, Ruby will load
“mambo.rb”. It won’t load “mambo.so” (because require first checks for
.rb, only then for .so).
So how can I cause “mambo.so” to get loaded?
One solution is to rename “mambo.rb” to, say, “mambo_something.rb”, and
in it to “require ‘mambo’”. But… it doesn’t look neat.
[…]
One solution is to rename “mambo.rb” to, say, “mambo_something.rb”, and
in it to “require ‘mambo’”. But… it doesn’t look neat.
Ah, another solution, I think, is to have “autorequires =
[‘mambo_something’, ‘mambo’]” in the gem spec. This will load the two
files. Still, it doens’t look neat to have such a central file,
‘mambo_something.rb’, have something tucked to its name. Or does it?