Cannot run compiled executable after downloading from GitHub releases #10382
-
|
I wrote a CLI in Deno (source). It works when...I compile locally and run the executable.
It doesn't work when...I download the executable as an asset from GitHub releases and run locally.
Do I need to sign the executables or do something else to get them to work out-of-the-box? P.S. - would be more than happy to contribute to the "Compiling Executables" docs once I figure this out. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 7 replies
-
|
Maybe you just need to make it an executable? |
Beta Was this translation helpful? Give feedback.
-
|
I don't think that after uploading an executable to GitHub releases will preserve its executable status. It's just a file. |
Beta Was this translation helpful? Give feedback.
-
|
Ah okay. I guess I thought it would since if you make a file executable and commit to a repo, it's executable later. How am I supposed to upload it in a way that preserves its executable status? |
Beta Was this translation helpful? Give feedback.
-
|
I chatted with a couple folks on the Deno Discord. They suggested try packaging it as a zip or tarball, which may preserve file permissions |
Beta Was this translation helpful? Give feedback.
-
|
That ended up working! I zipped it up and now when you unzip, it has the right permissions (at least when I tried on Linux). https://github.com/jsjoeio/jp-courses-install/releases/tag/0.0.3 |
Beta Was this translation helpful? Give feedback.
-
|
How would you make it so that you don't need to zip it then? Because it's a bit annoying to have to do that :/ |
Beta Was this translation helpful? Give feedback.
Maybe you just need to make it an executable?
chmod +x ./filename