HDevelop looks for procedures in a set of locations in the order specified in this section. Locations can be either directories or library files.
Import locations are specified in the program code using the import statement. Program lines following the import statement may call procedures from that location.
For example, if you want to call the procedure config.hdvp from the directory C:/Users/Public/procedures/common, here is how this can be achieved:
... import C:/Users/Public/procedures/common config() ...
An import location is valid from its import call to the end of the procedure.
HDevelop can be started from the command line with a set of locations that are searched for procedures in the current session only.
Calling
hdevelop -external_proc_path:<path name(s)>
adds the locations given in path name(s) to the list of searched procedure locations. Multiple locations may be specified by using the system-dependent separator, “;” on Windows systems and “:” on Linux systems.
Subdirectories of the specified locations are searched recursively.
Arbitrary locations can be added or removed in the preferences of HDevelop. Just like the standard procedure path below, each user-defined directory can be enabled or disabled independently. The user-defined directories and their settings are persistent. They survive a restart of HDevelop. It is good practice to put commonly used procedures into these locations.
Subdirectories of the specified locations are searched recursively.
By default, HDevelop is set up to look for procedures in a predefined directory which contains several useful procedures. The standard procedure path is %HALCONROOT%\procedures under Windows and $HALCONROOT/procedures under Linux. Because many example programs shipped with HALCON rely on these procedures, the standard procedure path cannot be removed, but it can be disabled to make the corresponding procedures unavailable.
Subdirectories of the specified location are searched recursively.