Support #871
website: Add macOS install instructions
0%
Description
Using the de-facto standard package manager, homebrew, it's just:
brew install audacious
It might help some people if you add this to the Downloads page.
History
#1
Updated by John Lindgren about 6 years ago
- Category set to website
- Tracker changed from Bug to Support
#2
Updated by Elton Sanchez almost 5 years ago
`brew install audacious` will only install the raw program and according to the update 2 at https://anishrkhadkablog.wordpress.com/portfolio/audacious-for-mac/, the following issues arise when using the brew package:
- "icon not showing in the dock" (this is because using `brew install audacious` only installs the executables and libraries, without icons. Such a feature could be implemented if a brew cask was implemented and uploaded to the brew cask repos)
- status bar (I wouldn't consider this an issue as there is no further information posted about this and seems to work for me)
- most of the plugins options not showing up (again, non specific and I got working input modules for playback of midi, MP3, ImpulseTracker (digital music module), and SPC (game music modules).
The report from brew on audacious (4.0.4) states:
- audtool does not work due to a broken dbus implementation on macOS (tested since at least High Sierra, likely the same in both Mojave and Catalina), so it is not built.
- Core Audio output has been disabled as it does not work (fails to set audio unit input property).
- GTK+ GUI is not built by default as the Qt GUI has better integration with macOS, and the GTK GUI would take precedence if present
Also, seems to crash upon exit, with following included in crash report, and cannot bring it back up afterwards (this is more critical). Attached for brevity.
#3
Updated by Elton Sanchez almost 5 years ago
Clarification on "the report from brew on audacious"; this is from the output after installation via brew completes (e.g. `brew install audacious`)
#4
Updated by Elton Sanchez almost 5 years ago
After reinstalling once, the program still crashes when exiting, but can be started up again from the shell without reinstallation.
#5
Updated by John Lindgren over 3 years ago
- Status changed from New to Closed
Closing this since no one has stepped up to work on it.