qbs build: Do not fail on no-op upx calls

The problem is as follows:
  - qbs re-runs a command if one of the rule inputs' file file stamp
    changes.
  - However, go has build tool functionality built in and will not
    rebuild if it detects that the changes in the source file are
    irrelevant.
  - In such a case, upx will get an input file that is already
    compressed, resulting in a warning.
  - Unfortunately, this harmless warning will result in an exit code
    of 2, which qbs interprets as a build failure.
  - Command.maxExitCode does not help, because the warning exit code
    is higher than the failure exit code.
Therefore, we use a JavaScriptCommand and run the process manually.

Change-Id: I567ba1a5e5f2891a4a093c7637b2845c8663ea22
Reviewed-by: Christian Stenger <[email protected]>

0 files changed, 0 insertions, 0 deletions