From GridLAB-D Wiki
Jump to: navigation, search

Current GridLAB-D Builds

Stable Release - Jojoba (Version 3.2)
Release Candidate - N/A
Next Release - Hassayampa (Version 3.0)
Trunk - Keeler (trunk)

Windows XP/7/8/10

The Windows version should be installed from the latest download build.

MS Visual Studio 2005
The standard build environment in MS Windows is MS Visual Studio 2005. For more information on building and debugging with VS2005, see Working with MS Visual Studio 2005. VS2005 was the standard build tool through GridLAB-D v3.x, but is in the process of being deprecated for the MinGW solution.
MS Visual Studio 2010
A MS Visual Studio 2010 solution is somewhat available, but will not be supported. See and for details and working examples.
The mingw with Eclipse solution is now working. All versions of GridLAB-D starting with v4.0 will use this as the default build process.


Redhat and MacOSX builds should be downloaded from the latest download build.

Most Linux and Unix system can be built using the standard automake process. If you just want to build the code, it is recommended that you only check out the trunk or one of the branches, as the full repository is very large (over 6GB). The first time you must checkout the source code from the Subversion repository:

host% cd work
host% svn checkout gridlab-d
   ...lots of output...
host% cd gridlab-d
host% autoreconf -isf
   ...lots of output...
host% ./configure
   ...lots of output...

If you want to checkout a branch instead, replace trunk in the second command with branch/2.3 (or whatever the number of the branch you want is).

Once you have a working copy checked out, you can synchronize your copy of the code by updating your files:

host% cd work
host% svn update gridlab-d
   ...some of output...
host% cd gridlab-d
host% make
   ...lots of output...
host% sudo make install
Password: your password
   ...lots of output...

If you want to check your build, run the validate process

host% make validate
   ...lots of output...

Any failures will be reported. Note that the latest version almost always has some validation problems because, almost by definition, a build with validation problems is not released.

HP Superdome

A number of problems were encountered with the libraries on the HP Superdome (uname Linux 2.6.18-128.1.6.el5 #1 SMP Tue Mar 24 12:10:08 EDT 2009 ia64 ia64 ia64 GNU/Linux) but they were easily resolved by making sure the most recent version of xercesc was installed.

There appear to be persistent performance problems with 2.2 on machines like the HP Superdome. These problems are not expected to be fixed until Grizzly (3.0) is released.

Mac OS X

GridLAB-D can be built for Leopard (10.5), Snow Leopard (10.6), Lion (10.7) and Mountain Lion (10.8). Before you download source code and build, you need setup your build environment.

The code download procedure is the same as for standard Linux systems:

host% svn co gridlab-d

where version is either trunk or a branch version, e.g., branch/2.3.

The build procedure is also the same as for standard Linux systems:

host% cd gridlab-d
host% autoreconf -isf
host% ./configure
host% sudo make install

You may wish to use fink, macports, or homebrew to install some of the necessary dependencies (mainly libxerces-c).

The following issues are known:

  1. Version 2.2 can only be built on Leopard because of incompatibility with Xerces-C 2.8 and Snow Leopard. See for details.
  2. As of the problems with Xerces-C compatibility have been fixed, but there is an unexplained link error in powerflow on Snow Leopard. This can be overcome by using 'make -i', but the powerflow module is not built correctly and will not load. See for details.
  3. As of 2012-07-25, there is a bug that may prevent builds from completing on Mac OS systems with MATLAB installed. See for details.
  4. As of 2013-01-25, there is a reported problem with Xerces libraries not being installed correctly during builds and/or installs. See for details.

Known Issues

Any known issues listed on this page may be out of date at any given time, but you can consult the bug tracker for a more up to date list.