HALCON Extension Package Programmer's Manual

More documents

Recommendations

Info

108 CHAPTER 7. CREATING A NEW HALCON PACKAGETo create a Parallel HALCON version of your application, just link the objectfiles to the Parallel HALCON version of the libraries (e.g., ÐÔÖÔº×Ó,ÐÔÖÔº×Ó, ÐÔÖÐÓÒº×Ó, andÐÔÖÐÓÒº×Ó in case of a C application).You can use the same object files as for creating the standard HALCON application.The directory °ÀÄÇÆÊÇÇÌ»ÜÑÔÐ×»ÜØÒ×ÓÒ Ô»ÐÓÒÙ×Ö contains two examplemakefiles: ÑÐ creates the example package halconuser, both for standard HAL-CON and for Parallel HALCON. ÑÐ Ø×ØÔÖÓ creates the example applications basedon the package halconuser, again for both HALCON versions. Both makefiles include the fileÑº×ÔÖ¹×ÙÒ¹×ÓÐÖ× which sets architecture-dependent variables.7.2.5.4 Generating Packages Under IRIXIn order to activate a package, its complete path, e.g.°ÀÄÇÆÊÇÇÌ»ÜÑÔÐ×»ÜØÒ×ÓÒ Ô»ÐÓÒÙ×Ömust be included in the environment variable ÀÄÇÆÌÆËÁÇÆË .IntheUNIXversionthepackage paths in ÀÄÇÆÌÆËÁÇÆË are separated by colons. Please see also the commentson installing a HALCON package on a IRIX system on page 8.¯ Creating the operator library ÐÔº×Ó:To create the operator library ÐÔº×Ó containing new HALCON operators theobject files containing the corresponding supply and action procedures must be linked.The linkage of shared libraries is done withÐ ¹Ö×ØÖÝ »Ù×Ö»Ð»×ÓÐÓØÓÒ× ¹×ÖSpecify the desired name ÐÔº×Ó and location of the library with the Ð option¹Ó. To allow the location of such a library 2 to be resolved by the operating system duringruntime (using Ä ÄÁÊÊ ÈÌÀ) also specify ¹×ÓÒÑ ÐÔº×Ó.¯ Creating the C interface library ÐÔº×Ó:To create the C interface library ÐÔº×Ó providing the interface to newHALCON operators, the object file ÀÔºÓ and the new operator libraryÐÔº×Ó must be linked.¯ Creating the C++ interface library ÐÔÔÔº×Ó:To create the C++ interface library ÐÔÔÔº×Ó providing the interface to newHALCON operators, the object files ÀÈÈÔºÓ and ÀÈÈÔÐÓÐºÓ, andthe new operator lib ÐÔº×Ó must be linked.¯ Creating new applications:In order to create new application programs (written in C or C++) you must linkÐÔº×Ó and ÐÔº×Ó or ÐÔÔÔº×Ó to your objects (besidesÐÐÓÒº×Ó and ÐÐÓÒº×Ó or ÐÐÓÒÔÔº×Ó as for any HAL-CON application). Furthermore, you must add the package library subdirectory2 Of course this has to be done for ÐÔº×Ó (¹×ÓÒÑ ÐÔº×Ó)andÐÔÔÔº×Ó(¹×ÓÒÑ ÐÔÔÔº×Ó) as well.HALCON Extension Package Interface / 2000-11-16
7.2. GENERATING HALCON PACKAGES 109Ð»ÑÔ×¹×¹ÖÜº to the environment variable Ä ÄÁÊÊ ÈÌÀ , otherwise theloader will fail to access the libraries.The directory °ÀÄÇÆÊÇÇÌ»ÜÑÔÐ×»ÜØÒ×ÓÒ Ô»ÐÓÒÙ×Ö contains two examplemakefiles: ÑÐ creates the example package halconuser for standard HALCON.ÑÐ Ø×ØÔÖÓ creates the exampleapplications based on the package halconuser.Bothmakefiles include the file ÑºÑÔ×¹×¹ÖÜº which sets architecture-dependent variables.7.2.5.5 Generating Packages Under HP-UXIn order to activate a package, its complete path, e.g.°ÀÄÇÆÊÇÇÌ»ÜÑÔÐ×»ÜØÒ×ÓÒ Ô»ÐÓÒÙ×Ömust be included in the environment variable ÀÄÇÆÌÆËÁÇÆË .IntheUNIXversionthepackage paths in ÀÄÇÆÌÆËÁÇÆË are separated by colons. Please see also the commentson installing a HALCON package on a HP-UX system on page 8.¯ Compiling the source code:In order to generate shared libraries you must produce position independent code. For the» compiler this is done using the option ·.¯ Creating the operator library ÐÔº×Ð:To create the operator library ÐÔº×Ð containing new HALCON operators,the object files containing the corresponding supply and action procedures must belinked. The linkage of shared libraries is done with Ð ¹. Specify the desired nameÐÔº×Ð and location of the library with the Ð option ¹Ó. To allow the location ofsuch a library 3 to be resolved by the operating system during runtime (using ËÀÄÁ ÈÌÀ)also specify the Ð option ·×.¯ Creating the C interface library ÐÔº×Ð:To create the C interface library ÐÔº×Ð providing the interface to newHALCON operators, the object file ÀÔºÓ and the new operator libraryÐÔº×Ð must be linked.¯ Creating the C++ interface library ÐÔÔÔº×Ð:To create the C++ interface library ÐÔÔÔº×Ð providing the interface to newHALCON operators, the object files ÀÈÈÔºÓ and ÀÈÈÔÐÓÐºÓ, andthe new operator lib ÐÔº×Ð must be linked.¯ Creating new applications:In order to create new application programs (written in C or C++) you must linkÐÔº×Ð and ÐÔº×Ð or ÐÔÔÔº×Ð to your objects (besidesÐÐÓÒº×Ð and ÐÐÓÒº×Ó or ÐÐÓÒÔÔº×Ð as for any HAL-CON application). Furthermore, you must add the package library subdirectoryÐ»ÔÔ½º½¹Ô¹ÔÙÜ½¼ to the environment variable ËÀÄÁ ÈÌÀ , otherwise the loaderwill fail to access the libraries.3 Of course this has to be done for ÐÔº×Ð and ÐÔÔÔº×Ð as well.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 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 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?