-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Provide a way for build files to set compatibility_version and current_version #3555
Labels
Milestone
Comments
nirbheek
added
OS:macos
Issues specific to Apple Operating Systems like MacOS and iOS
install targets
labels
May 9, 2018
nirbheek
added a commit
that referenced
this issue
Aug 29, 2018
We now use the soversion to set compatibility_version and current_version by default. This is the only sane thing we can do by default because of the restrictions on the values that can be used for compatibility and current version. Users can override this value with the `darwin_versions:` kwarg, which can be a single value or a two-element list of values. The first one is the compatibility version and the second is the current version. Fixes #3555 Fixes #1451
nirbheek
added a commit
that referenced
this issue
Aug 29, 2018
We now use the soversion to set compatibility_version and current_version by default. This is the only sane thing we can do by default because of the restrictions on the values that can be used for compatibility and current version. Users can override this value with the `darwin_versions:` kwarg, which can be a single value or a two-element list of values. The first one is the compatibility version and the second is the current version. Fixes #3555 Fixes #1451
nirbheek
added a commit
that referenced
this issue
Aug 29, 2018
We now use the soversion to set compatibility_version and current_version by default. This is the only sane thing we can do by default because of the restrictions on the values that can be used for compatibility and current version. Users can override this value with the `darwin_versions:` kwarg, which can be a single value or a two-element list of values. The first one is the compatibility version and the second is the current version. Fixes #3555 Fixes #1451
dcbaker
pushed a commit
to dcbaker/meson
that referenced
this issue
Sep 4, 2018
We now use the soversion to set compatibility_version and current_version by default. This is the only sane thing we can do by default because of the restrictions on the values that can be used for compatibility and current version. Users can override this value with the `darwin_versions:` kwarg, which can be a single value or a two-element list of values. The first one is the compatibility version and the second is the current version. Fixes mesonbuild#3555 Fixes mesonbuild#1451
iMichka
added a commit
to iMichka/homebrew-core
that referenced
this issue
Aug 24, 2019
meson-internal was introduced in Homebrew#25667 A patch was proposed upstream in mesonbuild/meson#2577, but never merged. It looks like the issues were fixed by mesonbuild/meson#3555 mesonbuild/meson#3691 mesonbuild/meson#3356 Now that we are one year later, and things have settled down, try to use meson everywhere and drop meson-internal, which is outdated.
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Carrying over the discussion from #3550 (comment).
The text was updated successfully, but these errors were encountered: