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

ios: Add CocoaPods support #125

Closed
rebello95 opened this issue Jun 17, 2019 · 2 comments · Fixed by #431
Closed

ios: Add CocoaPods support #125

rebello95 opened this issue Jun 17, 2019 · 2 comments · Fixed by #431
Assignees
Labels
help wanted platform/ios Issues related to iOS
Milestone

Comments

@rebello95
Copy link
Contributor

Adding support for CocoaPods will make integrating Envoy Mobile very straightforward on iOS and will be a good driver for adoption.

@rebello95 rebello95 added help wanted platform/ios Issues related to iOS labels Jun 17, 2019
@rebello95 rebello95 added this to the v0.2 "Primo" milestone Jun 17, 2019
@cwalo
Copy link
Contributor

cwalo commented Sep 5, 2019

@rebello95 feel free to assign this one to me

@rebello95
Copy link
Contributor Author

Thanks @cwalo!

rebello95 pushed a commit that referenced this issue Sep 13, 2019
This adds a new `EnvoyMobile.podspec` (unfortunately, "Envoy" is already taken). On `pod install` Cocoapods will download the latest prebuilt framework at /releases unless a specific version is defined in the Podfile. 

Once this is merged, we'll need to publish our podspec to the Cocoapods trunk. Moving forward, we'll also need to update the version listed in the podspec during the release process. 

Description: Adds Cocoapods support for distributing the prebuilt Envoy.framework
Risk Level: Low
Testing: Clone the [test project](https://github.com/cwalo/EnvoyTest) and with this branch checked out locally, run `pod install`. Be sure the two repos sit in the same parent directory (or update the podspec path in the Podfile). 
Docs Changes: Yes
Release Notes: No
Fixes: [#125](#125)
jpsim pushed a commit to envoyproxy/envoy that referenced this issue Nov 28, 2022
This adds a new `EnvoyMobile.podspec` (unfortunately, "Envoy" is already taken). On `pod install` Cocoapods will download the latest prebuilt framework at /releases unless a specific version is defined in the Podfile.

Once this is merged, we'll need to publish our podspec to the Cocoapods trunk. Moving forward, we'll also need to update the version listed in the podspec during the release process.

Description: Adds Cocoapods support for distributing the prebuilt Envoy.framework
Risk Level: Low
Testing: Clone the [test project](https://github.com/cwalo/EnvoyTest) and with this branch checked out locally, run `pod install`. Be sure the two repos sit in the same parent directory (or update the podspec path in the Podfile).
Docs Changes: Yes
Release Notes: No
Fixes: [#125](envoyproxy/envoy-mobile#125)

Signed-off-by: JP Simard <[email protected]>
jpsim pushed a commit to envoyproxy/envoy that referenced this issue Nov 29, 2022
This adds a new `EnvoyMobile.podspec` (unfortunately, "Envoy" is already taken). On `pod install` Cocoapods will download the latest prebuilt framework at /releases unless a specific version is defined in the Podfile.

Once this is merged, we'll need to publish our podspec to the Cocoapods trunk. Moving forward, we'll also need to update the version listed in the podspec during the release process.

Description: Adds Cocoapods support for distributing the prebuilt Envoy.framework
Risk Level: Low
Testing: Clone the [test project](https://github.com/cwalo/EnvoyTest) and with this branch checked out locally, run `pod install`. Be sure the two repos sit in the same parent directory (or update the podspec path in the Podfile).
Docs Changes: Yes
Release Notes: No
Fixes: [#125](envoyproxy/envoy-mobile#125)

Signed-off-by: JP Simard <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted platform/ios Issues related to iOS
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants