🤑 Indie game store🙌 Free games😂 Fun games😨 Horror games
👷 Game development🎨 Assets📚 Comics
🎉 Sales🎁 Bundles

Easy way to install butler on macOS?

A topic by eternalstarlight created 24 days ago Views: 79 Replies: 5
Viewing posts 1 to 3

Hello!


I am currently working on a game that I will release on itch.io and I am running into problems installing butler on macOS. I've looked all around the internet on how to write it into my bash_profile file but whenever I run the command, it fails to run with the error saying that the command isn't found. I don't know if this is a problem with the recent macOS software updates but it seems like common commands do not run without preempting them with running export to the default path.


Will there be an easier way to push builds through butler? If not, an easier way to install it on macOS?


Thank you.

Admin (Edited 1 time) (+1)

If doing something like:

export PATH=$PATH:~/path/where/butler/binary/is

does not work for you, you can always copy the `butler` binary to `/usr/bin`!

Make sure that it's executable first, with `chmod +x butler`

I will try that and let you know my results.

(+1)

I was able to make it an executable but I was unable to add it to my PATH. It still works if I drag the file into Terminal then run commands from there.

(Edited 1 time)

It works but it looks like I'll have to drag into terminal every time.


EDIT: I have a found a solution that works. It looks like newer versions of macOS (I'm assuming Sierra on up) only allow users to add Terminal executables to the /usr/local/bin without any problems or having to use sudo (which I attempted to open the /usr/bin folder with no luck). So if it's possible, there needs to be a disclaimer for macOS users to install butler for newer versions of the OS.

Admin(+1)

Indeed, `/usr/bin` is owned by root, so you need sudo to place executables there.

That's why the default instructions tell you to put it in a path you own and to add it to your `$PATH` environment variable. I assure you those instructions are correct even for recent macOS versions, it's ok if you did it another way, glad you got it working!