Setting the appropriate target when running autoharness-analyzer (#384)

… run-kani.sh

This finds the appropriate target directory instead of hard-coding
`x86_64-unknown-linux-gnu`.

Resolves #381

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 and MIT licenses.

Co-authored-by: Fedor Ryabinin <rfedor@amazon.com>

Author: vonaka

scripts/run-kani.sh

@@ -351,19 +351,19 @@ main() {
             --cbmc-args --object-bits 12
         # remove metadata file for Kani-generated "dummy" crate that we won't
         # get scanner data for
-        rm target/kani_verify_std/target/x86_64-unknown-linux-gnu/debug/deps/dummy-*
+        local target=$(find "target/kani_verify_std/target/" -mindepth 1 \
+                         -type d -exec test -e '{}'/debug/deps/ \; -print)
+        rm $target/debug/deps/dummy-*
         echo "Running Kani's std-analysis command..."
         pushd scripts/kani-std-analysis
         ./std-analysis.sh $build_dir
         popd
         echo "Running autoharness-analyzer command..."
         pushd scripts/autoharness_analyzer
         cargo run -- --per-crate \
-          ../../target/kani_verify_std/target/x86_64-unknown-linux-gnu/debug/deps/ \
-          /tmp/std_lib_analysis/results/
+          ../../$target/debug/deps/ /tmp/std_lib_analysis/results/
         cargo run -- --per-crate --unsafe-fns-only \
-          ../../target/kani_verify_std/target/x86_64-unknown-linux-gnu/debug/deps/ \
-          /tmp/std_lib_analysis/results/
+          ../../$target/debug/deps/ /tmp/std_lib_analysis/results/
         popd
     fi
 }