Bug 60974 - Allow customization of libraries linked / ignored in final clang invocation and smartly parse Info.plist
Summary: Allow customization of libraries linked / ignored in final clang invocation a...
Alias: None
Product: Xamarin.Mac
Classification: Desktop
Component: mmp ()
Version: Master
Hardware: PC Mac OS
: --- enhancement
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2017-12-04 20:02 UTC by Chris Hamons
Modified: 2017-12-06 17:33 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report for Bug 60974 on Developer Community or GitHub if you have new information to add and do not yet see a matching new report.

If the latest results still closely match this report, you can use the original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:

Description Chris Hamons 2017-12-04 20:02:23 UTC
There are some cases like this where hard references are required to pass Apple validation:


and a number (like the QTKit issues) where references are forbidden to pass Apple validation.

We should add a feature to mmp to allow customization of this. Something like:


which overrides the logic here:


Also, a few cases like MapKit could be handled if we parsed the info.plist.
Comment 1 Alain 2017-12-05 08:57:00 UTC
I'm really sorry. I don't use Bugzilla as support but since I detect a bug, I post the bug via this subsidiary.

Normally, I don't need an immediate answer but here it's really very annoying because I can't post my application now.

Moreover, I don't understand because the solution you gave me a month ago to work and now more. As I said, the only difference is that I was in Xamarin.Mac 3.8 instead of 4.0. Can this be the problem ?

Can I get back to 3.8 without this being a problem in my application ?

Do I have to remove Maps to post my app now ?

Thanks for your help

Comment 2 Timothy Risi 2017-12-06 17:33:34 UTC
@Alain as long as you are not using any new APIs added in XM 4.0 (High Sierra APIs) there should be no problem with going back to XM 3.8 until we can fix whatever is causing the problem.