-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
```
If I change the arguments to a Gyp action, the action does not get re-run when
building the Gyp file with MS Visual Studio.
Here is an example Gyp file that reproduces the problem:
{
'include…
-
This might honestly end up being too hairy to be worth it, but for simple tests, it might be nice to get rid of the essentially boilerplate Python wrapping around transcripts. For example:
```py
#…