I add a new target 'setup' in the main Makefile.
That's allow the creation of a setup-parrot-x.y.z.exe ('standard' binary
distribution) that contains all parrot install directories and the ICU
shared libraries.
A new script tools/dev/mk_setup.pl creates a script 'parrot.iss' for Inno
Setup .
Inno Setup is a free installer for Windows programs. See
http://www.jrsoftware.org/
François Perrad.
> I add a new target 'setup' in the main Makefile.
> That's allow the creation of a setup-parrot-x.y.z.exe ('standard' binary
> distribution) that contains all parrot install directories and the ICU
> shared libraries.
Shouldn't that better read:
make win32-setup
Just "setup" seems to be to general, IMHO. Or does the term "setup"
apply to Win32 only and all the time - like "make rpm" to a different
category of OS?
leo
Or even:
nmake win32-installer
?
The Windows equivalent of "rpm" would be "msi".
Cf http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx
Ron
> Or even:
> nmake win32-installer
> ?
> The Windows equivalent of "rpm" would be "msi".
Maybe then:
nmake win32-inno-installer
nmake win32-msi-installer
...
(which make the win32 prefix rather superfluent)
> Ron
leo
I think we should only pick one installer, and stick with it. There
is no benefit I can think of having multiple installers (anyone?). I
guess it would only confuse people.
Ron
Francois.
> nmake win32-msi-installer
> ...
>
>(which make the win32 prefix rather superfluent)
>
> > Ron
>
>leo
I rename too the new script to mk_inno.pl
Francois
>Thanks,
>leo
>
>
> I rename too the new script to mk_inno.pl
Sorry for bothering you again. But with the recent ICU changes,
installing any ICU stuff is obsolete. ICU will be removed from the
source tree soon (when we switch to SVN).
> Francois
Thanks,
leo
Thanks, applied.
leo