David,
I had exactly the same problem. It turns out in my case the problem
is that the new version of ExtUtils::ParseXS is being installed into /
Library/Perl rather than /Library/Perl/Updates and since the @INC
search path is /Library/Perl/Updates, then /System/Library/Perl (where
the ol
Hello,
till today I was using PerlApp to compile my wxPerl application without
a problem.
I had to reinstall perl (ActiveState latest build) and cannot get it
going since then.
I installed all the latest modules from www.wxperl.co.uk.
First I noticed that Wx::Perl::Packager no longer contai
Hi,
The PDK "error: Can't locate Wx\Loader\Custom.pm" is fine and expected.
You can ignore it.
wxpdk is not needed anymore (since PerlApp 7.1)
I have tested
ActivePerl 5.10 build 1007
Wx 0.9701
Wx::Perl::Packager 0.20
PerlApp 7.3
And all seems to work OK ?
What is your version of ActivePer
Hi,
I have the same configuration (Windows 7) and the test script compiles
and runs fine.
Hm, maybe it is not a Wx problem?
Till today I had no problem to compile and run my program. Today I
suddenly could not run perl at all (side by side configuration error).
I went to update my perl inst
Hi,
On 02/03/2010 17:54, Jiří Pavlovský wrote:
One more thing: I forgot to tell that with the ppm package from
www.wxperl.co.uk I could not run my prog at all.
Error was missing wxbase28u_vc_custom.dll (IIRC).
That I resolved by replacing Alien-wxWidgets-gcc-0.50.4 with
Alien-wxWidgets0.50.
On Tue, 02 Mar 2010, Mark Dootson wrote:
> The ActivePerl PPM did not pick up the new package.xml from the
> repository (or at least decided it was unchanged). This, despite me
> reinstalling to a completely fresh location. Clearly, 'uninstall' leaves
> stuff hanging around. I had to disable the w
Hello,
I found the problem. I was using wxGlade to create my Dialogs. It puts 2
'use Wx' lines. Like below.
use Wx 0.15 qw[:allclasses];
use strict;
package Wx::SelectRequestedTranslation;
use Wx qw[:everything];
use base qw(Wx::Dialog);
Removing the first line solved the problem.
On 2.3
On Mon, 2010-03-01 at 18:46 -0800, Kyle McKay wrote:
> David,
>
> I had exactly the same problem. It turns out in my case the problem
> is that the new version of ExtUtils::ParseXS is being installed into /
> Library/Perl rather than /Library/Perl/Updates and since the @INC
> search path is
On 02/03/2010 18:52, Jan Dubois wrote:
You should be able to force a package.xml update with:
ppm repo sync --force wxperl
Nice tip. I really ought to read the docs more often.
Neither do I. Every now and then I try to figure this out, but always run
out of time before I get things
On 03/03/2010 05:25, Mark Dootson wrote:
sit typing makefile parameters for 4 architectures - or be left with the
impression that there is any magic in the build process that goes beyond
parameters to perl Makefile.PL and perl Build.PL.
oops - I forgot the ExtUtils::FakeConfig fix for MacOSX.
10 matches
Mail list logo
