-
Notifications
You must be signed in to change notification settings - Fork 166
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
mac build wanted for v1.04 #315
Comments
I have a milkytracker-1.04.00-Darwin.dmg built with the script above. Let me know how I can get it to you. |
You were fast |
awesome! thank you very much!
I will attach it to the current release afterwards |
https://filebin.net/vs4n20wtx6plbfui Built on macOS 12.6.7 x86 |
thank you! x86 means 32bit right? |
Sorry, x64, it's a 64-bit build. |
Xcode no longer supports building 32 bit Intel binaries for macOS. But then again, having a universal or an arm64 build, that would be nice 😉 |
@coderofsalvation the first channel scope background is grey, is that a new feature or did a find a bug? |
I was able to produce an arm64 binary. Upload to filebin as well? Unfortunately I don't use this software so I can't work with it in depth, but installs/functions/seems to work ok - playing the sample tracks work. Built on macOS Ventura 13.4.1 and Xcode 14.3.1 |
@coderofsalvation - Filebin seems to be restricting uploads due to over capacity. Do you have another preferred file service? Else I can upload to GoFile or an alternate service. Or perhaps I can attach here? |
GoFile is also fine, it's just temporary so I can download it |
I'll also take care of updating the macOS Homebrew cask once both versions are posted. |
Thanks to you @krehel @johngirvin for empowering other mac users ❤ |
@coderofsalvation - I am really sorry! The arm64 build may cause issues for users as macOS may report the software as damaged due to not being signed/notarized due to policy. How do you want to handle this? I suppose I could do those steps, but since I'm not a part of your team I am not sure that is appropriate or desired. Calling this out now before any issues may start to get opened. I didn't notice this because my local build copy worked, and the GitHub download did not despite being the same sha256. I had to run The Point being, providing the information so you can best decide how you want to proceed - if getting the ARM version signed/notarized, or just simply run the |
Same, let me know what you need to do for the x86_64 build. |
Well, for macOS I guess somebody "official" would need to register an official Apple developer account which we can use to sign the binaries, so they can be run without any restrictions. Unfortunately the membership is not free, I believe it's $99 per year. |
First of all I'd like to thank everybody in this thread for their efforts & thinking along ♥ Ok, well as a starter I've mentioned the workarounds on the downloads-page (website) and the release. The 'official' direction perhaps starts making more sense when donations exceed $99 p/year? |
|
thanks (updated docs) |
I spent some time yesterday trying to figure this out and I was able to ad-hoc sign the binary. Working in CMake and all this is not my strong suit. 😃 But, signing can be done without an official Apple developer account and spending the $99. I'm going to keep working on this a bit more to make sure what is being produced will work. Apologies for the extra overhead and hassle. |
that is awesome news @krehel !
same here, welcome to the club ;) |
@coderofsalvation - I added you to a private repository for the signed ARM build. Figured it might be better than scattering files across services. I set a release with the latest file I built. |
Yes, ad-hoc signing is possible, but IMO not the recommended way for software that is to be released: |
Just a note, whoever is doing the Mac builds can make universal binary builds with the |
anyone in this issue, please consider doing the same magic for the latest release: #341 |
can somebody provide/compile binaries (any macos version welcome) which we can attach to the latest release? ❤️
(@peterbart-lmi ?)
The text was updated successfully, but these errors were encountered: