HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

102 CHAPTER 7. CREATING A NEW HALCON PACKAGEFileØÐ Ó ÓÒØÒØ×ºØÑÐÒÜ Ý ÒÑºØÑÐØÓ chapter subchapterºØÑÐoperatorºØÑÐDescriptionHome page containing the chapter structure and links to thedifferent (sub-)chapters (ØÓ chapter subchapterºØÑÐ).Alphabetic list of all operators with links to the correspondingoperator description pages (files operatorºØÑÐ).For every (sub-)chapter: A list of all operators within thechapter with links to the corresponding operator descriptionpages (files operatorºØÑÐ).A description page for each operator.7.1.5 MiscellaneousHere are some more options supported by ÓÑÔ:OptionÓÑÔ ¹ filename ¹Ð×ÓÑÔ ¹Ü filename ¹Ð×ÓÑÔ ¹Ñ ¹Ð×DescriptionConsider only the operators listed in filename.Do not consider the operators listed in filename.Generate a list of operators within the -files sortedby modules.7.2 Generating HALCON PackagesOnce the new operators have been described in -file(s) and implemented (supply and actionprocedures) a couple of dynamic objects (DLLs in Windows NT an Windows 2000, sharedlibraries in UNIX environments) must be created. Never change the name of a package orthe corresponding names of the libraries/DLLs contained in a package. These names areencoded within the libraries. If you change the names this information will not match anylonger. Thus, the loader of the operating system will fail to open the dynamic libraries. If youwant to rename a package, you must create the libraries/DLLs again.To activate a package, its complete path must be added to the environment variableÀÄÇÆÌÆËÁÇÆË , e.g.,±ÀÄÇÆÊÇÇÌ±ÒÜÑÔÐ×ÒÜØÒ×ÓÒ ÔÒÐÓÒÙ×ÖPlease note, that the package paths in ÀÄÇÆÌÆËÁÇÆË are separated by semicolons (WindowsNT/ 2000) or colons (UNIX), see also section 1.3.7.2.1 Creating the Operator LibrariesThe supply and action procedures must be encapsulated in a DLL or a shared library. The nameof this shared object has to be identical with the package name (plus file extension). For the useHALCON Extension Package Interface / 2000-11-16
7.2. GENERATING HALCON PACKAGES 103by Parallel HALCON, a second version of the library must be created, with the additional prefixÔÖ to the name. Please refer to section 7.2.5 and the documentation of your programmingenvironment for more details (also about the following sections).Under Windows NT or Windows 2000 the generated DLLs must be placed in the subdirectoryÒÒ±ÊÀÁÌÌÍÊ±, the libraries in the subdirectory ÐÒ±ÊÀÁÌÌÍÊ±. Under UNIX,the generated shared libraries must be placed in the subdirectory ÐÒ±ÊÀÁÌÌÍÊ±, binariesin the subdirectory ÒÒ±ÊÀÁÌÌÍÊ± of the package.7.2.2 Creating the C InterfaceTo access new HALCON operators inside a package within C programs or from ÀÚÐÓÔ youmust create a C interface library Ô residing in the subdirectory ÐÒ±ÊÀÁÌÌÍÊ±of the package. This library is based on a single C file ÀÔº which is generated viaÓÑÔ ¹ ¹ÔÔ ¹Ð´×µfrom the -file(s) of your new operators. Note, that ÓÑÔ simultanously generates the fileÀÔº containing the C prototypes of your new operators. Include this file in your Cprograms using these operators.7.2.3 Creating the C++ InterfaceTo access new HALCON operators inside a package within C++ programs you must create aC++ interface library ÔÔÔ residing in the subdirectory ÐÒ±ÊÀÁÌÌÍÊ± of thepackage. This library is based on the files ÀÈÈÔºÔÔ and ÀÈÈÔÐÓÐºÔÔgenerated viaÓÑÔ ¹ ¹ÔÔ ¹Ð´×µfrom the -file(s) of your self developed operators. Note, that ÓÑÔ simultanously generatesthe file ÀÈÈÔº containing the C++ prototypes of your new operators. Include this filein your C++ programs using these operators.7.2.4 Creating New ApplicationsIn order to create new application programs (written in C or C++) based on your own HAL-CON operators you must link the corresponding language interface libraries Ô orÔÔÔ to your objects. Furthermore, you will need the HALCON library itself and theHALCON/C or HALCON/C++ library (as for any HALCON application).7.2.5 Additional Information for Specific ArchitecturesThe previous sections summarized the generation of HALCON extensions in general. Thissection contains additional information for specific architectures. The main differences concernthe name handling and the generation of shared libraries / DLLs.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 and 108: Chapter 7Creating a New HALCON Pack
Page 109: 7.1. THE HALCON COMPILER ’HCOMP
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

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

Delete template?

Save as template?