antilogoboss

• Install Padwalker Eclipse Windows

I often work with IBM/Rational's Clearquest product writing scripts. Clearquest uses a specialized version of Perl called cqperl (Don't ask - I don't like it but am stuck with it). I'd like to use EPIC to develop and debug cqperl scripts. Cqperl is an ActiveState based perl that uses some special libraries.When I attempt to use the debugger I get an error stating:Error displaying local variablesInstall PadWalker and restart Eclipse or disable display of local variables.I also see:Bareword found where operator expected at D:/Profiles/p6258c/workspace/.metadata/.plugins/org.epic.debug/epicbreakpoints.pm line 49, near '$DB::OUT abspath'(Missing operator before abspath?)Default die handler restored.Trouble is I don't have PadWalker nor do I have ppm with which to install it. IBM/Rational gives you an ActiveState based, specialize Perl called cqperl but does not give you tools to install additional Perl CPAN modules into it's perl.Is there a way to get ppm and PadWalker to install into this beast or am i just out of luck?

You can build PadWalker in your area and add it in the include path. Go to cpan.org. Download the latest PadWalker and build it. If you are in Windows environment then you will need to install 'cmake' and its dependencies first. When you build PadWalker it will create objects in blib directory, copy the objects under 'arch' and 'lib' directory to some directory and add that directory in your include path.Or if you have install/Admin permission use 'make install' to install it to the perl lib installation location.

Well I didn't get that far. First off, I don't really need Unix utilities as I have Cygwin. But I know that Cygwin will build things with POSIX paths and that'll probably not be good so I downloaded UnxUtils and unpacked it. What am I supposed to do with it then?I also downloaded the nmake thing but it says to install it into your C:Perlbin directory. I don't have a C:Perlbin directory because I don't have ActiveState Perl. I have Rational's cqperl which is a derivative of ActiveState Perl so I put nmake into C:Program FilesRationalClearquest - where cqperl.exe resides.Moving onward, I download PadWalker and unpacked it then did cqperl Makefile.PL and got:Perl v5.8.2 required-this is only v5.6.1, stopped at Makefile.PL line 4.What next? Well I removed the require and tried a cqperl Makefile.PL again and received:Checking if your kit is complete.Looks good'NOMETA' is not a known MakeMaker parameter name.Error: Unable to locate installed Perl libraries or Perl source code.It is recommended that you install perl in a standard location beforebuilding extensions.

Some precompiled versions of perl do not containthese header files, so you cannot build extensions. In such a case,please build and install your perl from a fresh perl distribution. Itusually solves this kind of problem.(You get this message, because MakeMaker could not find 'publicrationalcommonlibperl55.6.1MSWin32-x86-multi-threadCOREperl.h')Again, i don't know how to use UnxUtils nor nmake to build this. I assume I need to use cqperl and keep Windows style paths and the like. I mean I could try building this under Cygwin but that would probably embed POSIX paths which would not work with cqperl, which is decidedly Windows like and will not like POSIX paths.

If cqperl is based on 5.6.x, the debugger backend it is not compatible with the EPIC frontend, so don't try to use them together unless you are ready to modify Java code. If it is based on 5.8.x or 5.10.x, then it may be worth trying to copy the binary PadWalker files from a matching ActiveState Perl distribution to their expected locations./html/site/lib/PadWalker.html./site/lib/auto/PadWalker./site/lib/auto/PadWalker/PadWalker.bs./site/lib/auto/PadWalker/PadWalker.dll./site/lib/auto/PadWalker/PadWalker.exp./site/lib/auto/PadWalker/PadWalker.lib./site/lib/auto/PadWalker/PadWalker.pdb./site/lib/PadWalker.pm. EPIC communicates with the perl5db.pl debugger back-end extracted from your Perl installation and patched with one line to interface with the 'epicbreakpoints.pm' module. EPIC retrieves the back-end's current state, adds/removes breakpoints (dynamically, when source files are loaded by the back-end) and obtains values of variables on each suspend. It basically emulates what the user would type in the command-line debugger and parses the output. You can see this communication if you enable the 'debugger console' in EPIC preferences. It is likely that some commands and/or output strings have changed since 5.6.

The helper modules that rely on PadWalker or introspection to display values may need to be understood and updated also.If you are interested, follow the instructions at to create a development environment. Then, install breakpoints at interesting locations in the org.epic.debug plug-in (particularly the DebuggerInterface class and friends). Also, print-to-file logging statements in the.pm files contained in that plug-in are useful to understand how they work. There is also javadoc on the Java side and POD regarding the variable dump syntax.It's hard to tell to what extent the current (that is, 'testing', CVS HEAD) front-end is incompatible with 5.6. It just hasn't been tried yet, could be anything from changing a few constants to hacking PadWalker.

Install Padwalker Eclipse Windows

.EclipseBefore installing the EPIC plug-in Eclipse version 3.6 (for EPIC 'stable') or version 3.7 or higher (for EPIC 'testing') has tobe installed. Eclipse can be downloaded from.Eclipse is distributed in several flavors which differ in theirpre-installed set of plug-ins. Because EPIC has a very modest ofdependencies, you are free to pick any flavor of Eclipse you like.We develop and test EPIC using the 'Eclipse IDE for Java Developers' flavor.Eclipse does not include a Java runtime environment (JRE).

You willneed a 1.6 (for EPIC 'stable') or 1.8 (for EPIC 'testing') level or higher Java runtime or Java development kit (JDK)installed on your machine in order to run Eclipse. If you are on Linux,do not use the gcj version of Java, which is preconfigured in somedistributions (e.g. Instead, install the Java implementationfrom Oracle. (gcj is known to cause slowdowns in the editor and problemswith displaying variables in the debugger.)PerlIn order to have all EPIC features like Syntax Checking, Source Formattingetc. A Perl interpreter is needed. In principle any Perl interpretercan be used. EPIC works with the following versions of Perl: 5.20.x, 5.10.x,5.8.x and 5.6.x (no longer tested and not recommended).

Perl 5.26 is alsosupported since 0.7.5 release of EPIC.Most.nix/Linux installations will provide Perl interpreters out of thebox. For Windows, we recommend.The Cygwin distribution of Perl is also supported. PadWalkerIf you wish to use the debugger, make sure that the Perl module PadWalker,version 1.0 or later, is installed as part of your Perl distribution.EPIC is unable to display values of local variables without PadWalkerand will tell you so. The preferred way to install PadWalker is byusing either your Linux distribution's package manager or, under Windows,using ActiveState'stool. For ActivePerl 5.10.x, a version of PadWalker installablewith PPM might not be available in the standard repository, but is providedin therepository. Of course, you can also install PadWalker directly fromCPAN, but this requires a working C compiler on your system. Considerations when using CygwinMake sure that the mount command is available and that it is in yoursystem path.

Download the latest drivers for your Compaq EVO N800c to keep your Computer up-to-date.

As mount is a standard component of Cygwin this usuallyonly have to add the cygwinbin directory to your system path.A recent release of PathTools (part of Perl distribution, file Cwd.pm) unfortunately containsa which breaksEPIC's debugger frontend. The specific symptom is the error message 'perl5db.pl did notreturn a true value.' - to see this message, you should enable the 'debugger console' in EPICPreferences. Furthermore, if you have this problem, debugging doesn't work at all.To fix it, you must edit Cwd.pm of your Perldistribution and remove the offending 'eval' keyword from one line,as described in.DO NOT attempt to fix it by adding Perl's 'lib' directory to your project'sinclude path, as this will cause all breakpoints to be ignored!The autocompletion suggestions will pop up automatically after you havetyped a trigger character.

Triggers are ':' and '.