Front page | perl.wxperl.users |
Postings from June 2011
From: Ahmad Zawawi
June 13, 2011 06:52
Message ID: BANLkTinRn0QvFM3iwyH7s98ZW_nXRd-7Xw@mail.gmail.com
Oops forgot to CC the wxPerl users list :)
---------- Forwarded message ----------
From: Ahmad Zawawi <email@example.com>
Date: Mon, Jun 13, 2011 at 4:40 PM
Subject: Re: Alien::wxWidgets questions
To: Mark Dootson <firstname.lastname@example.org>
Thanks for the quick reply :)
> I use mingw-w64 32 and 64 bit gcc compilers to build against all current
> versions of ActivePerl. A recent gcc from mingw.org works too.
I was referring the broken ActivePerl PPM gcc + dmake support. The one
you get when you run cpan Alien::wxWidgets (after a fresh ActivePerl
installation) and it tells you that it cannot find a working compiler
and it downloads the one from ActiveState PPM repository. I will post
the exact log if you are interested. VC++ CL is not registered in PATH
unless you explicity call "%VS_STUDIO_HOME%\VC\bin\vcvars32.bat"
> Occasionally, in the past, a particular release of ActivePerl broke gcc
> compatibility, though I can't remember the last one. (one of the 5.10.1
> For this reason I'm in the habit of still using ExtUtils::FakeConfig,
> creating my own libperl5xx.a and loading a Config_w64.pm
> ( http://www.wxperl.co.uk/building/Config_w64.pm )
>> - What are the supported Alien::wxWidgets configurations of over
>> Linux, Mac OS X and other platforms?
> Not sure what you mean?
Alien::wxWidgets compiler / platforms tested support matrix. For example:
On Linux, Alien::wxWidgets links to libs or from source. Supports only gcc?
On win32, gcc or VC++ cl (ActivePerl). Only gcc on strawberry and Cygwin.
On Mac, only gcc also?
>> - How can one could 'require Alien::wxWidgets;' and then call
>> Alien::wxWidgets->compiler without a 'use Alien::wxWidgets' it?
>> Please note that I am asking about the supported configurations to
>> develop a proper Wx::Scintilla test plan. Hopefully, I will get more
>> tester reports for Wx::Scintilla on different platforms.
>> P.S. I need PAUSE *co-maintainer permission* on Wx::Event so I can
>> extend it without the PAUSE indexer complaints.
> you can also defeat indexer by splitting the package line
Fixed in 0.09. Thanks for the tip :)
> alternatively, you can add your events in your XS code - which may be the
> preferred way for new stuff. See Wx source
Thanks, I will take a look at it.
> Hope it helps.
It helped a lot.
Ahmad M. Zawawi