(v13) Integration notes

This page applies to Harlequin v13.1r0 and later; and to Harlequin Core but not Harlequin MultiRIP.

This section provides basic information on what you need to make use of the SDK.

The file structure of the SDK means that essentially everything in the \lib and \SW folder is required in order to create a working application. You can manage without some files, but to do this you have to modify the build dependencies.

Each instance of Harlequin Core must have its own SW directory (that is, multiple instances of Harlequin Core cannot share a SW folder unless mounted using the union device and a unique writable SW output folder). See the -W option to clrip, and the skinkit SDK union device.

Optional parts of the SDK include \cmmeg, \htmeg, and \liblittlecms. These folders provide examples of specific functionality that you may or may not require.

The \libtiff folder is used by certain raster handlers which are part of the SDK, but you may decide not to use them.

The files within \skintest are required until you have created your own equivalent. Skintest is an example application and the code is often use as a boilerplate for your created application and so skintest can still be present in many implementations.

The skintest example is provided on an “as is” basis and without warranty of any kind. Global Graphics Software Ltd. does not warrant or make any representations regarding the use or results of use of this example.

Skintest calls out to and, in conjunction with other code, communicates with the RIP core (corelib).

The skinkit requires the include files within lib/interface, lib/skinkit/export, and lib/skinkit/pc/export (on Windows; alternatively lib/skinkit/unix/export on Linux and macOS) and also some include files for third-party libraries (for example, lib/zlib/include).

OEM applications built using skinkit must include these files; you should understand how to access the functionality contained therein. Run time files in \SW are also required when running the RIP.

You must have an understanding of events to deal with synchronization, and understand the \SW folder and how when they try to use PostScript language resources in the RIP, how the RIP finds that and accesses it.

In addition, you should understand the underlying devices that the RIP uses for communication.