third_party.pigweed.src/pw_build/py/nop.py
Alexei Frolov 917756d925
Add a stamp option to pw_python_script
GN requires all actions to have at least one output file. However, many
Python scripts are run to process data without generating a file. Such
scripts would previously have to specify a dummy output file and touch
it on completion.

This change adds this stamp functionality to the script-runner script.
The pw_python_script template accepts a boolean "stamp" argument. If
set, the runner will touch a dummy file after it runs its sub-command.

Change-Id: Iff0408ea0d93007418a1766f1eb7ed7b30ec6913
2019-11-12 15:07:43 -08:00

28 lines
1.1 KiB
Python

# Copyright 2019 The Pigweed Authors
#
# Licensed under the Apache License, Version 2.0 (the "License"); you may not
# use this file except in compliance with the License. You may obtain a copy of
# the License at
#
# https://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
# WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
# License for the specific language governing permissions and limitations under
# the License.
"""Does nothing.
The purpose of this script is to allow for source file dependencies within GN
to be attached to targets that do not typically support them, such as groups.
For example, instead of creating a group target, a pw_python_script target to
run this script can be created. The script can be given a list of input files,
causing GN to rebuild the target and everything that depends on it whenever any
input file is modified.
This is useful in the case where metadata is attached to a group of files but
not collected into a generated_file until a later target.
"""