Deployment
It doesn't matter which platform is used on the developement machine; it's possible to target all supported platforms.
Example
You can create a macOS application on your Windows machine, however you'll need to sign the application manually after copying to the macOS machine!
When the created application is copied to the target machine, some steps might need to be taken to make it possible to run it.
macOS
Depending on how the application is copied to the target machine the necessary read, write and execute permissions might be removed. If the error message "You do not have permission to open the application" is shown try setting the correct permissions:
Starting from Big Sur on macOS ARM targets it is a requirement to sign the application. Miletus applications come unsigned on all platforms so on a macOS ARM target they always need to be signed first after copying:
If the code signing fails with the message "resource fork, Finder information, or similar detritus not allowed", remove the extended attributes by running the following command and sign the application afterwards:
The code signing above of course is not the equivalent of code signing with your own Developer ID certificate and it should only be used for testing (or personal use). Please consult Apple's guides on code singing.
The macOS application corresponding to the developer machine will automatically have the above code signing executed. You can still code sign with your own Developer ID certificate afterwards.
Linux and Raspberry Pi
Depending on how the application is copied to the target machine the necessary read, write and execute permissions might be removed. If the application cannot be run due to missing permissions try setting them: