Enable building Skia for iOS with bazel.

Enable building Skia for iOS with bazel.

BUG=skia:

Committed: https://skia.googlesource.com/skia/+/8b99ef434736791eefb31ecaa590a649dff83aed

[iroth, 2015-10-30 21:41:50]

iroth@google.com changed reviewers:
+ benjaminwagner@google.com, mtklein@google.com

[mtklein, 2015-11-02 13:56:03]

Ben, remind me how we best do this?  Land the skia/ change first?  Land the
Google3 change in its entirety then backport BUILD.public and .cpp changes to
Skia? Something else?

[dogben, 2015-11-02 14:07:35]

On 2015/11/02 at 13:56:03, mtklein wrote:
> Ben, remind me how we best do this?  Land the skia/ change first?  Land the
Google3 change in its entirety then backport BUILD.public and .cpp changes to
Skia? Something else?

In the general case:
1. Run 'g4 presubmit' on the combined CL, then move Git-only files out of the CL
('g4 revert' or 'g4 reopen -c default').
2. Send for review and get approval for both CLs.
3. Commit to Git via CQ (i.e. the button at the top of this page).
4. Submit the Piper CL with 'g4 submit -f'.
5. Launch the autoroller at
https://borgcron-atlanta.corp.google.com/job?name=skia/autoroller.borgcron.bo...
6. If the autoroller fails, revert both CLs and try again.

In this case, since the Piper CL can stand on its own (i.e. g4 presubmit
passes), I would submit to Piper first and just let the autoroller pick up the
Git change in the nightly run (or launch it manually if I have dependent
changes).

iroth, I can do step 5 for you, since you don't have permission.

[dogben, 2015-11-02 14:10:22]

On 2015/11/02 at 14:07:35, Ben Wagner wrote:
> On 2015/11/02 at 13:56:03, mtklein wrote:
> > Ben, remind me how we best do this?  Land the skia/ change first?  Land the
Google3 change in its entirety then backport BUILD.public and .cpp changes to
Skia? Something else?
> 
> In the general case:
> 1. Run 'g4 presubmit' on the combined CL, then move Git-only files out of the
CL ('g4 revert' or 'g4 reopen -c default').
> 2. Send for review and get approval for both CLs.
> 3. Commit to Git via CQ (i.e. the button at the top of this page).
> 4. Submit the Piper CL with 'g4 submit -f'.
> 5. Launch the autoroller at
https://borgcron-atlanta.corp.google.com/job?name=skia/autoroller.borgcron.bo...
> 6. If the autoroller fails, revert both CLs and try again.
> 
> In this case, since the Piper CL can stand on its own (i.e. g4 presubmit
passes), I would submit to Piper first and just let the autoroller pick up the
Git change in the nightly run (or launch it manually if I have dependent
changes).
> 
> iroth, I can do step 5 for you, since you don't have permission.

We could consider doing the backport approach too, but I'm not sure that's a
good idea long-term, if we are thinking of triggering the autoroller after each
commit.

[mtklein, 2015-11-02 18:28:17]

lgtm

[iroth, 2015-11-02 19:00:32]

The CQ bit was checked by iroth@google.com

[commit-bot: I haz the power, 2015-11-02 19:00:43]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1429863002/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1429863002/20001

[commit-bot: I haz the power, 2015-11-02 19:11:24]

Committed patchset #2 (id:20001) as
https://skia.googlesource.com/skia/+/8b99ef434736791eefb31ecaa590a649dff83aed

[dogben, 2015-11-02 20:21:23]

On 2015/11/02 at 19:11:24, commit-bot wrote:
> Committed patchset #2 (id:20001) as
https://skia.googlesource.com/skia/+/8b99ef434736791eefb31ecaa590a649dff83aed

Rolled to google3 at cl/106862369.