Essentially, it's either include_bytes! or not doing cargo install, unfortunately. Cargo doesn't allow for any post-build hooks, and on installation it simply copies the binary. If the workflow for specific app needs something else, it's expected that some other build system does the orchestration, and Cargo just provides the binary.