in reply to Re^5: Disappointed with latest Strawberry Perl
in thread Disappointed with latest Strawberry Perl

Nothing is wrong with Tk :) It just needs an extra argument on the initial Makefile.PL command line.

Maybe that could be addressed with CPAN.pm's new support for "distroprefs". That should be able to automatically add the necessary keyword on Win32.

The part I miss most is libexpat, so I cannot install any XML stuff. Maybe OpenSSL is second.

I agree. Alias and I disagree about the extent of bundling things. I'd just as soon throw in a kitchen sink of libraries (e.g. most of the libraries in GnuWin32) but he prefers a more spare distribution. Once the new tools are documented, I may take a swing at a more full-featured distribution and we can let users decide.

In the meantime, there are some ways to get expat, etc. support working:

I have also downloaded and compiled OpenSSL in C:\OpenSSL. As I recall, Net::SSLeay found it there but failed some tests (apparently unrelated to the library itself). I forced the install and was able to go on to install and use IO::Socket::SSL, etc. So it takes a bit of work, but can be made to work with Strawberry if you're not afraid of the compiler.

-xdg

Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.

  • Comment on Re^6: Disappointed with latest Strawberry Perl

Replies are listed 'Best First'.
Re^7: Disappointed with latest Strawberry Perl
by eserte (Deacon) on Dec 30, 2007 at 17:28 UTC
    Nothing is wrong with Tk :) It just needs an extra argument on the initial Makefile.PL command line.
    Maybe that could be addressed with CPAN.pm's new support for "distroprefs". That should be able to automatically add the necessary keyword on Win32.
    Tk should normally build without any additional arguments. Something else went wrong here.

    As for expat/XML::Parser, maybe an Alien::expat module would solve the problems: easy installation of XML::Parser, and keeping the Strawberry Perl distribution small.

      I have no experience with building Tk in a windows-only environment, because I always use Cygwin, with full X11 installed, and ActivePerl comes with Tk bundled, so I have no need to build myself. As Strawberry obviously is a similar build to ASperl ($^O - wise that is), adding MSWin32 can do no harm.

      Anyway, by now I really hate the title of this thread, as I value Strawberry more and more with every experience. It is all doable. At least for me. I'm just sharing my experiences here hoping the product will get even better with the next build.

      I can understand your point of seeing Tk as bloat to Strawberry, and if the new CPAN option solves that, I would not miss it, as building it with cpan then will yield no additional problems.

      Is there any reason why the install path for Strawberry is fixed at C:\Strawberry? I have those utils at D: normally, and I can imagine a network share as install path so all can share it's beauty without having to install it.


      Enjoy, Have FUN! H.Merijn

        It's only the path where the installer insists on putting Strawberry Perl. You can (after "installation") simply move the directory and patch Config.pm and Config_heavy.pl and CPAN/Config.pm to point to the new directory. I think the fixed installation mostly stems from some weird belief that executables (and especially Perl) are not relocatable by default on Win32.

        You will of course need to change $ENV{INCLUDE}, $ENV{LIB} and $ENV{PATH} to reflect the new location as well, but as you're setting up your own environment anyway, that should be no problem either.

Re^7: Disappointed with latest Strawberry Perl
by adamk (Chaplain) on Jan 03, 2008 at 00:23 UTC
    I absolutely want Expat bundled by default in Strawberry.

    It's just that I couldn't get an automated build working within the time available for the Strawberry 5.10.0 release.

    I either got a working version that had to like C:\Expat (not acceptable) or a broken build that would live in the correct place (in $DISTROOT\\c\\).

    As soon as someone can build me a working version and provide a Perl::Dist-compatible tarball for it, I'll add it immediately.
How to get expat and XML::Parser running on Strawberry Perl
by davebaker (Pilgrim) on Mar 15, 2008 at 19:49 UTC