Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • C clean-ide
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • clean-and-itasksclean-and-itasks
  • clean-ide
  • Issues
  • #4
Closed
Open
Issue created Jun 08, 2019 by Camil Staps@cstapsContributor

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking