On Fri, 2002-09-06 at 02:45, Brent Dax wrote:
> So, building Parrot ought to look something like this (for a Windows
> user):
>
> c:\parrot> cd build
> c:\parrot\build> win32
> Are you using MS VC++? [yn] y
>
> Miniparrot build complete.
> Enter 'miniparrot bu
Nicholas Clark:
# On Thu, Sep 05, 2002 at 07:03:00AM -0400, Dan Sugalski wrote:
# > 4) The *only* tools you will need to build parrot are a C compiler
# > environment and either a make tool or a shell
#
# I believe we may be able to get away without a make tool or a shell.
The final build system
On Thu, Sep 05, 2002 at 12:12:52PM +0100, Nicholas Clark wrote:
> On Thu, Sep 05, 2002 at 07:03:00AM -0400, Dan Sugalski wrote:
> > 4) The *only* tools you will need to build parrot are a C compiler
> > environment and either a make tool or a shell
>
> I believe we may be able to get away withou
On Thu, Sep 05, 2002 at 07:03:00AM -0400, Dan Sugalski wrote:
> 4) The *only* tools you will need to build parrot are a C compiler
> environment and either a make tool or a shell
I believe we may be able to get away without a make tool or a shell.
It won't be pretty, but I see no reason why we
I really hadn't planned on going into this now, but the issue's been
raised enough that it can't be left to later. Here's the current set
of long-term goals for Parrot:
1) We *will* run Perl 6, Perl 5, Ruby, Python, JVM bytecode, and .NET
bytecode. Not necessarily in that order
2) [EMAIL PROT
