1 # Copyright (c) 2012 The Chromium Authors. All rights reserved. 2 # Use of this source code is governed by a BSD-style license that can be 3 # found in the LICENSE file. 4 5 # This file is meant to be included into an action to copy test data files into 6 # an iOS app bundle. To use this the following variables need to be defined: 7 # test_data_files: list: paths to test data files or directories 8 # test_data_prefix: string: a directory prefix that will be prepended to each 9 # output path. Generally, this should be the base 10 # directory of the gypi file containing the unittest 11 # target (e.g. "base" or "chrome"). 12 # 13 # To use this, create a gyp target with the following form: 14 # { 15 # 'target_name': 'my_unittests', 16 # 'conditions': [ 17 # ['OS == "ios"', { 18 # 'actions': [ 19 # { 20 # 'action_name': 'copy_test_data', 21 # 'variables': { 22 # 'test_data_files': [ 23 # 'path/to/datafile.txt', 24 # 'path/to/data/directory/', 25 # ] 26 # 'test_data_prefix' : 'prefix', 27 # }, 28 # 'includes': ['path/to/this/gypi/file'], 29 # }, 30 # ], 31 # }], 32 # } 33 # 34 35 { 36 'inputs': [ 37 # The |-o <(test_data_prefix)| is ignored; it is there to work around a 38 # caching bug in gyp (https://code.google.com/p/gyp/issues/detail?id=112). 39 # It caches command output when the string is the same, so if two copy 40 # steps have the same relative paths, there can be bogus cache hits that 41 # cause compile failures unless something varies. 42 '<!@pymod_do_main(copy_test_data_ios -o <(test_data_prefix) --inputs <(test_data_files))', 43 ], 44 'outputs': [ 45 '<!@pymod_do_main(copy_test_data_ios -o <(PRODUCT_DIR)/<(_target_name).app/<(test_data_prefix) --outputs <(test_data_files))', 46 ], 47 'action': [ 48 'python', 49 '<(DEPTH)/build/copy_test_data_ios.py', 50 '-o', '<(PRODUCT_DIR)/<(_target_name).app/<(test_data_prefix)', 51 '<@(_inputs)', 52 ], 53 } 54
