-
-
Notifications
You must be signed in to change notification settings - Fork 200
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[REQ] Add Homebrew support for macOS #553
Comments
Another way around this would be to build the code locally, which I do every time. Although a bit clunky and time-consuming for someone doing it for the first time, it works well. |
Here's a quick breakdown of what you need to build it from your own Mac device: Installing Build DependenciesMake sure you have Homebrew installed (which I believe you already have). You'll also want:
After downloading and installing Xcode, I suggest opening it at least once to make sure Command Line Tools are enabled: Click Then open Finally, make sure Downloading the repositoryYou can do this in two ways:
If you downloaded a zip, make sure you extract it. For the rest of the guide, I'll assume the code was cloned/extracted to the Building the projectThe trickiest part, but if you have all the dependencies set, you should have a smooth way through this too. To make it easier, create a file named Now open #!/usr/bin/env bash
# Clean old binaries, if any
rm -rf ~/Library/Developer/Xcode/DerivedData/* && \
rm -rf ./GalaxyBudsClient.Platform.OSX/Native/Build && \
xcodebuild clean -project GalaxyBudsClient.Platform.OSX/Native/NativeInterop.xcodeproj
# Pulling native Xcode project dependencies
xcodebuild -project GalaxyBudsClient.Platform.OSX/Native/NativeInterop.xcodeproj -resolvePackageDependencies
# building the native XCode project
xcodebuild -project GalaxyBudsClient.Platform.OSX/Native/NativeInterop.xcodeproj \
-scheme NativeInterop \
-destination platform=macOS,arch=arm64 ARCHS=arm64 ONLY_ACTIVE_ARCH=NO CONFIGURATION_BUILD_DIR=/Users/{YOUR_USERNAME_GOES_HERE}/Downloads/GalaxyBudsClient/GalaxyBudsClient.Platform.OSX/Native/Build/Release CONFIGURATION_TEMP_DIR=/Users/{YOUR_USERNAME_GOES_HERE}/Downloads/GalaxyBudsClient/GalaxyBudsClient.Platform.OSX/Native/Build/Intermediates.noindex \
build
# Getting the necessary workloads for this project
sudo dotnet workload restore
sudo dotnet workload update
# restoring .NET dependencies
dotnet restore -r osx-arm64 --configfile GalaxyBudsClient/nuget.config GalaxyBudsClient/GalaxyBudsClient.csproj
# building the Application
dotnet publish -o bin_osx -c Release --no-restore GalaxyBudsClient/GalaxyBudsClient.csproj Almost there. Now open your terminal on the project folder ( You should see a bunch of text on your terminal. Wait until you see this: If the terminal gives you back control but you're not seeing this message, something probably went wrong. Assuming the build finished with no errors, you should have the App sitting at |
Hello,
I'm reaching out to request adding Homebrew support for macOS to GalaxyBudsClient. Currently, some macOS users encounter issues due to the app being flagged as unverified, even when using the "Open Anyway" option. Integrating Homebrew support would streamline installation and alleviate these verification concerns.
Thank you for considering this enhancement!
Is your feature request related to a problem? Please describe.
Yes, macOS users are encountering issues with the GalaxyBudsClient being flagged as unverified, which requires them to manually override security settings. (For all apps, not just this one)
Describe the solution you'd like
I would like to request the addition of Homebrew support for GalaxyBudsClient on macOS. This would provide a verified installation method and avoid the need for users to bypass security warnings.
Describe alternatives you've considered
Currently, users can manually bypass security settings by choosing "Open Anyway" but having Homebrew support would automate the installation process and ensure a verified package.
Additional context
The integration of Homebrew support would enhance user experience on macOS by simplifying the installation process and ensuring smoother updates.
The text was updated successfully, but these errors were encountered: