in reply to Error with Padre at ActivePerl

I just installed Padre earlier this week on a Win7 x64 system that had ActivePerl version 5.12.1 (32-bit) installed.

Basically, I followed the steps listed here, but with the GUI interface to PPM. The basic steps were: 1) add the wxperl repository, 2) install Alien-wxWidgets, 3) install Wx, and 4) install Padre.

If I remember correctly, one or more of the modules (Alien-wxWidgets, Wx) was also available from ActiveState's repository. When I tried that version first, the Padre install failed. After uninstalling that module and installing the one from the wxperl repository, I had no issues installing Padre. In other words, I'd recommend installing all 3 of those modules from the wxperl repository.

I'm not sure if this information would help you, but thought I'd share the steps that I went through on a very similar setup to yours.

Also, if you look at the very bottom of that link that I provided, there's a link on how to contact the Padre folks for more assistance.

Replies are listed 'Best First'.
Re^2: Error with Padre at ActivePerl
by Anonymous Monk on Feb 04, 2012 at 10:04 UTC

    This is good advice :) if you're gonna get Wx, get it all from the same place

    wxWidgets can be compiled about eleventeen different ways ( with/without unicode, debug, ... ) and any ppm of Wx you might install , is linked to a particular build of Alien::wxWidgets (platform, 32/64-bit, compiler)

    So from the aforementioned uk repository, Wx.dll would look for 

    blib\arch\Alien\wxWidgets\msw_2_8_12_uni_gcc_3_4\lib
...\wxbase28u_gcc_wxp_binary_14_0.dll
...\wxbase28u_net_gcc_wxp_binary_14_0.dll
...\wxbase28u_xml_gcc_wxp_binary_14_0.dll

    [download]

    msw means microsoft windows, 2.8 or 2.8.12 is wxWidgets version, gcc 3.4 is version of compiler, 28u indicates unicode version of 2.8 wxwidgets

[reply]
[d/l]
Re^2: Error with Padre at ActivePerl
by HelenCr (Monk) on Feb 05, 2012 at 01:38 UTC
    Thank you, dasgar. That was exactly the problem. In the meantime independently, I hit upon this advice:
    https://groups.google.com/group/binary-wxperl/browse_thread/thread/f53be0143430f408?hl=en# (see the answer, second post), (which is identical to what you're saying) and it fixed the problem. (Namely, removing some wx- related packages which originated from the ActiveState repository, and installing packages with the same name originating from the wxPerl repository).
[reply]

In Section Seekers of Perl Wisdom