Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge xcode9 into master #2707

Merged
merged 367 commits into from
Sep 16, 2017
Merged

Merge xcode9 into master #2707

merged 367 commits into from
Sep 16, 2017

Conversation

spouliot
Copy link
Contributor

No description provided.

chamons and others added 30 commits July 21, 2017 11:25
There's no header change to mention `init` is not allowed but
it's not clear how this default initializer could be used.

Also make public some other API to construct this type (outside
of XM). It's not clear why there were `internal` as they are
(at least now) part of the header files.
…ll (to avoid ambiguous API) (xamarin#2360)

Adding a strongly typed `PHLivePhotoEditingOption` (a strongly typed
version of an `NSDictionary`) can cause a `CS0121` (call is ambiguous)
since using a `null` argument is common (only one option exist so far).

This PR adds overloads that makes the code nicer in such case, e.g.

before Xcode9:

> // null is used when no options are given
> _foo.SaveLivePhoto (output, null, completion);

current (Xcode 9)

> // casting required to remove ambiguity with PHLivePhotoEditingOption
> _foo.SaveLivePhoto (output, (NSDictionary)null, completion);

with this PR

> // no option, no argument
> _foo.SaveLivePhoto (output, completion);

The same applies to `PrepareLivePhotoForPlayback`.
…ates

Those tests were not added to validate xOS so just keep the parts
that helps us (without constantly checking back the new break flavor)
Note: WKWindowFeatures.h is not compiled (part of the framework umbrella)
and the `@interface WKWindowFeatures (WKPrivate)` sounds like it should
not have been exposed (it's all fields starting with `_`)
…s-tests-58348

[tests] Disable watchOS from harness only. Workaround #58348
…arin#2376)

This fix is needed by PDFKit because it is a remapped framework[0],
the current code generates incorrect FieldAttribute on smart enums
because it uses `fa.LibraryName` as first option and this causes
remmaped frameworks have incorrect LibraryName generated for example
if a Field uses `+CoreImage` as `LibraryName` the following incorrect
code is generated:

```
	[Field ("First", "+CoreImage")]
	internal unsafe static IntPtr First {
		get {
			fixed (IntPtr *storage = &values [0])
				return Dlfcn.CachePointer (Libraries.+CoreImage.Handle, "First", storage);
		}
	}
```

[0]: https://github.com/xamarin/xamarin-macios/blob/f5956d6cc1eb5dfa7bab16628cf282d40237f64e/src/generator.cs#L5985
Make.config Outdated
@@ -30,28 +31,31 @@ PACKAGE_HEAD_REV=$(shell git rev-parse HEAD)
# on wrench, because wrench technically builds hashes, not branches)
#
#
PACKAGE_HEAD_BRANCH=master
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This shouldn’t be merged in master.

Make.config Outdated
IOS_PRODUCT=Xamarin.iOS
IOS_PACKAGE_NAME=Xamarin.iOS
IOS_PACKAGE_NAME_LOWER=$(shell echo $(IOS_PACKAGE_NAME) | tr "[:upper:]" "[:lower:]")
# NEVER customize IOS_PACKAGE_VERSION itself, other parts (mtouch, web updater) are using the IOS_PACKAGE_VERSION_* variables
IOS_PACKAGE_VERSION=10.15.0.$(IOS_COMMIT_DISTANCE)
IOS_PACKAGE_VERSION=11.5.$(PACKAGE_VERSION_REV).$(IOS_COMMIT_DISTANCE)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

11.5 doesn’t look right 😃

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

xcode9 (d15.3/stable) -> 11.0
d15-4-xi -> 11.2
d15-5 -> 11.4
master -> 11.5

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@rolfbjarne the final will like @VincentDondain mentioned
but yes I skipped a step ;-) since d15-5 (11.4) will be branched after the merge

Make.config Outdated
XCODE_VERSION=8.3
XCODE_URL=http://xamarin-storage/bot-provisioning/Xcode_8.3.xip
XCODE_DEVELOPER_ROOT=/Applications/Xcode83.app/Contents/Developer
# Xcode 9 beta 6
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor but comment is wrong :P

- branch name was still pointing to `xcode9`, not `master`

- version was 11.5, half true since we need to re-branch 15.5 (11.4), so down to 11.3 to be temporarily correct

- remove useless comment about xcode version, both the path and download link include the version
@monojenkins
Copy link
Collaborator

Build failure

1 similar comment
@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

@monojenkins
Copy link
Collaborator

Build failure

@spouliot
Copy link
Contributor Author

watchOS failure (no mono.security) -> https://bugzilla.xamarin.com/show_bug.cgi?id=57529
emptiest webkit is absent -> https://bugzilla.xamarin.com/show_bug.cgi?id=59539

@spouliot spouliot merged commit 67f4130 into xamarin:master Sep 16, 2017
@spouliot spouliot deleted the xcode9-master-merge branch September 16, 2017 00:27
@spouliot spouliot restored the xcode9-master-merge branch September 16, 2017 14:53
spouliot added a commit that referenced this pull request Sep 16, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.