From 91a727ec4957eca21d93d117a2e725bb5b3a9f5d Mon Sep 17 00:00:00 2001 From: Denis Shienkov Date: Wed, 9 Oct 2019 23:00:08 +0300 Subject: baremetal: Don't interpret BL51 linker warnings as errors BL51 linker (from Keil product for 8051 architecture) ends with the exit code '1' in case any linking warning occurred. It is not an error, because at errors the linker ends with the exit code '2'. So, we need just to increase the value of the linking command 'maxExitCode' property from 0 to 1, similar to the compiler command handling. Change-Id: I4917d08ca3407c8046879780e4c8696fdef7736a Reviewed-by: Christian Kandeler Reviewed-by: Ivan Komissarov --- share/qbs/modules/cpp/keil.js | 2 ++ 1 file changed, 2 insertions(+) diff --git a/share/qbs/modules/cpp/keil.js b/share/qbs/modules/cpp/keil.js index 4e40a3e64..4bf6e4b79 100644 --- a/share/qbs/modules/cpp/keil.js +++ b/share/qbs/modules/cpp/keil.js @@ -756,9 +756,11 @@ function prepareLinker(project, product, inputs, outputs, input, output) { var primaryOutput = outputs.application[0]; var args = linkerFlags(project, product, input, outputs); var linkerPath = product.cpp.linkerPath; + var architecture = product.cpp.architecture; var cmd = new Command(linkerPath, args); cmd.description = "linking " + primaryOutput.fileName; cmd.highlight = "linker"; + cmd.maxExitCode = getMaxExitCode(architecture); filterStdOutput(cmd); return [cmd]; } -- cgit v1.2.3