From: Curt Hibbs <ml.chibbs@...>
Date: 2006-07-21T08:33:22+09:00
Subject: Re: One-Click Installer: MinGW? or VC2005?

------=_Part_3876_32599230.1153438398438
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Extension authors are free to use Rake if they choose.

Curt


On 7/20/06, Tim Morgan <tmorgan99@gmail.com> wrote:
>
> I was rather hoping the Rake's reach could extend to the be a compelling
> platform for extension authors.  Sort of get into the stream in place of
> mkmf.
>
>
> On 7/20/06, Curt Hibbs <ml.chibbs@gmail.com> wrote:
> >
> > The One-Click Ruby Installer's build process is, in fact, controlled via
> > Rake. However, since the OCI is basically an aggregation of other
> > packages,
> > those packages are built with whatever tool he author of tht package
> used
> > (which is called by the OCI's rake file).
> >
> > Curt
> >
> >
> > On 7/20/06, Tim Morgan <tmorgan99@gmail.com> wrote:
> > >
> > > I was wondering if the toolchain could be built around rake?
> > > rake is Ruby's make, but you make ruby in (n)make?
> > >
> > >
> > > There is one major hole in the build processes for the one-click
> > installer
> > > > that I want to fix along with this compiler transition -- tests for
> > the
> > > > included extensions -- there aren't any. This needs to change. For
> > each
> > > > included extension there needs to be at least a few basic automated
> > > tests
> > > > to
> > > > ensure that the extension is functioning properly. If anyone wants
> to
> > > > volunteer to help with this, please email me (curt at hibbs dot com)
> > and
> > > > I'll hold your name in reserve until I get to that point.
> > > >
> > > > Curt
> > > >
> > > >
> > >
> > >
> >
> >
>
>

------=_Part_3876_32599230.1153438398438--