Hi, > Tuesday, August 5, 2003, 12:28:16 AM, you wrote: > > JW> What needs to go into the ZIP? My guesses are:- > JW> - parrot executable > JW> - imcc executable > JW> - The docs directory > JW> - The examples directory > JW> - The languages directory > JW> If you want regular (weekly? bi-weekly?) builds on Win32 zipping up and > JW> FTPing somewhere, I can do that for you. > > well, I am not sure, what the due content should be, but it would be > really good, and not just for me! If others agree and let me know what should go in there, I'll do my best to 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 at all, as people can just get the latest CVS snapshot and Configure, n?make, etc.
> Guys, sitting at Perl you do a great > work for all dynamic languages. If you could make your first pages on > web more comprehensive for other non-PERLers then you could obtain > some help from outside I guess. I think I heard something a while back to the effect that the parrot site was being updated sometime soon, but I'm not sure. > JW> FYI, current test status on Win32:- > > ?! > > under cygwin? > > JW> Don't know if this is supposed to happen (I don't recall seeing it before), > JW> but I'm seeing this many times during the nmake proccess:- > JW> Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 > JW> Copyright (C) Microsoft Corp 1988-1998. All rights reserved. > JW> cd classes && NMAKE && cd .. > > or using cl.exe/MSVC ? Using nmake/cl, etc. Not cygwin, I haven't tried it in that, though I *think* someone mentioned having parrot running successfully under cygwin on the list at some point. > "nmake" sounds quite strange with ultimate goal of portability, but > anyway. AFAIK, the makefiles that are generated from Configure can (theoretically) work with nmake or whatever make program you have on the target platform, so I don't see a portability problem. I may be completely wrong though! Jonathan
