Login

We are experiencing technical difficulties. Your form submission has not been successful. Please accept our apologies and try again later. Details: [details]

Download

Register

We are experiencing technical difficulties. Your form submission has not been successful. Please accept our apologies and try again later. Details: [details]

Download

Thank you for registering

An email to complete your account has been sent to

Return to the website

get direct access

Fill in your details below and get direct access to content on this page

Text error notification

Text error notification

Checkbox error notification

We are experiencing technical difficulties. Your form submission has not been successful. Please accept our apologies and try again later. Details: [details]

Download

Thank you for your interest

You now have access to CX-Designer

A confirmation email has been sent to

Continue to page

Please or get direct access to download this document

Mace-cl-compiled-program.bin Jun 2026

scp mace-cl-compiled-program.bin user@raspberrypi:/home/user/model/ ssh user@raspberrypi cd /home/user/model ./my_mace_app --program mace-cl-compiled-program.bin

Disclaimer: This article is based on information available in the MACE open-source community documentation and GitHub issues as of 2026. How to build - MACE documentation - Read the Docs

: Apps that use real-time face-tracking, augmented reality (AR) masks, or live video enhancement.

Developers may encounter the error "File does not exist" or a "no precompiled OpenCL binary" warning in their logs. mace-cl-compiled-program.bin

MACE implementations usually include a "fallback" mechanism. If the binary load fails, the app deletes the file and recompiles from source.

When a developer uses the MACE toolchain to compile a model for GPU deployment, the framework will generate OpenCL kernel source code. During the code generation build process ( build_type: code ), MACE has an internal mechanism to compile these kernels and generate the .bin file. A specific commit in MACE's history adds the functionality to "generate opencl kernel binary from source, and create opencl program with binary," marking the introduction of this file.

: This .bin file stores the result of that compilation. scp mace-cl-compiled-program

It is often accompanied by other cache files like mace-cl-kernel.bin or mace-cl-compiled-program.bin.pb (a text proto version).

(Neural Processing Units / Digital Signal Processors, via Qualcomm Hexagon NN Direct or Android NNAPI)

This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. How to build - MACE documentation - Read the Docs MACE implementations usually include a "fallback" mechanism

When deploying custom configurations, developers often see warnings in their terminal output, such as: File /data/local/tmp/mace_run/mace_cl_compiled_program.bin does not exist

The file is typically generated during the model deployment or tuning phase. How to build - MACE documentation - Read the Docs