In more complicated custom content processors you can trigger building of dependent content via code.

If you happen to use a relative path like ./foo.png or .\..\bar\foo.png it could cause the pipeline to generate multiple copies of the same content.

This ensures incoming source file paths are fully resolved before they are processed and they are cached with the same path.