Iverilog, containing the source tree, and will populate thatĭirectory with the most current source from the HEAD of the repository. Information now so you don't forget to do it later. Information is important if/when you submit a patch. The first two lines are optional and are used to tell git who you are.

% git config -global user.email git clone % git config -global user.name 'Your Name Goes Here' To get the development version of the code follow these steps: Stable releases are placed on branches, and in particular v11 stable You can use git to get the latest development head or the latest of a specificīranch. The source code for Icarus is stored under the git source code control system. Git installed on your system, go to (or see the package repositoryįor your Linux distribution) for current git software. Note: Icarus Verilog uses github to host the source code. The source is then compiled and installed in the manner appropriate This will create a directory, similar to the name of the tarball, such as verilog- version. Note that there are precompiled and/or prepackaged versions for a variety of systems, so if you find an appropriate packaged version, then that is the easiest way to install.ĭownload a tarball with a name such as verilog- and un-tar it using: The following instructions are the common steps for obtaining the Icarus Verilog source, compiling and installing. Icarus is developed for Unix-like environments but can also be compiled on Windows systems using the Cygwin environment or MinGW compilers. 2.3.2 Installing version 0.9.x from a PPA on Karmic, Lucid, Maverick, Natty, Oneiric, Precise.2.3.1 Installing version 0.9.1 from a launchpad PPA repository on Intrepid and Jaunty.1.3 Icarus Specific Configuration Options.

Brew install acrobat reader