I'm working on some code that uses the gyp build system. I find that
there are cases where I want to aggregate several libraries into a
single library target so other clients can depend on one "public"
library target instead of having to reference a bunch of individual
library targets. For instance I might have:
'targets': [
{
'target_name': 'foo',
'dependencies': [
some deps here
],
'sources': [
some sources here
]
},
{
'target_name': 'bar',
'dependencies': [
some deps here
],
'sources': [
some sources here
]
},
{
'target_name': 'public',
'dependencies': [
'foo',
'bar',
],
},
]
I then have consumers of my library depend on the 'public' target
rather than depending on 'foo' and 'bar'
This actually works fine on Linux and Windows builds, but on OS X
using xcodebuild, my builds fail with:
libpublic.a: No such file or directory
Is there some way to get the xcodebuilds to properly build these stub
libraries that don't have any source files? Does the gyp->xcode
generation code need to change to support this?
--~--~---------~--~----~------------~-------~--~----~
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
-~----------~----~----~----~------~----~------~--~---
