A SERVICE OF

logo

Installing the PDF Library and DLI 2.25
Sample Jobs
Each product contains a collection of sample jobs illustrating various tasks. Each sample job is contained
within its own subdirectory under its respective product, such as (on Windows platforms)
C:\Datalogics\APDFLxxx\Apdfl\Samples\ or C:\Datalogics\APDFLxxx\Dli\Samples\.
You may use the makefile.W32 included with each sample to build the job via the NMAKE command, or,
on Windows, you can build applications via the supported development software for the Windows
platforms, Microsoft Visual Studio C++ v6.0 or Microsoft Visual Studio .NET. Project Workspace files
(all.dsw under the \APDFL branch and dli_samples.dsw under the \Dli branch) are located in a
\Samples\All subdirectory underneath both the \ADPFL and \Dli sample directories.
To compile and link a selected sample yourself, set your default to its subdirectory and issue the
command:
nmake /f makefile.W32
This will compile and link the sample in a new \Release subdirectory under the current sample
location.
In order to execute the sample program from the current directory, specify the path to the executable, or
drop down into the \Release subdirectory to run it.
Some samples include referenced files that are located in the @data directory. These samples need to be
run from the original sample directory with the release path included with the executable:
release\sample.exe
For example, in order to run the APDFL addimage sample job you must type:
release\addimage.exe
as found in the C:\Datalogics\APDFLxxx\Apdfl\Samples\addimage directory.
The program expects the data files to be in a location relative to the sample source directory, not relative
to the \Release directory.
NOTE: The DLI DLL file Dli_dll.dll and other DLL files installed under DLI
must be placed in a directory specified in your PATH definition in order for the
sample executables to run correctly. They are initially installed in the
C:\Datalogics\APDFLxxx\DLI\Libs directory. Be sure to remove or
rename any previous copies which may be located elsewhere on your machine.