Mad SDK
The Mad SDK is a collection of compilers and run-time libraries which make it easy to install and use various pieces of software developed within the Madison Massive Star Group. Currently it functions as a superset of the MESA SDK, with the following additional packages included:
- The ODEPACK ordinary differential equation solver library
- The argtable command line parser library
- The MPICH implementation of the MPI standard
The compatibility and pre-requisites of the Mad SDK are the same as for the MESA SDK.
Linux
Download
To download the SDK for Linux, click on the appropriate link in the table:
| Version Release Date |
File | Notes |
|---|---|---|
| 22.6.1 (current) June 14 2022 |
madsdk-x86_64-linux-22.6.1.tar.gz | Updated to gcc 12.1.0; many other packages also updated |
| 22.2.1 February 19 2022 |
madsdk-x86_64-linux-22.2.1.tar.gz | Updated to gcc 11.2.0; many other packages also updated |
| 20190503 May 3 2019 |
madsdk-x86_64-linux-20190503.tar.gz | Patched makedepf90 to support external dependencies; fixed ffmpeg and ncurses |
| 20190327 March 27 2019 |
madsdk-x86_64-linux-20190327.tar.gz | Updated to gcc 8.3.0; many other packages also updated |
| 20180321 March 21 2018 |
madsdk-x86_64-linux-20180321.tar.gz | Updated to gcc 7.2, and more recent versions of many other packages. |
Note that versions of the SDK older than the current one are not formally supported but are provided here as a courtesy; if you run into problems using an older version, you should first try upgrading to the current version.
Installation
On Linux the SDK can be installed anywhere. However, for simplicity the following instructions will assume you're installing in your home directory. The steps are as follows:
- Download the package from the table above
- Extract it using the command tar xvfz package_name -C ~/ (note that's a tilde in front of the slash!)
- Set the path to the SDK:
- For the C shell: setenv MADSDK_ROOT ~/madsdk
- For the Bourne shell: export MADSDK_ROOT=~/madsdk
- Initialize the SDK (also checks compatibility):
- For the C shell: source $MADSDK_ROOT/bin/madsdk_init.csh
- For the Bourne shell: source $MADSDK_ROOT/bin/madsdk_init.sh
- Check that the SDK is properly installed by running gfortran --version. The first line of the output should look something like this:
GNU Fortran (GCC) 8.3.0
Steps 3 and 4 need to be repeated each time you begin a new shell session; alternatively, they can be added to the appropriate shell start-up file (~/.cshrc for the C shell, and ~/.profile for the Bourne shell).
Mac OS X
Download
To download the SDK for OS X, click on the appropriate link in the table:
| Version Release Date |
File | Notes |
|---|---|---|
| 22.6.1 (current) June 14 2022 |
madsdk-x86_64-macos-22.6.1.pkg | Updated to gcc 12.1.0; many other packages also updated |
| 22.2.1 February 19 2022 |
madsdk-x86_64-macos-22.2.1.pkg | Updated to gcc 11.2.0; many other packages also updated. Works with Big Sur and Monterey |
| 19.11.2 November 6 2019 |
madsdk-x86_64-macos-19.11.2.pkg | Switched to new .pkg installer system; added signing/notarization to work with Catalina |
Note that versions of the SDK older than the current one are not formally supported but are provided here as a courtesy; if you run into problems using an older version, you should first try upgrading to the current version.
Installation
On OS X the SDK is installed in the Applications folder. The steps are as follows:
- Download the disk image from the table above
- Open it by double clicking on it in the Finder
- Drag the madsdk folder across to the Applications folder
- Set the path to the SDK:
- For the C shell: setenv MADSDK_ROOT /Applications/madsdk
- For the Bourne shell: export MADSDK_ROOT=/Applications/madsdk
- Initialize the SDK (also checks compatibility):
- For the C shell: source $MADSDK_ROOT/bin/madsdk_init.csh
- For the Bourne shell: source $MADSDK_ROOT/bin/madsdk_init.sh
- Check that the SDK is properly installed by running gfortran --version. The first line of the output should look something like this:
GNU Fortran (GCC) 8.3.0
Steps 4 and 5 need to be repeated each time you begin a new shell session; alternatively, they can be added to the appropriate shell start-up file (~/.cshrc for the C shell, and ~/.profile for the Bourne shell).