Hi Mark, Nope, neither of those 2 commands work:
E:\usr\site\bin>perl padre E:\usr\site\bin>perl e:\usr\site\bin\padre E:\usr\site\bin>e:\usr\site\bin\padre.bat Using padre.exe works though, but I need to be able to run `perl padre` in order to be able to test some changes. Thanks. Octavian ----- Original Message ----- From: "Mark Dootson" <mark.doot...@znix.com> To: <padre-dev@perlide.org> Sent: Saturday, December 11, 2010 1:46 AM Subject: Re: [Padre-dev] Padre 0.76 Released > Octavian, > > Assuming ActivePerl is at C:\Perl > > then either > > perl C:\Perl\site\bin\Padre > > or > > C:\Perl\site\bin\Padre.bat > > should work for you? > > There should be three files installed in C:\Perl\site\bin > > Padre the perl script to run Padre > Padre.bat the above wrapped in a batch file > Padre.exe executable that runs the Padre script > > Regards > > Mark > > > > > On 10/12/2010 22:14, Octavian Rasnita wrote: >> Hi, >> >> I have commented the lines that check for Alien::wxWIDGETS and I was able to >> create the Makefile. >> >> On `nmake test` it gave just asingle error: >> >> t/44-perl-syntax.t ......... 23/73 >> # Failed test 'message match in 'Trivially broken package statement'' >> # at t/44-perl-syntax.t line 199. >> # got: 'syntax error' >> # expected: 'syntax error, near "package;"' >> t/44-perl-syntax.t ......... 68/73 # Looks like you failed 1 test of 73. >> t/44-perl-syntax.t ......... Dubious, test returned 1 (wstat 256, 0x100) >> >> Yes it would be very nice if the Padre builder would not check for wxWIDGETS >> and if it could be used to build Padre with ActivePerl also. >> >> BTW, do you know why Padre can't be started by running the program "padre" >> with perl? >> I want to try some changes/improvements, but I can't test the program and >> the possible errors it gives if I can't run its source code. >> >> Thanks. >> >> Octavian >> >> ----- Original Message ----- >> From: "Mark Dootson"<mark.doot...@znix.com> >> To:<padre-dev@perlide.org> >> Sent: Friday, December 10, 2010 10:05 PM >> Subject: Re: [Padre-dev] Padre 0.76 Released >> >> >>> Hi, >>> >>> As far as I can tell, Octavian's output suggests that the first compiler >>> found on the path is 'cl'. There's nothing to suggest that gcc is installed. >>> The problem is that Padre's Makefile.PL loads Alien::wxWidgets. >>> Alien::wxWidgets tells you it can't find a compiler compatible >>> installation any of the configurations it has found. This info is >>> irrelevant for Padre. >>> >>> The fix for Padre is to check Wx for the wxWidgets version, if that is >>> what's required, not check Alien::wxWidgets for the first compiler >>> compatible configuration (which is probably the version of wxWidgets >>> used to build the Wx you will load, but not absolutely). >>> >>> e.g. Makefile.PL should do: >>> >>> use Wx; >>> my $widgetsversion = Wx::wxVERSION(); >>> >>> For Octavian, you could wait for ppm's to be available which should be >>> within a couple of days. The only delay is waiting for the ActivePerl >>> ppm build process to catch up building a couple of dependencies. >>> >>> In the future, if the Padre Makefile.PL is amended not to load >>> Alien-wxWidgets, you should not have this problem. >>> >>> Hope this helps. >>> >>> Mark >>> >>> >>> >>> >>> >>> >>> >>> On 10/12/2010 19:10, breno wrote: >>>> On Fri, Dec 10, 2010 at 4:06 AM, Octavian Rasnita<orasn...@gmail.com> >>>> wrote: >>>>> Hi, >>>>> >>>>> I have tried: >>>>> >>>>> E:\padre\Padre-0.76\Padre-0.76>perl Makefile.PL >>>>> compilet-588840960.c >>>>> Creating library C:\DOCUME~1\Octavian\LOCALS~1\Temp\compilet.lib and >>>>> object C:\DOCUME~1\Octavian\LOCALS~1\Temp\compilet.exp >>>>> Searching configuration for: >>>>> wxWidgets (any version) for (any toolkit); compiler compatibility: cl >>>>> (any version); >>>>> Available configurations: >>>>> wxWidgets 2.008011 for msw; compiler compatibility: gcc 3.4; options: no >>>>> debug, unicode, no mslu >>>>> BEGIN failed--compilation aborted at Makefile.PL line 49. >>>>> E:\padre\Padre-0.76\Padre-0.76> >>>>> >>>>> >>>>> Can you please tell me what is missing? >>>>> I use ActivePerl 5.10.1 under Windows XP with Wx 0.98. >>>>> >>>> >>>> Hi Octavian, >>>> >>>> unfortunately I believe most of us use Strawberry Perl on Windows, not >>>> Active Perl. >>>> >>>> In order do build Padre from source using Active Perl you'll probably >>>> need some external dependencies. For example, I see you have "gcc" >>>> instead of "cl" >>>> (http://msdn.microsoft.com/en-us/library/9s7c9wdw%28VS.71%29.aspx), >>>> and this might be the reason of the build failure. I would suggest one >>>> of the following: >>>> >>>> * install "cl" and try again; OR >>>> * remove Active Perl and install the latest Strawberry Perl, then >>>> type "cpan Padre" on the prompt; OR >>>> * wait for Padre 0.76 to be packaged for Active Perl, then install via >>>> ppm. >>>> >>>> >>>> Good luck! >>>> >>>> breno >>>> _______________________________________________ >>>> Padre-dev mailing list >>>> Padre-dev@perlide.org >>>> http://mail.perlide.org/mailman/listinfo/padre-dev >>> >>> _______________________________________________ >>> Padre-dev mailing list >>> Padre-dev@perlide.org >>> http://mail.perlide.org/mailman/listinfo/padre-dev >> _______________________________________________ >> Padre-dev mailing list >> Padre-dev@perlide.org >> http://mail.perlide.org/mailman/listinfo/padre-dev > > _______________________________________________ > Padre-dev mailing list > Padre-dev@perlide.org > http://mail.perlide.org/mailman/listinfo/padre-dev _______________________________________________ Padre-dev mailing list Padre-dev@perlide.org http://mail.perlide.org/mailman/listinfo/padre-dev