This won't actually work. Your project is hitting the case where 0 binaries are specified. And we don't want to make that just be silently ignored.

It's the wpi.cpp.enableExternalTasks(it) in the binary definition that adds the binary to the simulation task.

Yeah I started testing it and I realised this. I've made another change to improve the error message a bit.

@ThadHouse maybe if we see you only have non executable binaries we print that out as a warning and peacefully exit at that point?

Thats not the issue. Currently, the task is created automatically whenever the gradlerio plugin is applied. It is then up to the project to explicitly add a binary to the simulation task. Thats what the call to wpi.cpp.enableExternalTasks(it) in the binary definition does. The sim task doesn't attempt to automatically add any binaries, and doesn't have access to do that either.

Basically the way to solve this would be to only create the sim tasks if wpi.cpp.enableExternalTasks(it) is called, instead of eagerly creating them, as happens currently.