Differences

This shows you the differences between two versions of the page.

--- openroad [2026/02/12 14:43] – created beckmanf
+++ openroad [2026/02/13 15:47] (current) – use ctest for regression beckmanf
@@ Line 8: / Line 8: @@
 === Install via bazel ===
-Bazel promises a reproducable build which I liked. I tried it on a virtual (via UTM) debian 13 (trixie) arm64 machine. The openroad binary is a gui application which relies on qt. It seems quite difficult to have system independent gui application. OpenROAD uses prebuild libraries, for example the xcd libraries which are from [[https://github.com/The-OpenROAD-Project/qt_bazel_prebuilts/tree/main/interface_libs|OpenROADS qt_bazel_prebuilts/interface_libs]]. There it turns out
+Bazel promises reproducable builds which I liked. I tried it on a virtual (via UTM) debian 13 (trixie) arm64 machine. The openroad binary is a gui application which relies on qt. It seems quite difficult to have system independent gui application. OpenROAD uses prebuild libraries, for example the xcd libraries which are from [[https://github.com/The-OpenROAD-Project/qt_bazel_prebuilts/tree/main/interface_libs|OpenROADS qt_bazel_prebuilts/interface_libs]]. It turns out that prebuild libraries are build in a ubuntu docker container and the copied to the repository. Therefore they are x86_64 and do not work on the arm64 machine.
+I gave up on that one for the time being.
 === Install via cmake ===
@@ Line 27: / Line 28: @@
 </code>
+=== Regression Test ===
+To be sure that the compiled tools are actually working as expected on possibly different platforms, a regression test is a good idea. The [[https://github.com/The-OpenROAD-Project/OpenROAD/blob/master/README.md|README.md]] mentions some tests. Run:
+<code>
+./test/regression flow
+ctest --test-dir build -j 8
+</code>
+=== Build Results ===
+Some collected build results:
+[[or_buildresults|OpenROAD Build Results]]