[Bsb] Better dry run feature
The current bsb -- -n ninja dry run feature works well, but still potentially outputs lots of stuff when there are stale files or errors in the project.
@bobzhang I don't mind the extra output since this is primarily used by the editor to check whether the output is empty. But I'm guessing the intention of having a specialized dry run is better speed?
@chenglou yes. Is it a high priority
Ah, also, bsb -- -n wipes .compiler.log and leaves only # Done, as if the build succeeded even when it might have been erroring. This is technically a bug.
so I fixed that dry-run mode will not touch .compiler.log in #4710
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.