Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
install [2020/12/02 01:00]
127.0.0.1 external edit
install [2022/07/17 09:57] (current)
rajit [Installing ACT]
Line 1: Line 1:
 +====== Installing ACT ======
  
-====== System requirements ======+Primary development of ACT 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). 
 + 
 +The core library is available from [[https://github.com/asyncvlsi/act|Github]]. 
 + 
 + 
 + 
 +===== Linux/Unix-like environments =====
  
 Before starting, please make sure that your system satisfies the following requirements: Before starting, please make sure that your system satisfies the following requirements:
Line 11: Line 18:
    * The system should have the macro pre-processing package ''m4'' installed    * The system should have the macro pre-processing package ''m4'' installed
  
-====== Build instructions ======+On MacOS, these packages can be installed using the [[https://brew.sh/|homebrew]] package manager. 
 + 
 +==== Build instructions ====
  
 Create a directory where you'd like the tools to be installed. Example common locations include ''/usr/local/cad'', ''/opt/cad'', ''/opt/async''. Once you've cloned the [[http://github.com/asyncvlsi/act|git repo]]: Create a directory where you'd like the tools to be installed. Example common locations include ''/usr/local/cad'', ''/opt/cad'', ''/opt/async''. Once you've cloned the [[http://github.com/asyncvlsi/act|git repo]]:
Line 20: Line 29:
    * Run ''./build''    * Run ''./build''
  
-If there is an issue building the software and you want to do a clean build, use ''make realclean''+If there is an issue building the software and you want to do a clean build, use ''make realclean'' before re-running the build instructions above.
  
 Once you've built the tools, run ''make install'' to install the files, and ''make runtest'' to run through a set of test cases. Once you've built the tools, run ''make install'' to install the files, and ''make runtest'' to run through a set of test cases.
Line 28: Line 37:
 Optional: to add the tools to your path add ''export PATH=$ACT_HOME/bin:$PATH'' to your ''.bashrc'' too Optional: to add the tools to your path add ''export PATH=$ACT_HOME/bin:$PATH'' to your ''.bashrc'' too
  
-=== trouble shooting ===+==== 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:+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:
  
 https://github.com/asyncvlsi/act/blob/master/.circleci/config.yml https://github.com/asyncvlsi/act/blob/master/.circleci/config.yml
Line 39: Line 48:
  
  
-====== Running large ACT files ======+===== 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]] 
 + 
 +===== Running large ACT files =====
  
 ACT files are typically short since they are written by a designer. However, an ACT file generated by another program---especially if the program generates a flattened design---can be large. If an ACT process (or a namespace) has a very large number of instances/connections that are individually listed (i.e. in the input file) and the library crashes, try removing system limits on the stack size (using ''unlimit'' or ''ulimit'' depending on your shell) and re-running the program. ACT files are typically short since they are written by a designer. However, an ACT file generated by another program---especially if the program generates a flattened design---can be large. If an ACT process (or a namespace) has a very large number of instances/connections that are individually listed (i.e. in the input file) and the library crashes, try removing system limits on the stack size (using ''unlimit'' or ''ulimit'' depending on your shell) and re-running the program.
  
-====== Synopsys linkages ======+===== Synopsys linkages =====
  
 Some of the library functionality can be linked into Synopsys ''vcs'' for co-simulation support. This requires some Synopsys header files (obviously not included in the ACT distribution). Some of the library functionality can be linked into Synopsys ''vcs'' for co-simulation support. This requires some Synopsys header files (obviously not included in the ACT distribution).