Post

Replies

Boosts

Views

Activity

Reply to Not Allowed To Open Rust Binary In Terminal
Yes, I can run the binary by calling "cargo run" from the Terminal, and then the binary opens as well. So you are saying that when using Finder, it expects a real app. Ok, so how do I convert my Rust binary into an Apple app? A further question. Are all binaries that run on MacOS considered "apps"? If so, that would imply that all binaries compiled with Xcode would be "apps".
Topic: Code Signing SubTopic: General Tags:
Dec ’24
Reply to Not Allowed To Open Rust Binary In Terminal
Finder When I double click on the binary in Finder, a second Terminal window opens up and says "Process Completed", with no opening of the GUI window. CommanderOne When I click on the binary in the development folder with CommanderOne, I get this first: a new Terminal window opens saying "Process Completed" I also get a notification window from CommanderOne saying “csv” is a Unix app created by the app Commander One. Are you sure you want to open it? When I click "open" to the message above, I get "csv” can’t be opened because Commander One is not allowed to open documents in Terminal." It does not seem to make a difference how the binary is compiled, either a debug or release compile gives the same result. By the way, I notice that my post Title is not completely correct, but I have no way of changing that initial post.
Topic: Code Signing SubTopic: General Tags:
Dec ’24