(not currently active) Ted Mielczarek Reporter
	Description • 9 years ago

Once I get all my patches landed (bug 1163827) I'd like to get a CI build for gecko-ios. The requirements here are pretty minimal--just a build, no buildsymbols or tests or even uploading the build is necessary, we just want to ensure it doesn't get broken.

I know Mac builder capacity is an issue, which could be a sticking point. One thing we could do would be to use this as a test for the Linux->Mac cross compile setup, since we should be able to build iOS binaries with a Linux clang without a problem, and we don't need to deal with the symbols or packaging, which were where we stalled out with desktop OS X builds.

	Chris Cooper [:coop] (he/him)
	Comment 1 • 9 years ago

(In reply to Ted Mielczarek [:ted.mielczarek] from comment #0)
> I know Mac builder capacity is an issue, which could be a sticking point.
> One thing we could do would be to use this as a test for the Linux->Mac
> cross compile setup, since we should be able to build iOS binaries with a
> Linux clang without a problem, and we don't need to deal with the symbols or
> packaging, which were where we stalled out with desktop OS X builds.

Yes, it would be ideal if we could target this for cross-compilation from the get-go.

	Chris Cooper [:coop] (he/him)
	Comment 2 • 8 years ago

Ted: do you still want this?

	(not currently active) Ted Mielczarek Reporter
	Comment 3 • 8 years ago

Yes, but when I get around to it it's likely to just be a cross-compiled build on Taskcluster, so this should be entirely on my plate.

	Bogdan Crisan [:bcrisan] (EEST - GMT + 3)
	Comment 4 • 6 years ago

Do we still need this or it has been implemented already and no update for this particular bug?

	(not currently active) Ted Mielczarek Reporter
	Comment 5 • 6 years ago

I don't think we're going to do this.