Why does each new version of Bitcoin Core require a newer version of macOS? Could it be due to XCode updates or other development factors?
Because Apple's gonna Apple.
Topic: Bitcoin Core 25.1 Released (Read 373 times)
Because Apple's gonna Apple.
Why does each new version of Bitcoin Core require a newer version of macOS? Could it be due to XCode updates or other development factors?
Quick question about the macOS build.
Over time, it seems that the more recent builds of Bitcoin Core require a newer and newer version of macOS to run. Is this because you guys are building against a newer XCode, or has it stayed the same all these years?
By comparison, the Windows and Linux builds have an excellent lifecycle.
Over time, it seems that the more recent builds of Bitcoin Core require a newer and newer version of macOS to run. Is this because you guys are building against a newer XCode, or has it stayed the same all these years?
By comparison, the Windows and Linux builds have an excellent lifecycle.
Im not familiar with macOS at all or anything Apple for that matter but it probably has to do with lack of backward compatibility with some libraries or something. Considering how the whole Apple stock depends on short lived newer models being bought and replaced. This guy here said on stackexchange:
Quote
The Windows code-base is all about backwards compatibility, some apps from Windows 1.0 continue to work just fine, as you can even run 16-bit apps in Windows 10 if you need to. macOS has a different philosophy, Apple burns the underbrush and cleans house on certain compatibility stubs on a regular basis. A Mac app from 2012 probably won't run today unless recompiled 64-bit, yet a Windows app from 1992 might run just fine.
Wouldn't recommend running anything Bitcoin outside of Linux anyway.
Quick question about the macOS build.
Over time, it seems that the more recent builds of Bitcoin Core require a newer and newer version of macOS to run. Is this because you guys are building against a newer XCode, or has it stayed the same all these years?
By comparison, the Windows and Linux builds have an excellent lifecycle.
Over time, it seems that the more recent builds of Bitcoin Core require a newer and newer version of macOS to run. Is this because you guys are building against a newer XCode, or has it stayed the same all these years?
By comparison, the Windows and Linux builds have an excellent lifecycle.
25.1 Release Notes
Bitcoin Core version 25.1 is now available from:
https://bitcoincore.org/bin/bitcoin-core-25.1/
This release includes various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on macOS)
or bitcoind/bitcoin-qt (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
Notable changes
P2P
Fees
RPC
Rest
Wallet
Build
Gui
Miscellaneous
CI
Credits
Thanks to everyone who directly contributed to this release:
As well as to everyone that helped with translations on
Transifex.
Bitcoin Core version 25.1 is now available from:
https://bitcoincore.org/bin/bitcoin-core-25.1/
This release includes various bug fixes and performance
improvements, as well as updated translations.
Please report bugs using the issue tracker at GitHub:
https://github.com/bitcoin/bitcoin/issues
To receive security and update notifications, please subscribe to:
https://bitcoincore.org/en/list/announcements/join/
How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes in some cases), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on macOS)
or bitcoind/bitcoin-qt (on Linux).
Upgrading directly from a version of Bitcoin Core that has reached its EOL is
possible, but it might take some time if the data directory needs to be migrated. Old
wallet versions of Bitcoin Core are generally supported.
Compatibility
Bitcoin Core is supported and extensively tested on operating systems
using the Linux kernel, macOS 10.15+, and Windows 7 and newer. Bitcoin
Core should also work on most other Unix-like systems but is not as
frequently tested on them. It is not recommended to use Bitcoin Core on
unsupported systems.
Notable changes
P2P
- #27626 Parallel compact block downloads, take 3
- #27743 p2p: Unconditionally return when compact block status == READ_STATUS_FAILED
Fees
- #27622 Fee estimation: avoid serving stale fee estimate
RPC
- #27727 rpc: Fix invalid bech32 address handling
Rest
- #27853 rest: fix crash error when calling /deploymentinfo
- #28551 http: bugfix: allow server shutdown in case of remote client disconnection
Wallet
- #28038 wallet: address book migration bug fixes
- #28067 descriptors: do not return top-level only funcs as sub descriptors
- #28125 wallet: bugfix, disallow migration of invalid scripts
- #28542 wallet: Check for uninitialized last processed and conflicting heights in MarkConflicted
Build
- #27724 build: disable boost multi index safe mode in debug mode
- #28097 depends: xcb-proto 1.15.2
- #28543 build, macos: Fix qt package build with new Xcode 15 linker
- #28571 depends: fix unusable memory_resource in macos qt build
Gui
- gui#751 macOS, do not process actions during shutdown
Miscellaneous
- #28452 Do not use std::vector = {} to release memory
CI
- #27777 ci: Prune dangling images on RESTART_CI_DOCKER_BEFORE_RUN
- #27834 ci: Nuke Android APK task, Use credits for tsan
- #27844 ci: Use podman stop over podman kill
- #27886 ci: Switch to amd64 container in "ARM" task
Credits
Thanks to everyone who directly contributed to this release:
- Abubakar Sadiq Ismail
- Andrew Chow
- Bruno Garcia
- Gregory Sanders
- Hennadii Stepanov
- MacroFake
- Matias Furszyfer
- Michael Ford
- Pieter Wuille
- stickies-v
- Will Clark
As well as to everyone that helped with translations on
Transifex.
Jump to: