From: Kevin Clark <kevin.clark@...>
Date: 2006-07-01T10:05:02+09:00
Subject: Re: [ANN] mkrf 0.1.0 released

Dan,
Most significantly, mkrf generates -Rakefiles-, not Makefiles. Because
I'm making Rakefiles it opens up a lot of functionalities that mkmf2
couldn't implement easily (gem packaging, rdoc generation built in
etc.). Also, as far as I know, mkmf2 isn't aiming for reuse of its
code. One of my goals is to make the Availability code clean and
simple enough that things like RubyGems can use it easily.

Kev

On 6/30/06, Daniel Berger <Daniel.Berger@qwest.com> wrote:
> Kevin Clark wrote:
> > I'm pleased to announce that tonight marks the first release of mkrf,
> > a library which generates Rakefiles to build C extensions to Ruby and
> > is aimed at a replacement for mkmf. This is a Ruby Summer of Code
> > project (http://code.google.com/soc/ruby/about.html).
> >
> > Though the gem doesn't seem to have propogated yet, it should be
> > availble through rubygems, and until then you can download the gem
> > directly at http://rubyforge.org/frs/download.php/11283/mkrf-0.1.0.gem
> >
> > The code does have RDoc included which I hope explains things well
> > enough. Please do send questions and bug reports my way. I'll have a
> > project setup at advisr.org where you can submit bug reports as soon
> > as I tweak its source to properly scope accounts, but until then email
> > is fine.
> >
> > **Please do try mkrf with your extensions. Please do send feedback.**
> >
> > As for syntax, it can be as simple as:
> >
> >  Mkrf::Generator.new('libtrivial_so.bundle')
> >
> > or more complex:
> >
> >  Mkrf::Generator.new('libxml_so.bundle', '*.c') do |g|
> >    g.include_library('socket','socket')
> >    g.include_header('libxml/xmlversion.h',
> >                     '/opt/include/libxml2',
> >                     '/usr/local/include/libxml2',
> >                     '/usr/include/libxml2')
> >  end
> >
> >
>
> Hm, what's the difference between this and mkmf2?
>
> Thanks,
>
> Dan
>
>
> 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.
>
>


-- 
Kevin Clark
http://glu.ttono.us