Alternatives to download the GreenSocs libraries

Beginning with version 3.0.0, the GreenSocs libraries will also be available in a tarball version. Below there are instructions to get and build the tarball version, and further bellow the usual instructions to use the GreenSocs Package Management (GSPM) to get the whole environment including the GreenSocs libraries.

Option 1: Download the tarball version

Fast link to the current version: files/greensocs-4.1.0.tar.gz. Please, continue reading if it is the first time you install this tarball.

The GreenSocs libraries relies on other software packages in order to offer some of its functionality. Depending on your project, the GreenSocs libraries will require that some of the following software are installed in your machine: SystemC, TLM, SCV, Boost, Lua. The GreenSocs libraries will find these dependencies if an environment variable is set to each installation path. The variable name is the name of the dependency with all capitals letters, followed by "_HOME", so: SYSTEMC_HOME, BOOST_HOME, and so on. Alternatively, if some of these dependencies are not installed already, a fast way to do it is to use GSPM: (more info about GSPM in the following section)

   # cd to a directory where GSPM will be installed. May be a user directory.
   wget http://downloads.sourceforge.net/greensocs/gspm_2007.03-1_i386.tar.gz
   tar xzf gspm_2007.03-1_i386.tar.gz
   source gspm/gspm.bashrc
   gs-use --upgrade

   gs-use systemc/2.2   # if you need SystemC or SYSTEMC_HOME variable is not set
   gs-use tlm/2.0       # if you need TLM or TLM_HOME variable is not set
   gs-use boost/1.34.1  # if you need Boost or BOOST_HOME variable is not set
   gs-use lua           # if you need Lua or LUA_HOME variable is not set

The packages from GSPM are pre-compiled with GCC 4, and may not work with earlier versions of GCC.

Now we should get the GreenSocs libraries tarball here: files/greensocs-4.1.0.tar.gz. And build the only binary library, GreenReg, with:

   cd greensocs-4.1.0/greenreg
   make
   cd ..

Set an environment variable to the current directory (the root of the extracted GreenSocs tarball) to make it easier to set the GreenSocs include path in Makefiles and other compilation environments.

   export GREENSOCS_HOME=$PWD   # should be in the directory greensocs-4.1.0

Last step is to put the $GREENSOCS_HOME directory in the include path of your compiler environment (and $GREENSOCS_HOME/greenreg in the library path it the greenreg library is needed). Congratulations! The GreenSocs libraries are ready to use.

Option 2: Download GreenSocs Package Management (GSPM)

GSPM is the simple way to get going with ESL. It's the easy road to get all GreenSocs packages.

YOU can install it. It requires no special privileges. It's a simple click download, unpack and run.

STEP 1: Download GSPM

Download the version of gspm which best corresponds to your architecture. If you dont see what you need, please get in touch.

Version 2007.03-1 (March 2007)

OS	Architecture	Size	File
Linux	i386	11 MB	gspm_2007.03-1_i386.tar.gz
Linux	x86-64	11 MB	gspm_2007.03-1_x86-64.tar.gz
Mac OS X	i386		(soon)
Mac OS X	powerpc		(soon)

Or access directly the SourceForge download area

NOTE: If you installed GSPM before 07/25/2007, the update feature may not work due a major change in the gcc package. The easiest way to upgrade is to reinstall all from scratch. We are very sorry for the inconvenience.

STEP 2: Installing GSPM

All the GSPM environment can be run as a normal user, root privileges are not necessary. Just untar the tarball in any directory you want:

  tar xzf gspm_2007.03-1*.tar.gz

STEP 3: Using GSPM

You must first be running a "bash" shell. Only the "bash" shell is supported right now. If you would like support for other shell, like "tcsh", please contact GreenSocs.

The entry point to use GSPM is to source the script 'gspm.bashrc' into the current shell session, like this:   source gspm/gspm.bashrc (you can do this from anywhere, you can even do it from your .bashrc so it's always loaded)

Your ready to go!

Now you can load the packages you want using the command 'gs-use'. Each time you ask for a new package, gs-use will download it, if it needs to, and download any packages that it depends upon.

NOTE: Some users experience problems with their Internet setup. gs-use operates over http, so there should not be any problems, but often you need to set your HTTP_PROXY environment variable to point to your systems proxies, like: export http_proxy="http://username:password@host:port/"

Example: a work session

GSPM uses concepts like enter the world and load/use packages. For a typical work session, you must first source gspm.bashrc script to enter the world, then some GreenSocs tools will be available. After that, load the pieces of software that will be used in this session with gs-use (they will be installed when first used). This step is necessary because more then one version of a tool can be installed in the same world, and gs-use also select the version of the tool to be used (or a default one if none specified).

For example, a work session that compiles a program from the greenbus package using the gsc compiler wrapper to easily find the loaded libraries (in this case systemc and boost):

Finding packages

All projects release packages through this web site. So simply browse the projects/ on this web site, find things you are interested in, and type

The full name of project releases can be found on each project page.