Re: question about Perl with Mingw
[email protected] (kmx)
| Newsgroups | perl.win32.vanilla |
|---|---|
| Message-ID | <[email protected]> |
Dne 24.6.2010 23:44, LM napsal(a): > Can I delete the extra mingw compiler downloaded with Strawberry Perl > and simply adjust my path via the command line to point to both the > Strawberry Perl bin directory and the mingw bin directory? > Technically it is possible (you just have to avoid mixing 32/64bit perl and gcc compiler). > Is that all I'd need to do or are there other settings required. > Apart from mingw compiler (gcc toolchain + binutils + C-runtime) you need: 1/ dmake.exe = absolute must 2/ patch.exe, pexports.exe, gmake.exe or mingw32-make.exe (for building some modules from CPAN) 3/ Keep in mind that c:\strawberry\c directory does not contain only gcc compiler but also a bunch of external libraries (libexpat, libgdbm, berkeleydb, libxml2, libxslt, openssl, mysql, postgres, gmp, mpc, mpfr and many others). These libs are needed for building certain perl modules. You can download them separately from http://strawberryperl.com/package/kmx/32_libs Please note that since 5.12 release strawberry uses gcc 4.4.3 toolchain from http://mingw-w64.sf.net project not from http://mingw.org - the main reason was that mingw.org delivers just 32bit compiler whereas mingw-w64.sf.net delivers both 32 and 64bit native gcc compiler. I personally do not see any reason why strawberry should switch back. > MinGW's msys supplies a version of Perl in the msysDTK file and Strawberry > Perl supplies a copy of MinGW. Both of these appear to be older versions. > (I don't think MinGW specifically supplies Strawberry Perl or Vanilla Perl, > but I don't think their Perl distribution is the latest either.) What I > really want is to run the best and latest distributions of both MinGW and > Perl. Is there any way these two projects can get together and work out > supplying later versions of each other's tools? The biggest trouble of mixing MSYS environment with strawberry perl is the fact that MSYS environment is using UNIX-like paths like /usr/local/whatever which are not understood by strawberry perl (from obvious reasons). Of course you can even in MSYS environment use paths like c:/dirname/subdir which strawberry can handle but strawberry simply is not 100% replacement of perl delivered with MSYS. -- kmx