Thank you Mark,
After moving padre, padre.exe and padre.bat in the perl/bin directory the
editor works if I start it with padre.exe.
It doesn't work if I execute padre.bat.
I have tried to install it using cpan after installing it with ppm (for
installing its dependencies) and after I removed it with `ppm remove Padre`,
but I still can't install it with cpan. It gives some strange and unclear
errors.
--
Octavian
----- Original Message -----
From: "Mark Dootson" <mark.doot...@znix.com>
To: "Octavian Rasnita" <orasn...@gmail.com>
Cc: <wxperl-users@perl.org>
Sent: Tuesday, April 27, 2010 2:32 AM
Subject: Re: Padre can't be installed from WxPerl repository?
Hi,
I think that's an issue with Padre 0.56 as installed by PPM.
The command
padre.bat
should work. Alternatively, you could move padre.exe, padre.pl and
padre.bat from ..perl\site\bin to ..\perl\bin
One thing you might like to try. I think that as you will now have most of
the pre-requisites installed, if you have a compiler I don't see why
cpan Padre
would not work for you. It might be an idea to uninstall the Padre PPM
first.
Regards
Mark
On 26/04/2010 20:51, Octavian Rasnita wrote:
Hi Mark,
From: "Mark Dootson"<mark.doot...@znix.com>
Hi,
I tested ActivePerl 1007 Padre install and it seemed to work OK.
Perhaps the repository needs re-sync
ppm repo sync --force wxperl
ppm s Padre
Regards
Mark
Thank you. I was able to install Padre.
Unfortunately when I try to run it, it displays the following error
window:
Padre
Cannot find 'WPerl.exe'!
OK
There is no "WPerl.exe", but there is "wperl.exe" in the bin directory of
ActivePerl and I guess it should work because under Windows the case
differences shouldn't matter.
Do you have any idea what could be the problem? Padre? ActivePerl?
Thanks.
Octavian
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 5063 (20100426) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
__________ Information from ESET NOD32 Antivirus, version of virus signature
database 5064 (20100427) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
