![[ChimeraX Issue Tracking System]](/trac/ChimeraX/chrome/site/ChimeraX-icon.svg){kind=icon}
Opened 3 years ago
#7495 assigned enhancement
Make bundle_builder set MACOSX_DEPLOYMENT_TARGET
| Reported by: | Tristan Croll | Owned by: | Greg Couch |
|---|---|---|---|
| Priority: | moderate | Milestone: | |
| Component: | Build System | Version: | |
| Keywords: | Cc: | chimerax-programmers | |
| Blocked By: | Blocking: | ||
| Notify when closed: | Platform: | all | |
| Project: | ChimeraX |
Description
Tristan asks in ticket #4663 (Mac M1 port) comment 70 whether he needs to set MACOSX_DEPLOYMENT_TARGET when building ISOLDE for distribution. On ARM Mac it should be 11.0 and on Intel Mac it should be 10.14 for our current distributions.
Maybe bundle builder already does this when compiling code.
I am not sure we want it to do this by default, maybe it could be an option, because plugin developers may not have the 11.0 or 10.14 SDKs installed with Xcode and it will put them to some trouble to figure out how to get those when they are first trying to compile a plugin. Might be better if bundle builder looked at whether those Mac SDKs are available and if not don't set MACOSX_DEPLOYMENT_TARGET and warn that the older SDKs were not found so the compiled plugin won't be compatible with older macOS and maybe provide a link how to get those SDKs.
