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

Update CI to Xcode 15.1 on macos 13.0 #818

Conversation

karim-alweheshy
Copy link
Contributor

@karim-alweheshy karim-alweheshy commented Dec 26, 2023

Updated CI runners to macos-13
Update Xcode to 15.1.0 from 14.2.0
Update min iOS version to 12.0 from 10.0 and 11.0 and remove Host-App pre 12.0
Updated iOS sdk to 17.2 and devices to sims from the runner
Update swift_version from 5.1 to 5.9
Update xcodeproj installer, as it was pointing to a static lib for dynamic lib compilation and fixed path to remove //
Updated compile frameworks to the correct arch ios-sim-arm64-x86_64
Updated third party libs to be on the right arch ios-sim-arm64-x86_64

@karim-alweheshy karim-alweheshy changed the title Update CI to Xcode 15.1 on macos 14.2 Update CI to Xcode 15.1 on macos 13.0 Dec 26, 2023
@karim-alweheshy karim-alweheshy marked this pull request as ready for review December 26, 2023 13:56
…mic libs

otherwise point to the .zip file so it can be unzipped and unpack the dylib .framework. before this solution it points to the static .framework
@karim-alweheshy karim-alweheshy marked this pull request as draft December 28, 2023 07:32
@karim-alweheshy karim-alweheshy marked this pull request as ready for review December 28, 2023 07:32
@karim-alweheshy
Copy link
Contributor Author

A step for bazel 7 migration

Copy link
Collaborator

@luispadron luispadron left a comment

Choose a reason for hiding this comment

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

The xcspec changes / ci look good to me.

I'm not sure about the project changes though, it seems like the path was broken? @thiagohmcruz @jerrymarino

Copy link
Collaborator

Choose a reason for hiding this comment

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

Was this change intentional? Seems to break the path

Copy link
Contributor Author

Choose a reason for hiding this comment

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

without this path change it was pointing to a static framework when it should point to the dynamic framework. This dynamic framework can at times be compressed into a zip i.e. doesn't exist yet on disk. in that case i added the zip to be unzipped later in the same script

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.

2 participants