Chromium Code Reviews| OLD | NEW |
|---|---|
| (Empty) | |
| 1 # Copyright 2015 The Chromium Authors. All rights reserved. | |
|
Sergey Ulanov
2015/06/08 18:57:37
Do we really need to add this extra .gyp file? Why
tonychun
2015/06/08 20:35:58
I completely agree. This change would optimize gyp
| |
| 2 # Use of this source code is governed by a BSD-style license that can be | |
| 3 # found in the LICENSE file. | |
| 4 | |
| 5 { | |
| 6 'includes': [ | |
| 7 'remoting_version.gypi', | |
| 8 ], | |
| 9 | |
| 10 'target_defaults': { | |
|
Sergey Ulanov
2015/06/08 18:57:37
Why do you need this?
tonychun
2015/06/08 20:35:58
I thought, by default, every .gyp file requires a
| |
| 11 'type': 'none', | |
| 12 }, # target_defaults | |
| 13 'targets': [ | |
| 14 { | |
| 15 # A chromoting version of the common test driver tool | |
|
joedow
2015/06/08 18:35:20
what is the common test driver tool?
tonychun
2015/06/08 20:35:58
It is the common lib in remoting_all.gyp. I will r
| |
| 16 'target_name': 'chromoting_test_driver', | |
| 17 'type': '<(gtest_target_type)', | |
| 18 'dependencies': [ | |
| 19 '<(DEPTH)/remoting/remoting_test_driver_common.gyp:remoting_test_driver_ common', | |
| 20 ], | |
| 21 'defines': [ | |
| 22 'VERSION=<(version_full)', | |
| 23 ], | |
| 24 'sources': [ | |
| 25 'test/chromoting_test_driver.cc', | |
| 26 ], | |
| 27 'include_dirs': [ | |
| 28 '../testing/gtest/include', | |
| 29 ], | |
| 30 }, # end of target 'chromoting_test_driver' | |
| 31 ], # end of targets | |
| 32 } | |
| OLD | NEW |