Komodo integrates with ActiveState's
Perl
Dev Kit (PDK), a set of tools for building executable programs, ActiveX
controls and Windows services in Perl.
Perl Dev Kit 6.X
Users of the Perl Dev Kit 6.x can access PDK tools via the Tools
menu (Tools|Perl Dev Kit) or the
Perl Dev Kit Toolbar. The
VBScript Converter, Filter Builder and Visual Package Manager options are
displayed by default. The other options (described below) are only available
if a Perl file is open in the Editor Pane. Select the feature from the menu,
or click the toolbar, to launch a graphical user interface for the chosen PDK
tool. Users who prefer to access the PDK tools using Komodo's Build
Standalone Perl Application feature can still do so. When you select
Tools|Build Standalone Perl Application, Komodo displays a
message advising that GUI versions of the tools are available. Click
OK to ignore the message and open the Build Standalone Perl
Application dialog box. The options contained in this dialog box are described
later in this document.
Perl Dev Kit 3.1 to 5.X
If you have an earlier version of the PDK, many of the same PDK
features are available through the Build Standalone Perl Application dialog box.
With a Perl script open in Komodo's Editor Pane, select Tools|Build
Standalone Perl Application to configure the Perl application.
The Build Standalone Perl Application dialog box opens, providing access to the
core PDK tools from within Komodo.
Use the following PDK tools to build executable programs, ActiveX
controls and Windows services.
- PerlApp - Build an executable file from Perl scripts.
- PerlCtrl - Build Active X controls from Perl scripts.
- PerlNET - Create Perl components and applications that are
compliant with Microsoft's .NET Framework.
- PerlSvc - Convert Perl programs to Windows services.
- PerlTray - Write system tray applications in Perl.
Note: On Linux, only the PerlApp tool is supported.
For complete instructions on building executables, controls and services in Perl,
view the
Perl Dev Kit User
Guide on ASPN, the ActiveState Programmer Network.
As you configure options using the Build Standalone Perl Application
dialog box, corresponding command-line strings are displayed in the pane at the
bottom of the dialog box. Command-line options for PerlApp, PerlCtrl, PerlSvc,
PerlNET and PerlTray are described in the
user guide
that accompanies the PDK.
Note: When using the Build Standalone Application
feature with Perl 5.8.0 on a Linux installation where the environment is set to
use UTF-8, you must add the module 'utf8' on the Modules tab.
This is the equivalent of perlapp --add utf8 . The module is not
required for Perl 5.8.1 or higher.
After configuring options using the tabs in the Build Standalone Perl
Application dialog box, use the buttons at the bottom of the dialog box to
create a build, add a script to the
Toolbox,
or debug a script in Komodo.
- Add to Toolbox - Once you have created a new script, click
this button to add it to the Toolbox as a run command.
- Build - Create a new build or overwrite
an existing build.
- Debug - If the Komodo debugging option is selected on the
General tab, click this button to start the
debugger.
|
|
The build options for the Perl Dev Kit correspond with the
tools described in the
Perl Dev Kit documentation,
which contains detailed instructions on configuring Perl executables, services and controls.
- Enter the name of the script to build using the PDK - Specify
the path and filename of the source Perl script. This option is equivalent to
the
-script command-line argument.
- Build the script using - Select the type of output to
generate.
- Enter the name of the target executable or control - Specify
the path and name of the output file. This option is equivalent
to the
-exe command-line argument.
- Dependencies
- None - Include all necessary files
in the output file, so that it can be run on systems that do not have Perl56.dll
or ActivePerl. This option is equivalent to the
-freestanding
command-line argument.
- Perl Dll required on target - Reduce the size of the
generated executable by excluding Perl56.dll from the output file. Target
systems must have the Perl56.dll installed. This setting corresponds with
the
-xclude command-line argument.
- ActivePerl required on target - Create
an output file to run on systems where ActivePerl and any modules
included via
use and require statements are installed. This
option is equivalent to the -dependent command-line argument.
- Verbose build information - Generate detailed
output messages while the output file is being built. This option corresponds
to the
-verbose command-line argument.
- Hide console (for GUI applications) - Similar to running wperl.exe,
this option is useful for building applications that run in the background. This setting
corresponds with the PerlApp
-gui command-line argument and is only available
for the PerlApp tool.
- Overwrite existing build - Replace the existing build with
a new build. If you attempt to overwrite a build without selecting
this option, a pop-up dialog box warns that the .exe file already exists. You can then
choose to overwrite the file, overwrite the file and enable the check box, or
cancel the command. This option is equivalent to the
-force
command-line argument.
- Delete temp files after each run - Freestanding Perl applications,
services and controls sometimes contain embedded DLLs that are extracted and
cached in the host system's temporary directory. Select this check box to
delete these files after each run. This setting corresponds with the
-clean command-line argument.
- Debugging - To debug the Perl executable, control or service
as it is being built, select the desired debugger from the drop-down list. If you are
not using either the Komodo or PDK debugger, specify a Hostname and
Port for another debugger in the fields provided.
Use the Modules tab to add external modules to the build, and
trim unwanted modules.
To add a module to the output program, enter the name of the module in the
Module name field, and click Add. The module
to be added is displayed in the list box above. Remove modules from the list box
using the Delete and Delete All buttons.
This option corresponds with the -add command-line argument.
To remove an unwanted module from the build, enter the name of the module
in the Modules field, and click Add. The module
to be trimmed is displayed in the list box above. Remove modules from the list
box using the Delete and Delete All buttons.
This option corresponds with the -trim command-line argument.
Use the Files tab to add additional files (typically data
files used by the embedded program) to the output file that is extracted when
the program runs.
This option corresponds with the -bind command-line argument.
To add a file to the output program, click Add. In the pop-up
dialog box, enter the source location of the file on your system, and the location
where the file should be extracted when the output file runs.
To edit a file that has been added to the output program, click Edit.
In the dialog box, as required, alter the source location of the file on your system,
and the location where the file should be extracted when the output file runs.
To remove a file that was to be added to the output
program, click the file, then click Delete.
Use the Version tab to embed version information in the
output program. It corresponds to the -info command-line argument.
To alter any of the version options, select the desired option in the
Version field column, and enter the desired value in the
field below. This information is assembled as a version information (VERINFO)
resource and displayed to users if they view the properties for the script
in Windows Explorer.
Use the Library Paths tab to add directories to your build.
The options on this tab correspond with the command-line arguments -lib
and -blib .
To add a lib or blib directory to include in an output file, click Add.
In the Browse for Folder dialog box, select the directory path
to include, and click OK. The path can contain multiple directories
that are separated in the same way as in the PATH environment variable.
Use Delete and Delete All to remove
directories that you do not want to add from the "lib" and "blib" list boxes.
The Extra tab is for adding icon files as well as manually
specifying any additional command-line arguments.
To include .ico files in a build, click Add. From the
Add Icon dialog box, select the icon(s) you want to add, and
click Open. The complete path for the icon file is displayed
in the Icon File list box.
This option is equivalent to the -icon command-line argument.
If you want to specify any command-line parameters in addition to those selected
using the options in the Build Standalone Perl Application dialog box, enter
them in the field provided.
|