Allow single-platform macOS apps #1482
Labels
enhancement
New features, or improvements to existing features.
good first issue
Is this your first time contributing? This could be a good place to start!
macOS
The issue relates to Apple macOS support.
What is the problem or limitation you are having?
With the addition of #1475, macOS apps are guaranteed to be universal, regardless of whether the wheels supplying binary components are universal.
However, there are legitimate use case for not producing universal binaries:
The last 2 points points in particular will only increase in frequency over time, as x86_64 macOS machines become increasingly uncommon.
Briefcase should allow an app to specify that it should not build a universal app.
Describe the solution you'd like
A new option,
universal_build
, honored by the macOS backends. The default value isTrue
for now; new apps templates should include an explicit value for this setting. At some point in the future, this default will be changed toFalse
, and then the setting will be deprecated completely.The current (post-#1475) behavior should continue if
universal_build==True
. If the user specifiesuniversal_build=False
, the older pre-#1475 pip install behavior should be restored (i.e., only wheels that match the current platform will be installed)Describe alternatives you've considered
Do nothing, and force all apps to be universal.
Additional context
Updates to the macOS App and macOS Xcode templates will also be required to set the new value explicitly.
The text was updated successfully, but these errors were encountered: