From 96d0bc0313ca8a2e986f9bdfb09455460c796f1f Mon Sep 17 00:00:00 2001 From: Steve Mynott Date: Fri, 21 Jul 2017 13:47:43 +0100 Subject: more docs for Strawberry Perl type Windows build --- tools/star/windows-msi.pod | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/tools/star/windows-msi.pod b/tools/star/windows-msi.pod index dae1783..b3a9178 100644 --- a/tools/star/windows-msi.pod +++ b/tools/star/windows-msi.pod @@ -39,6 +39,10 @@ Visual C++ Express for version 2010 or perhaps newer. Finally, install the Windows Software Development Kit (SDK) for your Windows version. +An alternative to ActivePerl and the Microsoft toolchain is to use Strawberry +Perl which ships with GCC and a mingw toolchain. Run these tools under cmd.exe +and replace all following references to "nmake" by "gmake". + =item 1. Make sure there is no C:\rakudo directory, as this will be our installation @@ -83,7 +87,7 @@ Finally create the MSI package. nmake msi -(Note if you are using Strawberry Perl's GCC use 'build_msi') +(Note if you are using Strawberry Perl's GCC use 'build_msi' at this point) Depending on your architecture you either rename that msi to: @@ -103,6 +107,10 @@ created installer, and do some sanity tests: zef list --installed zef install Inline +If you are using Strawberry Perl then move its directory temporarily to a +different name in order to check all DDLs are correctly installed in the +C:\rakudo folder. + =item 8. Stop the release process if step 7 failed. Post any issues to the irc channel -- cgit v1.1