On Tuesday, August 05 at 2003 2:40 PM, Dan Sugalski wrote:
> At 12:12 AM -0400 8/5/03, Melvin Smith wrote:
> >At 11:37 PM 8/4/2003 -0400, Brent Dax wrote:
> >>Jonathan Worthington:
> >>> work something out. :-) However, Brent said "If you mean
precompiled
> >>> binaries, not yet. Parrot is still under development, so we aren't
> >>shipping
> >>> binaries.", so I'm guessing maybe I shouldn't do a ZIP with the
> >>executables
> >>> in? But in that case I guess there's no point me doing anything like
that
> >>
> >>I wasn't saying "we shouldn't do it", I was saying that "at this point
in
> >>the development cycle we aren't doing it." I have neither the authority
nor
> >>the knowledge to set that kind of policy.
> >>
> >>Translation: if Dan doesn't say otherwise, go ahead--it's not my call
> >>anyway. :^)
> >
> >Dan is usually very happy when people volunteer to do things.
> >I would expect everyone would be happy if someone built
> >a Win32 distro. All that would be required of it is to pass the same
> >set of tests as the reference compile, if there is one.
>
> And this would be one of those cases. :) I'd be happy if someone with
> a Win32 box could make regular snapshot builds. (If I had a spare x86
> box I would, but alas I don't) There certainly are enough people
> who'd like to play with Parrot but not mess around with C and, while
> that's possible on most Unix platforms (since you get a C compiler
> whether you like it or not) it isn't on Windows.
OK, I'll go ahead and put something together. Thanks for everyone's
thoughts on this, and I hope my efforts will be helpful.
> If someone wanted to take a look at the "make install" target as they
> did this (yes, we do have one :) to make sure that what it provides
> is sufficient, well, that'd be cool too.
In dev/tools/install_files.pl, I suspect the problem is in these lines:-
my %options = ( buildprefix => '',
prefix => '/usr',
exec_prefix => '/usr',
bindir => '/usr/bin',
libdir => '/usr/lib',
includedir => '/usr/include',
);
Is it as simple as checking whether the OS is Windows, and setting %options
to contain appropriate paths, e.g.
%options = ( buildprefix => '',
prefix => 'c:\parrot',
exec_prefix => 'c:\parrot',
bindir => 'c:\parrot\bin',
libdir => 'c:\parrot\lib',
includedir => 'c:\parrot\include',
);
As these directories may not exist in Windows, and I don't see anything that
creates non-existent directories, I believe I'll need to write something
that checks if they are there and creates them if they are not.
I'll put together a patch for this later tonight, unless anyone tells me I'm
on the wrong track before I get round to it. :-)
Jonathan
