HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

6 CHAPTER 1. INTRODUCTION¯ ÐÔ: This subdirectory contains files with data for the online access to the knowledgebase. They must be generated and placed in this directory in order to use a package insideof ÀÚÐÓÔ. Without these files ÀÚÐÓÔ cannot retreive the information needed toaccess the operators of a package.We also recommend to provide additional subdirectories:¯ ÒÐÙ: In this directory the generated include files containing the prototypes for theoperators of a package should be placed.¯ Ó: In this directory the documentation of the package should be placed (see also%HALCONROOT%Òdoc for comparison). Especially, it is necessary to put the generatedHTML files in docÒhtmlÒreferenceÒhdevelop in order to enjoy the online help fromthe operator window of ÀÚÐÓÔ.¯ ÜÑÔÐ×: This directory might contain some typical example programs (e.g., ÀÚÐÓÔdev-files) demonstrating the use of the new operators.¯ Ñ×: If the provided examples need specific images, they should be placed in thisdirectory. In that case we recommend to include the path to this subdirectory in theenvironment variable HALCONIMAGES in order to allow access to these images withoutusing an absolute file path in the programs.1.2.3 How to Create and Use a HALCON PackageIn summary, the following steps are necessary to create a HALCON package with the nameÔ integrating new operators into the HALCON system. As noted in section 1.2.1, tocreate a Parallel HALCON package, you must create a second version of the libraries. A detaileddescription of the steps can be found in the referenced sections of this manual:1. Description of the new operator(s) in one or more -file(s) (cf. chapter 2).2. Creation of a library (called Ô) containing the supply procedures in C and thecorresponding action procedures (cf. chapter 3–6). This library has to be placed in thepackage subdirectory 7 Ð or ÐÒ±ÊÀÁÌÌÍÊ±.3. Creation of a library containing the language dependent operator interface (Ôand ÔÔÔ) based on the -file(s) with the help of ÓÑÔ (cf. section 7.1).These libraries have to be placed in the subdirectory Ð or ÐÒ±ÊÀÁÌÌÍÊ± ofthe package.4. Generation of files for online access to the knowledge base with the help of ÓÑÔ.These files are used, e.g., by ÀÚÐÓÔ. They have to be placed in the subdirectoryÐÔ of the package.5. Generating the HTML reference files with the help of ÓÑÔ (optional). The generatedfiles have to be placed in the subdirectory ÓÒØÑÐÒÖÖÒÒÚÐÓÔ, , orÔÔof the package.7 In the Windows NT/ 2000 version, the DLLs corresponding to the link libraries have to to be placed in Ò orÒÒ±ÊÀÁÌÌÍÊ±.HALCON Extension Package Interface / 2000-11-16
1.3. INSTALLING A HALCON PACKAGE 76. Generating PostScript- manuals with the help of ÓÑÔ (optional).7. Extension of the package list in the environment variable ÀÄÇÆÌÆËÁÇÆË by thecomplete file path of the new package, e.g.,±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×ÖFor specific architectures additional environment variables have to be modified, see sections1.3 and 7.2.5.8. Linking of the generated libraries together with the HALCON library to the image analysisapplication (cf. chapter 7). For this, you have to modify additional environmentvariables, depending on the operating system (see below). Please note, that HDevelopis able to access the new operators dynamically without linkage.1.3 Installing a HALCON PackageIn order to install a HALCON package you have to copy the package to your hard disk and addthe complete path of the package to the environment variable ÀÄÇÆÌÆËÁÇÆË, e.g.,±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×ÖNote, that the delimiter between paths in an environment variable is a semicolon on WindowsNT or Windows 2000 systems and a colon on UNIX systems.Never change the name of a package or the corresponding names of the librariesor DLLs contained in a package.These names are encoded within the libraries/DLLs. If you change the names this informationwill not match any longer. Thus, the loader of the operationg system will fail to open thedynamic libraries. In order to use the new package within HDevelop you have to restart theprogram. For generating a standalone application using the package you have to link the C orC++ interface library of the package to the application code, see sections 7.2 and 7.2.5.If the package contains images used e.g., within example programs you might want to includethe corresponding directory (e.g., Ñ× within the package) in the environment variableÀÄÇÆÁÅË to access those images without specifying a complete path.For UNIX architectures you have to modify additional environment variables in order to use aHALCON package (see below).1.3.1 Additional Information for Windows NT and Windows 2000To be able to link the package DLL to your application program, the complete DLL file path ofthe new package, e.g.,±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×ÖÒbinÒ¹ÒØhas to be added to the environment variable ÈÌÀ.Do not copy a package DLL into the Windows system directories, as it would be loadedtwice in this case!HALCON 6.0
Page 1: HALCON Version 6.0MVTec Software Gm
Page 7 and 8: Dl Iosub menţionează că diferen
Page 9 and 10: Chapter 1IntroductionHALCON can be
Page 11: 1.1. HALCON OPERATORS 3objects (or
Page 17 and 18: 1.4. AN EXAMPLE 9Note, that it is n
Page 19 and 20: 1.4. AN EXAMPLE 11¯ one input cont
Page 21 and 22: 1.5. ADDITIONAL SOURCES OF INFORMAT
Page 23 and 24: Chapter 2Operator Description (-fil
Page 25 and 26: 2.2. EXTENDED OPERATOR DESCRIPTION
Page 33 and 34: 2.3. DESCRIBING THE PARAMETERS 252.
Page 37 and 38: 2.3. DESCRIBING THE PARAMETERS 29Pl
Page 39 and 40: 2.3. DESCRIBING THE PARAMETERS 31¯
Page 43 and 44: 2.4. TEXT IN ’DEF’-FILES 35Umla
Page 45 and 46: Chapter 3Style Guide for Programmin
Page 47 and 48: 3.2. MEMORY MANAGEMENT 39If you use
Page 49 and 50: 3.2. MEMORY MANAGEMENT 41NamesÀÐ
Page 51 and 52: 3.2. MEMORY MANAGEMENT 43NamesÀÐ
Page 53 and 54: 3.3. STRUCTURING PROGRAMS 453.2.3 D
Page 55 and 56: 3.6. ERROR HANDLING 47or via Extens
Page 57 and 58: Chapter 4HALCON Data TypesThe HALCO
Page 59 and 60: 4.2. REGION DATA (’HRLREGION’)
Page 61 and 62: 4.3. XLDS (’HCONT’, ’HPOLY’
Page 63 and 64:
4.4. CONTROL PARAMETERS (’HPAR’
Page 65 and 66:
4.4. CONTROL PARAMETERS (’HPAR’
Page 67 and 68:
Chapter 5Handling Iconic Objects an
Page 69 and 70:
5.1. BASIC ACCESS TO ICONIC INPUT O
Page 71 and 72:
5.1. BASIC ACCESS TO ICONIC INPUT O
Page 73 and 74:
5.2. ADDITIONAL ROUTINES FOR ACCESS
Page 75 and 76:
5.2. ADDITIONAL ROUTINES FOR ACCESS
Page 77 and 78:
5.3. LOOP MACROS FOR ACCESSING SING
Page 79 and 80:
5.4. CREATING OBJECTS AND WRITING O
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
5.5. READING AND WRITING CONTROL PA
Page 89 and 90:
5.5. READING AND WRITING CONTROL PA
Page 91 and 92:
5.6. AUXILIARY MACROS AND PROCEDURE
Page 93 and 94:
5.6. AUXILIARY MACROS AND PROCEDURE
Page 95 and 96:
Chapter 6Special Routines for Typic
Page 97 and 98:
6.1. LOOP MACROS 89NamesÀÐÐÊ¸
Page 99 and 100:
6.1. LOOP MACROS 91contains less ch
Page 101 and 102:
6.1. LOOP MACROS 93ÀÖÖÓÖ ÁÈ
Page 103 and 104:
6.2. OBJECT GENERATION 95ÀÖÖÓÖ
Page 105 and 106:
6.2. OBJECT GENERATION 97each regio
Page 107 and 108:
Chapter 7Creating a New HALCON Pack
Page 109 and 110:
7.1. THE HALCON COMPILER ’HCOMP
Page 111 and 112:
7.2. GENERATING HALCON PACKAGES 103
Page 114 and 115:
106 CHAPTER 7. CREATING A NEW HALCO
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
114 APPENDIX A. HALCON ERROR CODES
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140:
132 APPENDIX A. HALCON ERROR CODESH
show all

HALCON Extension Package Programmer's Manual

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?