HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

100 CHAPTER 7. CREATING A NEW HALCON PACKAGEÓÑÔ ¹ ¹ÔÔ℄ ¹Ð×to create interface code for . ÓÑÔ ¹ ¹ÔÔ creates the files ÀÔº (interfacecode) and ÀÔº (prototypes of operators).To create interface code for ·· useÓÑÔ ¹ ¹ÔÔ℄ ¹Ð×creating ÀÈÈÔºÔÔ, ÀÈÈÔÐÓÐºÔÔ, and ÀÈÈÔº (prototypes)providing the C++ interface to the new operators.The generated source files are the basis for the interface libraries, see section 7.2.7.1.2 Creating the ÐÔ-filesThese files are necessary for the online access to the operator knowledge base via HALCONoperators like Ø ÓÔÖØÓÖ ÒÓ. For example, ÀÚÐÓÔ uses their information to build upthe menu tree ’ÇÔÖØÓÖ’ (chapter and section structuring) and ’ËÙ×ØÓÒ×’ (alternatives,cross references, predecessor, successor, and keywords). The ÐÔ files are generated for thelanguage selected with the (optional) ¹Ð option. The default language is ÒÐ×.ÓÑÔ ¹Å ¹Ðlanguage℄ ¹Ð×creates the following files:FileDescriptionlanguageºÐÔ The operator description (text, value lists, ...).languageºÜ Index for every operator specifying the start address of its entry withinthe ºÐÔ file.languageºÝ List of keywords with the associated operators.languageºÒÙÑ Specification of the number of parameters per parameter class for everyoperator.languageº×Ø Specification of the parameter names and the chapter names for everyoperator.In addition to the option ¹Å¹TAGS-FILEcan be set in order to insert the source file and the line number of the supply procedure of theoperator into the ºÐÔ file. To do this, a TAGS-File (usually ÌË) must have been generatedby the Ø× command before.HALCON Extension Package Interface / 2000-11-16
7.1. THE HALCON COMPILER ’HCOMP’ 1017.1.3 Creating the ManualsÓÑÔ can generate L A TEX files containing the complete reference manuals (full text or shortversion) adapted to the different supported programming languages, i.e. the description of theoperators is provided in a specific syntax. UseÓÑÔ ¹Êplanguagespecification ¹Ðlanguage] ¹Ð×to create L A TEX files with planguage and specification as follows:planguage can be set to , ··, andØÖ× (corresponds basically to the ÀÚÐÓÔ-Syntax).ØÖ× is default and may therefore be omitted. The specification determines the extent of themanual by specifying the additional operator information that will be inserted into the manualbesides the operator header. Supported specifications are:SpecificationÐÐ×ÓÖØ℄×ÓÐDescriptionAll available information is presented in the manual.Only the short descriptions are inserted.A file is generated for each operator containing its complete description.By specifying ×ÓÐ afileoperatorºØÜ is created for every operator. Using any of the otherspecifications the file ÀÊÖÒºØÜ is generated.The generated L A TEX files use the package ÐÓÒ ÖÖÒº×ØÝ. This package resides inthe directory °ÀÄÇÆÊÇÇÌ»Ó»ÑÖÓ× (UNIX notation). You must include this directory inthe environment variable ÌÁÆÈÍÌË, otherwise L A TEX will be unable to find it (typical errormessage: Ð ÐÓÒ ÖÖÒº×ØÝ³ ÒÓØ ÓÙÒ.The L A TEX file(s) can be transformed to PostScript files by using ÐØÜ, ÑÒÜ, andÚÔ×.Note, that ÐØÜ must be called several times to get the references right.7.1.4 Creating HTML FilesÓÑÔ can also generate HTML files. Thus, its easy to provide an online documentation of newoperators that can be accessed using an HTML browser. UseÓÑÔ ¹Äplanguagespecification ¹Ðlanguage℄ ¹Ð×to create HTML files. All things said above about the issues planguage and specification holdalso for this section — with the exception that ×ÓÐ is not supported. The following files aregenerated: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 15 and 16:
1.3. INSTALLING A HALCON PACKAGE 76
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 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
2.3. DESCRIBING THE PARAMETERS 252.
Page 35 and 36:
Page 37 and 38:
2.3. DESCRIBING THE PARAMETERS 29Pl
Page 39 and 40:
2.3. DESCRIBING THE PARAMETERS 31¯
Page 41 and 42:
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 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: Chapter 7Creating a New HALCON Pack
Page 111 and 112: 7.2. GENERATING HALCON PACKAGES 103
Page 114 and 115: 106 CHAPTER 7. CREATING A NEW HALCO
Page 122 and 123: 114 APPENDIX A. HALCON ERROR CODES
Page 140: 132 APPENDIX A. HALCON ERROR CODESH
show all

HALCON Extension Package Programmer's Manual

Create successful ePaper yourself

Delete template?

Save as template?