Differences

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

--- install_actflow [2024/07/12 09:41] – [Linux/Unix-like environments] rajit
+++ install_actflow [2025/04/17 10:32] (current) – [Installing actflow] rajit
@@ Line 2: / Line 2: @@
 Primary development of the tools in the actflow repository is conducted on Linux and MacOS, and so it has been extensively tested on such systems. It has also been tested in certain [[install#Microsoft Windows|Windows]] environments (see below).
+If you are a Homebrew user, check out the [[https://github.com/asyncvlsi/homebrew-tap|homebrew tap]] for the tools.
+===== Getting the source  =====
 The repository is available from [[https://github.com/asyncvlsi/actflow|Github]]. Once you clone this repository, make sure you run
@@ Line 17: / Line 23: @@
       * For ''apt-get'', it is ''libeditline-dev'' or ''libedit-dev''
       * Some systems have both packages. In that case please use ''libedit'', not ''libeditline''.
-   * The system should have ''zlib'' installed
+   * The system must have ''zlib'' installed
-   * The system should have the macro pre-processing package ''m4'' installed
+   * The system must have the macro pre-processing package ''m4'' installed
-   * The system should have a modern C++ compiler (at least C++-17)
+   * The system must have a modern C++ compiler (at least C++-17)
-   * The system should have ''cmake'' (at least version 3.16)
+   * The system must have ''cmake'' (at least version 3.16)
-   * The system should have the Boost libraries (at least version 1.71.0)
+   * The system must have the Boost libraries (at least version 1.71.0)
-   * The system should have ''libfmt'' (at least version 4.0)
+   * The system must have ''libfmt'' (at least version 4.0)
 **MacOS:** These packages can be installed using the [[https://brew.sh/|homebrew]] package manager. Note that on recent versions of MacOS, the C++ compiler provided by Apple does not accept the ''-fopenmp'' flag for OpenMP compilation, so you will likely need to install g++ using homebrew as well.
@@ Line 45: / Line 51: @@
-==== Troubleshooting ====
+===== Microsoft Windows =====
+Recent versions of Windows include compatibility layers for Unix, and ACT has been successfully tested in such an environment.
+[[windows_build|Some instructions for running ACT tools on Microsoft Windows]]
+===== Troubleshooting =====
 If you have trouble building on your specific operating system have a peek in the continuous integration scripts of the git repository if your operating system is covered there and you can try the commands specified:
@@ Line 51: / Line 66: @@
 https://github.com/asyncvlsi/actflow/blob/main/.circleci/config.yml
-for ''Debian'', ''Ubuntu'' look at the ubuntu section
+for ''Debian'', ''Ubuntu'' look at the ubuntu section. Here's the script used by the continuous integration build on Ubuntu to build and install the tools in ''/usr/local/cad'', and run the test cases:
+<code>
+$ apt-get -q update -y
+$ apt-get -q install -y libedit-dev zlib1g-dev m4 build-essential cmake libfmt-dev git libboost-all-dev libopenmpi-dev llvm flex bison
+$ git clone https://github.com/asyncvlsi/actflow
+$ cd actflow
+$ git submodule update --init --recursive
+$ mkdir /usr/local/cad
+$ export ACT_HOME=/usr/local/cad
+$ ./build && ./run.sh
+</code>
+Replace ''/usr/local/cad'' on the lines where it is used with your actual installation directory.
-for ''Alpine'' look at the alpine section
+For Alpine Linux look at the alpine section in the yml file.
-**MacOS:** Recent versions of MacOS have a C++ compiler issue, namely that the default compiler distributed by Apple does not support the "-fopenmp" flag. To fix this issue, we normally install either ''llvm'' or ''g++'' using homebrew. This normally results in the compiler being installed in a path that looks something like ''/opt/homebrew/Cellar/llvm/<version>/bin/clang++" or "/opt/homebrew/Cellar/gcc/<version>/bin/g++-<version>''. Set the environment variable "CXX" to the absolute path name of this C++ compiler before running "./build".
+**MacOS:** Recent versions of MacOS have a C++ compiler issue, namely that the default compiler distributed by Apple does not support the "-fopenmp" flag. To fix this issue, we normally install either ''llvm'' or ''g++'' using homebrew. This normally results in the compiler being installed in a path that looks something like ''/opt/homebrew/Cellar/llvm/<version>/bin/clang++'' or ''/opt/homebrew/Cellar/gcc/<version>/bin/g++-<version>''. Set the environment variable ''CXX'' to the absolute path name of this C++ compiler before running "./build".
 === OpenMP message ===
@@ Line 100: / Line 127: @@
 </code>
-Tie build script tries to compile this with and without the ''-lstdc++fs'' option (needed for some older C++ compilers, but no longer needed in a modern compiler). This message means both options did not succeed using the compiler that supported the ''-fopenmp''' flag.
+Tie build script tries to compile this with and without the ''-lstdc++fs'' option (needed for some older C++ compilers, but no longer needed in a modern compiler). This message means both options did not succeed using the compiler that supported the ''-fopenmp'' flag.
-===== Microsoft Windows =====
-Recent versions of Windows include compatibility layers for Unix, and ACT has been successfully tested in such an environment.
-[[windows_build|Some instructions for running ACT tools on Microsoft Windows]]