Pull necessary dependencies to be able to process mojo.gyp on iOS

Pull necessary dependencies to be able to process mojo.gyp on iOS

This CL adds support for building the Mojo core system and C++ bindings-related
targets on iOS. It also adds necessary dependencies such that mojo.gyp can
be processed on iOS.

This CL also rolls DEPS on libjpeg_turbo to catch a change to libjpeg.gyp
that is needed in order for gyp to avoid choking when processing the file
on iOS.

[blundell, 2014-07-10 09:52:04]

Hi James,

How does this CL look? Note that the iOS bots are red because the CL depends on
a minor change in a gypfile in another repo; I've verified locally that this
works on iOS.

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp
File mojo/mojo.gyp (right):

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp#newcode28
mojo/mojo.gyp:28: 'target_name': 'mojo',
I'd really like to be able to build mojo.gyp:mojo in all.gyp on iOS rather than
a hardcoded list of targets, as there's no chance that that hardcoded list would
be updated when people add new Mojo targets that are relevant on iOS.

[jamesr, 2014-07-10 22:28:22]

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp
File mojo/mojo.gyp (right):

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp#newcode28
mojo/mojo.gyp:28: 'target_name': 'mojo',
On 2014/07/10 09:52:04, blundell wrote:
> I'd really like to be able to build mojo.gyp:mojo in all.gyp on iOS rather
than
> a hardcoded list of targets, as there's no chance that that hardcoded list
would
> be updated when people add new Mojo targets that are relevant on iOS.

As an author, how am I supposed to know which section to put a new target in?

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo_public.gypi
File mojo/mojo_public.gypi (right):

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo_public.gypi#ne...
mojo/mojo_public.gypi:98: 'type': 'static_library',
hmm, why?

[blundell, 2014-07-11 14:29:49]

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp
File mojo/mojo.gyp (right):

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo.gyp#newcode28
mojo/mojo.gyp:28: 'target_name': 'mojo',
What we've done in other gypfiles is put a comment saying "New dependencies
should generally go in the !iOS section below." I can understand your concern.
If you're really opposed to this, I could put the list in lines 31-44 into
all.gyp on iOS (especially because given that comment, presumably all
dependencies end up in the !iOS section unless the author knows specifically
that they're intended for iOS as well).

On 2014/07/10 22:28:22, jamesr wrote:
> On 2014/07/10 09:52:04, blundell wrote:
> > I'd really like to be able to build mojo.gyp:mojo in all.gyp on iOS rather
> than
> > a hardcoded list of targets, as there's no chance that that hardcoded list
> would
> > be updated when people add new Mojo targets that are relevant on iOS.
> 
> As an author, how am I supposed to know which section to put a new target in?

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo_public.gypi
File mojo/mojo_public.gypi (right):

https://codereview.chromium.org/376573003/diff/20001/mojo/mojo_public.gypi#ne...
mojo/mojo_public.gypi:98: 'type': 'static_library',
Apps can't load shared libraries on iOS :\.

On 2014/07/10 22:28:22, jamesr wrote:
> hmm, why?

[blundell, 2014-07-15 14:22:49]

Hi James,

Could you review PS1? The only difference between that and PS2 is that PS1 lists
the Mojo targets used by iOS explicitly in all.gyp.

[jamesr, 2014-07-17 20:53:37]

ps1 seems ok, although as soon as you have a real target using these things you
can remove those from the root build target, right?

lgtmish

[blundell, 2014-07-25 10:28:18]

Thanks. Yes, as we start to pull in these dependencies from things that are
already built as part of "All" on iOS we can remove them from being explicitly
in the "All" list.

jochen@, can you review //content? Thanks!

[jochen (gone - plz use gerrit), 2014-07-28 09:23:11]

lgtm