Closed ricka-github closed 8 years ago
Your generator makes a bunch of nodes that are identical for each configuration, so the DAG generator doesn't know how to separate them. The generators computes a hash based on the action (command line), input and output files (and maybe something else, I forget). This node has nothing, so they all map to the same thing which confuses the subsequent pass. The hashes are used for a couple of things, including automatic filesystem cleanup of build steps that are not present anymore.
I thought that might be the case, which is why I tried removing all but a single configuration.
...
Which means I still have the debug/release/production triplet, so I actually have three configurations. Thanks for the help!
The following tundra file gives me an error about duplicate node guids. I am unsure why this is happening. This example is pretty non-functional, but I had the same issue with a slightly more realistic scenario. Naturally, it's my new node that is causing the issue somehow.