search

sveinbjornt / Platypus

Create native Mac applications from command line scripts.
https://sveinbjorn.org/platypus
BSD 3-Clause "New" or "Revised" License
2.84k stars 171 forks source link

Issues with relative path to the interpreter #233

Open finnhewes opened 2 years ago

finnhewes commented 2 years ago

Platypus now supports a relative path to the interpreter, which means that in theory you can include a static binary in bundled files and call it directly.

Originally posted by @sveinbjornt in https://github.com/sveinbjornt/Platypus/issues/211#issuecomment-1236192611

I'm working on a small project I want to distribute to my non-tech savvy dad and have him be able to click and run without having to configure, update, or install anything outside of the app. I've tried a number of ways of bundling the interpreter and referencing it (inside of a venv, inside of a bin folder (tried this both inside and outside of a venv), as an alias file, and as a static binary) and can't seem to get anything working.

Platypus detects the interpreter within my bundled files in the setup GUI, and wraps it into the application's contents, but whenever I try to run the app, a missing interpreter error appears.

This may not be an issue with Platypus itself, but it is directly related to the functionality I can expect from apps I wrap in Platypus, so I thought that posting it here could possibly lead to a discussion that's helpful for others too! I searched through closed issues and found the reference above, but I still couldn't iron out the kinks on my end. Any ideas?

footlooseboss commented 2 years ago

(assuming Python) might help: gregneagle/relocatable-python