build: Resolve certificate and key paths

Since both the certificate path and the private key path are forwarded
to CMake, the user is asked to specify them as absolute. Build process
fails when either of these is a local path instead. Unfortunately,
although our build script checks for existence of both files, the check
is not done from CMake's point of view. As a result, the build error
seen by the user is hard to understand (no known rule to make a missing
ninja target).

Resolve both AWS certificate path and AWS private key path to prevent
the unhelpful error message from showing up, and make the build script
more flexible by giving users option to use local paths as well as
absolute paths for PEM files.

Signed-off-by: Filip Jagodzinski <[email protected]>

Author: Filip Jagodzinski

release_changes/202401221030.change

@@ -0,0 +1 @@
+build: Resolve certificate and key paths.

tools/scripts/build.sh

@@ -74,8 +74,8 @@ Options:
     -s,--audio                  Audio source (ROM | VSI)
     --toolchain                 Compiler (GNU or ARMCLANG)
     --configure-only Create build tree but do not build
-    --certificate_path          The full path for the AWS device certificate
-    --private_key_path          The full path for the AWS device private key
+    --certificate_path          Path to the AWS device certificate
+    --private_key_path          Path to the AWS device private key
 Examples:
     blinky, aws-iot-example, freertos-iot-libraries-tests, keyword-detection, speech-recognition
 EOF
@@ -124,11 +124,11 @@ do
       shift 2
       ;;
     --certificate_path )
-      CERTIFICATE_PATH=$2
+      CERTIFICATE_PATH=$(realpath "$2")
       shift 2
       ;;
     --private_key_path )
-      PRIVATE_KEY_PATH=$2
+      PRIVATE_KEY_PATH=$(realpath "$2")
       shift 2
       ;;
     --configure-only )