Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
install_actflow [2026/05/29 12:28] – [Build instructions] rajitinstall_actflow [2026/07/22 15:09] (current) – [Linux/Unix-like environments] rajit
Line 34: Line 34:
 **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. **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.
  
 +**Archlinux:** One of the ACT users has contributed an Archlinux [[https://aur.archlinux.org/packages/actflow-git |package]]. 
 ==== Build instructions ==== ==== Build instructions ====
  
Line 50: Line 51:
  
  
-**actsim and Xyce:** The ACT simulator also supports mixed analog/digital simulation using "Xyce". To include this feature, follow the instructions above. After that, follow the instructions provided by the [[https://github.com/asyncvlsi/actsim|''actsim'']] repository to re-build and re-install ''actsim''.+**actsim and Xyce:** The ACT simulator also supports mixed analog/digital simulation using [[https://xyce.sandia.gov/|Xyce]]. To include this feature, follow the instructions above. After that, follow the instructions provided by the [[https://github.com/asyncvlsi/actsim|actsim]] repository to re-build and re-install ''actsim''.
  
 **Building from source.**  Sometimes it is not possible to use package managers to install the required dependencies. In this case, the standard approach that we use is to install the missing dependencies by setting the install directory to ''$ACT_HOME''. GNU autotools support the ''--prefix=$ACT_HOME'' (two hyphens before ''prefix'') option to the generated ''configure'' script, and CMake supports ''-DCMAKE_INSTALL_PREFIX=$ACT_HOME''. **Building from source.**  Sometimes it is not possible to use package managers to install the required dependencies. In this case, the standard approach that we use is to install the missing dependencies by setting the install directory to ''$ACT_HOME''. GNU autotools support the ''--prefix=$ACT_HOME'' (two hyphens before ''prefix'') option to the generated ''configure'' script, and CMake supports ''-DCMAKE_INSTALL_PREFIX=$ACT_HOME''.
  
 +=== Environment variables ===
 +
 +The following environment variables are used during the build process:
 +   * ''ACT_HOME'': see above; this is used as the installation directory for the tools and supporting files.
 +   * ''CXX'': used as the C++ compiler. Note that the build script checks if the C++ compiler supports various options that are used by different tools.
 +   * ''ACTFLOW_EXTRA_CFLAGS'': this passes in additional compiler flags (augments the standard ''CFLAGS'' environment variable).
 +   * ''BOOST_ROOT'': if your Boost installation is in a non-standard place (e.g. you had to install your own version because the system version was too old and can't be modified), this should point to the root of your installation directory for Boost.