diff options
| author | Randy Eckenrode <randy@largeandhighquality.com> | 2024-02-04 13:07:09 -0500 |
|---|---|---|
| committer | Randy Eckenrode <randy@largeandhighquality.com> | 2024-03-29 10:07:50 -0400 |
| commit | 71c6ee929561c149c81f3511697b1d43c6fbb1d8 (patch) | |
| tree | 78ea8fa6b2c16de8ceb58a4545c3002006ee7b10 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | f61e189ad369d873d247a6db01370732b4f6bf39 (diff) | |
darwin.stdenv: add sdkRoot to extraNativeBuildInputs
Setting the SDK root by default allows `overrideSDK` to correctly set
the SDK version when using a different SDK. It also allows the correct
SDK version to be set when using an older deployment target. Not setting
the correct SDK version can result in unexpected behavior at runtime.
Examples:
* Automatic dark mode switching requires linking against an SDK version
of 10.14 or newer. With the current behavior, the only way to do this
is by using a 10.14+ deployment target even when the application
supports older platforms when build with a newer SDK.
* MetalD3D checks that the system version is at least 14.0. The API it
uses returns a compatibility version when the the SDK is older than
11.0, which causes it to display an error and terminate the
application even when even when its requirements are all met.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions