[Rake-devel] Building native extensions with Rake

Berger, Daniel Daniel.Berger at qwest.com
Tue Nov 18 14:27:50 EST 2008


> -----Original Message-----
> From: rake-devel-bounces at rubyforge.org 
> [mailto:rake-devel-bounces at rubyforge.org] On Behalf Of Charlie Savage
> Sent: Tuesday, November 18, 2008 12:14 PM
> To: Rake Development and Discussion
> Subject: Re: [Rake-devel] Building native extensions with Rake
> Hi Dan,
> > Implementing an mkmf replacement was tried a while ago:
> > 
> > http://rubyforge.org/projects/mkmf2/
> > 
> > But it never caught on. But gems are more pervasive now, so 
> maybe if 
> > it was gemified, we could take another look. However, I 
> don't think it 
> > was ever trying to be a distutils replacement.
> Yeah, I had hopes that mkmf2 would solve the problem, but it 
> didn't  So although it was an improvement, it didn't solve 
> the fundamental problem, and thus wasn't enough of an improvement.

Do you think mkmf2 could be made to do the job? Or is it an evolutionary
dead end?
> > Porting distutils may be the answer, though. You volunteering? ;)
> With the amount of time I've spent figuring out how to 
> compile Ruby c extensions on C, I should have just started 
> with that :)
> As much as it would be interesting, I'm not volunteering.  
> libxml-ruby, libxslt-ruby and ruby-prof are taking all my 
> open source cycles at the moment.

It might be worth starting a RubyForge project anyway, recruit a few
people, get a few people testing and so on.

BTW, this looks like a current reference, yes?




This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly 
prohibited and may be unlawful.  If you have received this communication 
in error, please immediately notify the sender by reply e-mail and destroy 
all copies of the communication and any attachments.

More information about the Rake-devel mailing list