On Thu, Apr 4, 2013 at 2:07 PM, Mark Dootson <mark.doot...@znix.com> wrote:
> Google harder :-) Are you referring to this thread? http://www.nntp.perl.org/group/perl.wxperl.users/2012/02/msg8353.html If so, I should have mentioned I had read it. I had also read this thread: http://www.nntp.perl.org/group/perl.wxperl.users/2012/08/msg8492.html > Without seeing your full build output, this is a bit of a stab in the dark, > but I'll guess you built and installed your own wxWidgets or are using the > system installed wxWidgets? Please forgive my unintentional obtuseness. Next time I will post a link to my CPAN Testers fail report. That said, your instincts were spot-on. I was using the MacPorts-provided wxWidgets 2.9.4 (specifically, wxWidgets30 @2.9.4_2+sdl), a remnant of my pre-perlbrew efforts to get Wx working with the MacPorts-provided Perl 5.16.1. Once I uninstalled the port, wxPerl built and tested without issue. Just so we're clear though, wxPerl at this point more or less needs a custom build of wxWidgets 2.9.4, is that correct? Out of curiosity, and I'm sure you've discussed this before, but - in your opinion, are the deficiencies currently present in wxWidgets likely to remain in the future? If so, and maybe this is such an edge case that it's not worth the effort, but would it be useful to alert the user to this condition when they're building Alien::wxWidgets? Is it possible to test an existing wxWidgets installation for the conditions that prevent a successful Wx build (or make test, as the case may be) ? Thanks so much for all your work on this library, Mark, it is much appreciated. -- Wallace Winfrey wwinf...@gmail.com
