# Create a QNN converter Op Package shared library `qnn-op-package-generator` generates skeleton code and makefiles used to create a QNN converter Op Package shared library. `qnn-op-package-generator` takes an XML configuration as an input that describes the package attributes and the `--converter_op_package` or `-cop` option that specifies whether to generate the converter Op Package and produce a QNN converter Op Package directory structure. Note Executing `qnn-op-package-generator` with the `--converter_op_pacakge` or `-cop` option creates a Converter Op Package in addition to the QNN Op Package. The name of the Converter Op Package generated will be *QNN Op Package* appended with the string `Converter_Op_Package`. **The option is not supported on Windows platform yet**. ## Linux Platform 1. Create a Converter Op Package skeleton - Using ReluOpPackage as an example. Note These instructions assume that the general setup instructions [1](https://docs.qualcomm.com/doc/80-63442-10/topic/converter_op_package_gen_example.html#id3) have been followed and that `qnn-op-package-generator` is accessible on the command line. For Linux users, the converter Op Package can be generated and compiled on a linux-86\_64 platform. 1. Define an XML OpDef configuration. This operation definition XML describes package information like name, version, and domain. See [XML OpDef Schema Breakdown](https://docs.qualcomm.com/doc/80-63442-10/topic/op_def_schema.html) for more information about XML schema. Sample configurations can also be found at [Example XML Op Def Configs](https://docs.qualcomm.com/doc/80-63442-10/topic/example_op_defs.html) and in the SDK at: ${QNN_SDK_ROOT}/examples/QNN/OpPackageGenerator Copy to clipboard Note The XML configuration used to generate the QNN Converter Op Package is same as the XML configuration used in QNN Op Package generation. 2. Run the `qnn-op-package-generator` tool and pass the XML configuration using the `--config_path` or `-p` option along with the `--converter_op_pacakge` or `-cop` option. qnn-op-package-generator -p /examples/QNN/OpPackageGenerator/ReluOpPackageCpu.xml -cop -o Copy to clipboard This command creates an Op Package named *ReluOpPackage* and a converter Op Package named *ReluOpPackage\_Converter\_Op\_Package*. [2](https://docs.qualcomm.com/doc/80-63442-10/topic/converter_op_package_gen_example.html#id4) Note The `-p` command line option can be specified multiple times to generate different packages, provided each package name is distinct. If the package name is not distinct, the tool will merge all ops defined in each configuration into a single package directory. - Directory structure The package directory tree is shown and explained below: |-- Makefile |-- ConverterOpPackage |-- ConverterOpPackage.cpp `-- Makefile.linux-x86_64 Copy to clipboard - Makefile – Contains make targets and rules to compile the package source files for x86 targets. - ConverterOpPackage – Contains generated source files for all operations defined in the configuration and target specific makefile. Note The converter Op Package must be generated and compiled on a linux-86\_64 platform. 1. Implement the skeleton code - Op source file – ConverterOpPackage.cpp The source file contains empty functions bodies that should be completed by users. The code used in this section references the generated package in [Directory Structure](https://docs.qualcomm.com/doc/80-63442-10/topic/converter_op_package_gen_example.html#package-directory-structure). The following example highlights the output for the Relu op defined in the example configuration. The following autogenerated code contains a structure that takes opConfig of type Qnn\_OpConfig\_t as its parameter. OpConfig is the operations configuration for storage and retrieval of inputs, outputs, and parameters. 1EXPORT_API Qnn_ErrorHandle_t ReluShapeInference(Qnn_OpConfig_t *opConfig) { 2 3/** 4* Add code here 5**/ 6 7return QNN_SUCCESS; 8} 9 10Qnn_ErrorHandle_t (*ReluOutputInfoInferencePtr)(Qnn_OpConfig_t *) = &ReluShapeInference; Copy to clipboard Complete the function by implementing the logic to populate output shapes using the opConfig and add any necessary validation. The function is called by a function pointer associated by the converter. 1EXPORT_API Qnn_ErrorHandle_t ReluDataTypeInference(Qnn_OpConfig_t *opConfig) { 2 3/** 4* Add code here 5**/ 6 7return QNN_SUCCESS; 8} 9 10Qnn_ErrorHandle_t (*ReluDataTypeInferencePtr)(Qnn_OpConfig_t *) = &ReluDataTypeInference; Copy to clipboard Complete the function by implementing the logic to populate output datatypes using the opConfig and add any necessary validation. The function is called by a function pointer associated by the converter Note Users can populate both the output shapes and output datatypes within a single function named operation name followed by ShapeInference (Eg: ReluShapeInference for Relu operation). This ensures backward compatibility. Users should note that populating both the output shapes and output datatypes within the same function will be deprecated and the logic to populate the output shapes must be written in OpNameShapeInference function and and output datatypes must be written in OpNameDataTypeInference function respectively. Note The operation name *must* be a valid C++ identifier, meaning that it can only contain alphanumeric characters and underscores. Note The inputs, outputs, and parameters order in the opConfig *must* follow the order they are present in the model. See `/examples/QNN/OpPackageGenerator/generated/CONVERTER` for sample Relu implementation. 2. Compile the package for x86 targets. 1. Set up the QNN environment. $ source /bin/envsetup.sh Copy to clipboard 2. **Required for x86**: Ensure clang compiler is in your path, or set CXX to point to a valid compiler path.[3]\_ Note Steps a-b can also be set manually in the makefiles or as a command line option to make without the use of scripts. 3. Compile the package for x86 targets : > > > make cpu > or > make cpu_x86 > Copy to clipboard This creates a shared library at *<current\_dir>/<package\_name>\_Converter\_Op\_Package/ConverterOpPackage/lib<ConverterOpPackage>.so* - [1](https://docs.qualcomm.com/doc/80-63442-10/topic/converter_op_package_gen_example.html#id1) - For instructions on QNN tool setup, see [Setup](https://docs.qualcomm.com/doc/80-63442-10/topic/general_setup.html). - [2](https://docs.qualcomm.com/doc/80-63442-10/topic/converter_op_package_gen_example.html#id2) - If the directory already exists, the tool will only generate new files and attempt to append to existing files. To force a new package to be generated, use the `--force-generation` option. - 3 - The script, `/bin/check-linux-dependency.sh`, can also be used to download the appropriate Clang version if it is not present. Last Published: Jun 04, 2026 [Previous Topic Example XML OpDef Configs](https://docs.qualcomm.com/bundle/publicresource/80-63442-10/topics/example_op_defs.md) [Next Topic Tools](https://docs.qualcomm.com/bundle/publicresource/80-63442-10/topics/general_tools.md)