Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/website/mmp-errors.md
Original file line number Diff line number Diff line change
Expand Up @@ -221,8 +221,6 @@ Consider updating your application and any dependencies to 64-bit.

### <a name="MM202x"/>MM202x: Binding Optimizer failed processing `...`.

### <a name="MM2100"/>MM2100: Xamarin.Mac Classic API does not support Platform Linking.

### <a name="MM2103"/>MM2103: Error processing assembly '\*': *

An unexpected error occured when processing an assembly.
Expand Down Expand Up @@ -268,6 +266,8 @@ This is in general safe, and will reduce application bundle size as an added ben

Consider using `lipo` to remove the unnecessary archtectures permanently from the source library. If the application is not being published to the App Store, this removal can be disabled by passing --optimize=-trim-architectures as Additional MMP Arguments.

### <a name="MM2109"/>MM2109: Xamarin.Mac Classic API does not support Platform Linking.


# MM3xxx: AOT

Expand Down
2 changes: 1 addition & 1 deletion tools/mmp/driver.cs
Original file line number Diff line number Diff line change
Expand Up @@ -462,7 +462,7 @@ static void Main2 (string [] args)
throw new MonoMacException (1404, true, "Target framework '{0}' is invalid.", userTargetFramework);

if (IsClassic && App.LinkMode == LinkMode.Platform)
throw new MonoMacException (2100, true, "Xamarin.Mac Classic API does not support Platform Linking.");
throw new MonoMacException (2109, true, "Xamarin.Mac Classic API does not support Platform Linking.");

// sanity check as this should never happen: we start out by not setting any
// Unified/Classic properties, and only IsUnifiedMobile if we are are on the
Expand Down