You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like the default process name has changed from aircast-osx-multi to aircast-macos.
Also, line 75 has said process name hardcoded in a grep instead of referring to the processName variable defined up top by the user.
I'd do a PR myself for those two little items, but I also had to add a line to export my DYLD_LIBARY_PATH otherwise I get an error about libcrypto and the plugin doesn't actually work. It's my understanding this has to do with Homebrew putting packages somewhere different on Apple silicon (which I use). I'm a layman and not a developer and I'm not sure what the best practice is for handling Intel vs Apple issues like this other than adding a line for m* chip users to uncomment?
The text was updated successfully, but these errors were encountered:
fao @CartoonChess -
Looks like the default process name has changed from
aircast-osx-multi
toaircast-macos
.Also, line 75 has said process name hardcoded in a grep instead of referring to the
processName
variable defined up top by the user.I'd do a PR myself for those two little items, but I also had to add a line to export my
DYLD_LIBARY_PATH
otherwise I get an error about libcrypto and the plugin doesn't actually work. It's my understanding this has to do with Homebrew putting packages somewhere different on Apple silicon (which I use). I'm a layman and not a developer and I'm not sure what the best practice is for handling Intel vs Apple issues like this other than adding a line for m* chip users to uncomment?The text was updated successfully, but these errors were encountered: