In the IDE, the iTasks resource collector is not called when the executable is up to date (#4) · Issues · clean-and-itasks / clean-ide

In the IDE, the iTasks resource collector is not called when the executable is up to date

(Issue reported by @peter88)

The iTasks web resource collector is a separate link step:

		EnvironmentLinker:	Tools\Clean System 64\StaticLinker.exe : -h 64M | Tools\Clean System\WebResourceCollector.exe

The IDE internally keeps track of whether the executable generated for a project is up to date (by checking if source files and/or options have changed). When the executable is still up to date, the entire link step is skipped and therefore also the web resource collector is skipped. This is a problem because one would expect that changing a file in some WebPublic folder and running a project update in the IDE would cause the resources to be collected again.

(cpm does not have this problem because it cannot keep track of whether the application options for an executable changed, so the link step is always performed.)

Possible solutions I see are:

Always performing the link step
Only skipping the links step for StaticLinker.exe
Adding a separate entry in the environment for additional link steps

A workaround is to trigger the link step by modifying a Clean module.

(Issue reported by @peter88)

The iTasks web resource collector is a separate link step:

```
		EnvironmentLinker:	Tools\Clean System 64\StaticLinker.exe : -h 64M | Tools\Clean System\WebResourceCollector.exe
```

(`cpm` does not have this problem because it cannot keep track of whether the application options for an executable changed, so the link step is always performed.)

Possible solutions I see are:

- Always performing the link step
- Only skipping the links step for `StaticLinker.exe`
- Adding a separate entry in the environment for additional link steps

A workaround is to trigger the link step by modifying a Clean module.

To upload designs, you'll need to enable LFS. More information