summaryrefslogtreecommitdiff
path: root/test/toolsets/toolsets.gyp
diff options
context:
space:
mode:
authorthakis@chromium.org <thakis@chromium.org@78cadc50-ecff-11dd-a971-7dbc132099af>2012-03-14 16:04:11 +0000
committerthakis@chromium.org <thakis@chromium.org@78cadc50-ecff-11dd-a971-7dbc132099af>2012-03-14 16:04:11 +0000
commit299eb63862f16469aa6548d0d947f930fa756de7 (patch)
tree82e97ef15bc22413140c558fc744e4c3488b79e4 /test/toolsets/toolsets.gyp
parent20076770ec90e5e4dab81a3d34cca8346108bf59 (diff)
downloadgyp-299eb63862f16469aa6548d0d947f930fa756de7.tar.gz
mac make: Don't put host shared libraries into the product directory.
With the components build, but host and target create a libbase.dylib. With the old code, both would end up directly in out/Release, creating conflicting build rules for out/Release/libbase.dylib. Instead, let the host version go into out/Release/obj.host/base/libbase.dylib BUG=chromium:90078 Review URL: https://chromiumcodereview.appspot.com/9700021 git-svn-id: http://gyp.googlecode.com/svn/trunk@1245 78cadc50-ecff-11dd-a971-7dbc132099af
Diffstat (limited to 'test/toolsets/toolsets.gyp')
-rw-r--r--test/toolsets/toolsets.gyp10
1 files changed, 10 insertions, 0 deletions
diff --git a/test/toolsets/toolsets.gyp b/test/toolsets/toolsets.gyp
index e41b928d..286edf2f 100644
--- a/test/toolsets/toolsets.gyp
+++ b/test/toolsets/toolsets.gyp
@@ -34,5 +34,15 @@
'main.cc',
],
},
+ # This tests that build systems can handle a shared library being build for
+ # both host and target.
+ {
+ 'target_name': 'janus',
+ 'type': 'shared_library',
+ 'toolsets': ['target', 'host'],
+ 'sources': [
+ 'toolsets.cc',
+ ],
+ },
],
}