build: cpplint should always run, even if jslint fails

[mscdex]

• Version: all
• Platform: all
• Subsystem: build

As the title says, it would be nice to always run both jslint and cpplint, even if one or both exit non-zero.

[krydos]

@mscdex what do you think about implementation?

Is it ok to do something like this?

lint:
        EXIT_STATUS=0;\
	$(MAKE) jslint || EXIT_STATUS=$$?; \
	$(MAKE) cpplint || EXIT_STATUS=$$?; \
	exit $$EXIT_STATUS

Or it will be better to create additional script inside ./tools that will run list of passed make targets?
Code above looks a bit complex probably and it will be not so easy to extend.

In case of the script it can look something like this:

lint: 
   tools/lint_runner.sh jslint cpplint

and this bash script can remember exit status of each job and return non 0 in case one of them failed. It looks a bit more extendable and pretty. I'm just not sure if it is ok to create new files in tools directory

[mscdex]

I'm ok with the first solution for Makefile, that's actually more or less how nodejs/github-bot does it. vcbuild.bat would need to be updated accordingly as well.