From: Cheetah <fa...@gm...> - 2004-12-20 20:09:25
|
On Sun, 19 Dec 2004 18:17:35 +0100 (ora solare Europa occidentale), Mattia Barbon <mat...@li...> wrote: > Hello, > there seems to be quite a lot of interest on this topic :-) > here are the instructions. So, here's what I did, and the results I got: 1) Downloaded the MinGW all-in-one and installed it into the default C:\MinGW 2) Installed ExtUtils-FakeConfig from PPM 3) Followed Mattia's instructions for compiling wxMSW-2.5.3 -- Current MinGW installs make as mignw32-make.exe, so copied that to make.exe to avoid problems -- Because of some weird issues revolving around my usage of the Safe module, I compiled a non-unicode version, even though I'm targeting WinXP [1] < wait a while for wxMSW-2.5.3 to compile > -- The makefile.gcc for stc is in $WXDIR\contrib\build\stc, not in contrib\src\stc < uninstall ppm package of Wx just in case > 4) Downloaded and unpacked Wx-0.21 5) Set environment vars as instructed by Mattia 6) Build Wx -- Setting WXDIR and WXWIN to $WXDIR\build\msw resulted in an error N:\src\Wx-0.21>set WXDIR=N:\src\wxWidgets-2.5.3\build\msw N:\src\Wx-0.21>set WXWIN=N:\src\wxWidgets-2.5.3\build\msw N:\src\Wx-0.21>perl -MConfig_m Makefile.PL chdir 'N:\src\wxWidgets-2.5.3\build\msw\samples\minimal' at N:/src/Wx-0.21/build/Wx/build/Config/Win32_MinGW.pm line 27. I also tried variants of setting one or both of WXDIR/WXWIN to the base wxMSW-2.5.3 unpack dir, but those each gave their own errors. Help? [1] In short, what I've deduced is that character classes and case insensitivy in regexes when working on unicode text requires pulling in numerous support files via require, which I have blocked in my usage of the Safe module. Since all the text I'm working with is plain ascii, I just use a non-unicode build of Wx and this ceases to be a problem. -- -- Cheetah |