(v13) Plugin directory

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

The plugin directory can have any name provided that it is unique. Its name is usually similar to the plugin's executable, but this is not a requirement.

The plugin can determine the full path of the directory from which the executable is loaded in two ways:

• Use the field d_plgDir in the deviceDefinition structure.
• Use the fields d_SWDir and d_plgDir in the deviceDefinition structure which are passed to the PLUGIN function.

Note: The deviceDefinition structure is not passed to the RIPCALL functions in CoreModule plugins.

• The plugin can access data files by concatenating their names to the values of d_SWDir and d_plgDir . The values include a terminating directory separator.

• Using the SELECT_DEV_DIRECTORY entry of the s_param array in the devSelectDeviceParam structure passed to the D_SELECT_DEVICE selector call. For example: pSelDevParam->s_param[SELECT_DEV_DIRECTORY]

Again, this value includes a terminating directory separator.