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
fluid-synth 2.1.1 #48863
fluid-synth 2.1.1 #48863
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the pull request! Almost there…
Formula/fluid-synth.rb
Outdated
| @@ -29,11 +34,18 @@ def install | |||
|
|
|||
| mkdir "build" do | |||
| system "cmake", "..", *args | |||
| system "make", "check" | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything else is OK, but please remove make check: we don't generally run compile-time tests, except for security-related formulas.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alright; I'm pushing the change now. I saw it in other formulae (probably the security-related ones you are talking about) and was curious but didn't get a response in the other PR. Thanks!
|
It looks like the build failed this time on High Sierra on the Do you have any ideas why it might be failing? Current (failing) Diff between initial PR and current: diff --git a/Users/foster/Downloads/fluid-synth.rb b/Formula/fluid-synth.rb
index eceed476..96fdb266 100644
--- a/Users/foster/Downloads/fluid-synth.rb
+++ b/Formula/fluid-synth.rb
@@ -34,7 +34,6 @@ class FluidSynth < Formula
mkdir "build" do
system "cmake", "..", *args
- system "make", "check"
system "make", "install"
end
Thanks for the help! |
|
So I rebased against master and the build seems to have passed this time. I'm not entirely sure what was up with that. Is there anything else I need to do to get this merged? Thanks again! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
|
@BrewTestBot test this please |
|
|
|
So as of last Monday FluidSynth 2.1.1 has been released (see link below). Since this PR includes more than a version bump, you can either merge this one then I can do a https://github.com/FluidSynth/fluidsynth/releases/tag/v2.1.1 What would you prefer? Thanks! |
|
If you could update this PR (title, update url, sha256 commit message) and amend the commit (or squash) and force push that would be ideal. |
|
I don't think I can give the PR a new branch name but I updated the PR title, commit message, and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your contribution to Homebrew! 🎉 🥇
Without awesome contributors like you, it would be impossible to maintain Homebrew to the high level of quality users have come to expect. Thank you @fkmclane!
brew install --build-from-source <formula>, where<formula>is the name of the formula you're submitting?brew test <formula>, where<formula>is the name of the formula you're submitting?brew audit --strict <formula>(after doingbrew install <formula>)?Following from #46793 by @Bo98, this bumps the formula to 2.1.0 (released 2019-12-01) and implements a reasonably useful test that FluidSynth was installed and succesfully runs. I additionally added a
make checkstep beforemake installsince that seems to be common for packages that have it and FluidSynth recommends doing so aftermakewhen compiling from source.See #46793 and #46793 (comment)
Thanks to @Bo98 for the idea of (and some code for) synthesizing a simple midi as a test.
I think the only potentially breaking change with 2.1.0 is that the
fluid_synth_set_sample_ratefunction in libfluidsynth has been deprecated. I'm not sure if it's commonly used, however, because the documentation says the function is broken by design and the deprecation notice says:Let me know if any changes are necessary but everything works and passes on my system. I opened a new pull request despite #46793 already being open because this bumps the version to 2.1.0 (instead of 2.0.9) and supercedes that pull request. If that isn't the right thing to do, let me know the appropriate way to get the update merged.
Thanks!