The MESA SDK is a collection of compilers and run-time libraries that make it easy to install and use the MESA stellar evolution code.
- Mac Os X Installer Download
- Freeware Os X Software
- Download Apple Os For Windows
- Free Mac Os For Windows
- Download Mac Os X Free
- Java Jdk Download Mac Os X
![Download os x lion installer Download os x lion installer](/uploads/1/1/9/5/119586140/359656068.png)
|
You can download the latest edition of the Zoom Mac SDK directly from git. You will find five folders in the download. The ZoomSDKSample folder contains a sample app that uses the SDK. You can open the ZoomSDKSample.xcodeproj file in your Xcode. Java ME Downloads Java Platform Micro Edition Software Development Kit 3.0 for Mac OS. Java ME Platform SDK is a state-of-the-art toolbox for developing mobile applications. It provides device emulation, a standalone development environment, and a set of.
Overview
Experience has demonstrated that incompatibilities and bugs in compilers and libraries are significant obstacles in getting MESA up and running with minimal fuss. For instance, MESA makes use of various features in the new(ish) Fortran 2003 standard, which aren't implemented (or are still buggy) in all but the most recent compiler releases.
To help overcome these obstacles, I've put together a unified software development kit (SDK) which contains compilers and libraries known to compile MESA correctly. The SDK contains the following components:
- The GNU Comipler Collection (gcc), with support for C, C++, and Fortran
- The GNU Project Debugger (gdb)
- The Valgrind code instrumentation framework
- The Basic Linear Algebra Subprogram (BLAS) library
- The Linear Algebra PACKage (LAPACK) library
- The Hierarchical Data Format v5 (HDF5) library
- The PGPLOT graphics library
- The SE library from the NuGrid project
- The ffmpeg movie encoder
- The ndiff fuzzy comparison tool
- Various helper scripts for use in linking against these libraries and other tasks
Currently, both Linux and Mac OS X running on Intel/AMD processors are supported. Although the SDK was initially bundled as part of the standard MESA distribution (from release 3708 onwards), it makes more sense to keep it separate. This page hosts all the necessary information and links to download, install and use the SDK.
Linux (Intel)
Compatibility
Mac Os X Installer Download
The SDK should work on any relatively-recent Linux distribution running on 64-bit Intel-compatible processors (32-bit processors are no longer supported; in any case, MESA itself doesn't work on 32-bit). The GNU C library (also known as GLIBC) included in the distribution must be version 2.5 or more recent; to determine what GLIBC your system uses, run the command /lib/libc.so.6 (or, possibly, /lib64/libc.so.6) and examine the first line of the output for the version number.
Prerequisites
The following components must be installed for the SDK to work on Linux-based systems:
- The 'Binutils' development tools
- The 'Make' dependency/compilation tool
- The 'Perl' scripting language
- The 'X11' windowing library plus development headers
- The 'Z' compression library plus development headers
- The 'C' shell or derivatives
Not all of these components are installed by default on some Linux distributions, and you may have to use the appropriate package management tool (e.g., apt-get, yum, rpm, emerge) to install them. The following table lists the package names of the components (and any other pieces that are required) for some of the more-common distributions:
Package | Fedora / CentOS | Ubuntu | Mint | Gentoo | Arch |
---|---|---|---|---|---|
Binutils | binutils | binutils | binutils | sys-devel/binutils | binutils |
Make | make | make | make | sys-devel/make | make |
Perl | perl | perl | perl | dev-lang/perl | perl |
X11 library | libX11, libX11-devel | libx11-6, libx11-dev | libx11-dev | x11-libs/libX11 | libx11 |
Z library | zlib, zlib-devel | zlib1g, zlib1g-dev | zlib-dev | sys-libs/zlib | zlib |
C shell | tcsh | tcsh | tcsh | sys-shells/tcsh | tcsh |
Other | libc6-dev | glibc |
If your distribution is not listed here, please contact me and I'll add it to the table.
Download
To download the SDK for Linux, click on the appropriate link in the table:
Release Date MESA Version at Release | File | Notes |
---|---|---|
March 25 2020 (current) 12778 | mesasdk-x86_64-linux-20.3.2.tar.gz | Added ODEPACK library |
March 1 2020 12778 | mesasdk-x86_64-linux-20.3.1.tar.gz | Added math slots functionality |
August 30 2019 12115 | mesasdk-x86_64-linux-20190830.tar.gz | Upgraded gcc to 9.2.0, ffmpeg to 4.2; added crlibm |
May 3 2019 11701 | mesasdk-x86_64-linux-20190503.tar.gz | Patched makedepf90 to support external dependencies; fixed ffmpeg and ncurses (again) |
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 (this is different from previous releases, where it had to be put in the /opt directory). 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 MESASDK_ROOT ~/mesasdk
- For the Bourne shell: export MESASDK_ROOT=~/mesasdk
- Initialize the SDK (also checks compatibility):
- For the C shell: source $MESASDK_ROOT/bin/mesasdk_init.csh
- For the Bourne shell: source $MESASDK_ROOT/bin/mesasdk_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) 9.2.0
If it doesn't, then you should consult the Troubleshooting section below.
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).
Usage
Nothing special needs to be done in order to use the SDK to build MESA. Simply change into the top-level mesa directory (the one created when you download and unpack MESA) and then run ./install.
Mac OS X (Intel)
Compatibility
The SDK should work on any relatively-recent OS X distribution (10.10, Yosemite or later) running on Apple computers with 64-bit Intel-compatible processors (32-bit processors are no longer supported; in any case, MESA itself doesn't work on 32-bit).
Prerequisites
The following components must already be installed before the SDK can be installed on OS X systems:
- The Xcode command-line tools
- The XQuartz X-windows infrastructure
Freeware Os X Software
The Xcode command-line tools can be installed by running xcode-select --install from a Terminal prompt. (Note that a full installation of the Xcode development environment is not necessary). Likewise, XQuartz can downloaded and installed from here. Note that it is often necessary to reinstall the command-line tools and/or XQuartz after upgrading to a new release of OS X.
Download
To download the SDK for OS X, click on the appropriate link in the table:
Release Date MESA Version at Release | File | Notes |
---|---|---|
September 28 2020 (current) 12778 | mesasdk-x86_64-macos-20.9.1.pkg | Fixed 'library not found for -lSystem' issue, arising on fresh Xcode 12 deployments |
April 7 2020 12778 | mesasdk-x86_64-macos-20.4.1.pkg | Added md5sum and other checksum utilities from coreutils |
March 25 2020 12778 | mesasdk-x86_64-macos-20.3.2.pkg | Added ODEPACK library |
March 1 2020 12778 | mesasdk-x86_64-macos-20.3.1.pkg | Added math slots functionality |
November 5 2019 12115 | mesasdk-x86_64-macos-19.11.2.pkg | Fixed version reported by mesasdk_version script |
November 1 2019 12115 | mesasdk-x86_64-macos-19.11.1.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 into the Applications folder; you will likely need Administrator privileges to do this.
- Download the installer from the table above
- Open it by double clicking on it in the Finder
- Follow the on-screen prompts until the installation completes
- Set the path to the SDK:
- For the C shell: setenv MESASDK_ROOT /Applications/mesasdk
- For the Bourne shell: export MESASDK_ROOT=/Applications/mesasdk
- Initialize the SDK (also checks compatibility):
- For the C shell: source $MESASDK_ROOT/bin/mesasdk_init.csh
- For the Bourne shell: source $MESASDK_ROOT/bin/mesasdk_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) 9.2.0
If it doesn't, then you should consult the Troubleshooting section below.
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 ~/.bash_profile for the Bourne shell).
Usage
See the usage instructions above for Linux (they are the same for OS X).
Math Slots
It's often convenient to have different versions of the same math libraries available through a single SDK installation — for instance, one optimized for speed, one for accuracy, and so on. To this end, recent releases (>= 20.3.1) of the SDK support a feature known as 'math slots'. By setting the MESASDK_MATH_SLOT environment variable, you can chose which set of math liberaries ('slot') gets used at compile time. Possible choices are as follows:
MESASDK_MATH_SLOT choice | Description |
---|---|
default | Default (no special optimizations or modifications) |
crmath | Correctly-rounded math, via the crlibm library |
If MESASDK_MATH_SLOT is not set, then the default slot is used. Note that when compiling MESA it isn't necessary to set MESASDK_MATH_SLOT yourself; the build scripts take care of it.
Making Movies
The SDK includes the ffmpeg encoder and a simple script, images_to_movie, which uses ffmpeg to create movies from PNG files produced by MESA.
To illustrate the script in action, suppose the &pgstar section of the MESA inlist file contains the following parameters:
⋮ Grid6_file_flag = .true. Grid6_file_dir = 'png' Grid6_file_prefix = 'grid6_' ⋮
This will make MESA write a sequence of PNG images into the png subdirectory, with filenames grid6_NNNNN.png (where N represents a single digit). To combine these files together into a movie, run the following command from the same directory MESA was run in:
This will produce an MPEG4 movie, with the filename movie.mp4. The type of movie produced is determined from the file extension. Other choices are possible (e.g., mpg for MPEG2), but the images_to_movie.sh script is specifically targeted at producing MPEG4 output, so it might be best to stick with the mp4 extension unless you know what you're doing.
IMPORTANT NOTE: In the example above, the quotes (' ') are necessary to prevent the shell from prematurely expanding the wildcard (*) character.Installing as Root User
If you wish to install the SDK as the root user, that's fine — but you must run the initialization script at least once as root, before you can use the SDK as an ordinary user. This is because configuration files are written into the $MESASDK_ROOT/etc directory on first initialization; and these files must be written as root if you installed as root.
Troubleshooting
If you encounter an error during the build process, please consult the FAQ first. If your problem is not resolved, then you should submit a bug report to the MESA Forum. Be sure to include the following information in your bug report:
- The version of MESA you are trying to build
- The version of the SDK you are using (use the mesasdk_version.sh command to determine this)
- Your platform (machine type, operating system, version)
Also, it would be helpful if you could post the output of the following commands:
- uname -a
- gfortran -v
- echo $MESASDK_ROOT
- echo $PATH
Frequently Asked Questions (FAQ)
Q: When trying to download the SDK using wget, I get the error
403: Forbidden
A: Our web server is set up to reject requests from wget. As a workaround, add the flag --user-agent=' to your wget invocation.
Q: How can I download the SDK from the command line?
A: Use the wget tool. For instance, to download the Linux version dated YYYYMMDD, run
![Download Sdk For Mac Os X Download Sdk For Mac Os X](/uploads/1/1/9/5/119586140/427385705.png)
wget --user-agent=' http://www.astro.wisc.edu/~townsend/resource/download/mesasdk/mesasdk-x86_64-linux-YYYYMMDD.tar.gz
(See the question above for a discussion of why the --user-agent=' flag is necessary.)
Q: The initialization script produces errors of the sort
mesasdk_init.sh: checking architecture touch: cannot touch '/opt/mesasdk/etc/check_arch.done': Permission denied
A: This is occurring because you installed the SDK as a different user (e.g., root). You must run the initialization script at least once as the installation user, before running as any other user.
Q: When compiling, I'm encountering the error
file locking disabled on this file system (use HDF5_USE_FILE_LOCKING environment variable to override)
A: To fix this, set the HDF5_USE_FILE_LOCKING environment variable to FALSE. This can be done via the command
Updated 2020-09-28 12:19:47
-->In this article, you'll learn how to install .NET Core on macOS. .NET Core is made up of the runtime and the SDK. The runtime is used to run a .NET Core app and may or may not be included with the app. The SDK is used to create .NET Core apps and libraries. The .NET Core runtime is always installed with the SDK.
The latest version of .NET Core is 3.1.
Supported releases
The following table is a list of currently supported .NET Core releases and the versions of macOS they're supported on. These versions remain supported either the version of .NET Core reaches end-of-support.
- A ✔️ indicates that the version of .NET Core is still supported.
- A ❌ indicates that the version of .NET Core isn't supported.
Operating System | .NET Core 2.1 | .NET Core 3.1 | .NET 5 Preview |
---|---|---|---|
macOS 10.15 'Catalina' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.14 'Mojave' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.13 'High Sierra' | ✔️ 2.1 (Release notes) | ✔️ 3.1 (Release notes) | ✔️ 5.0 Preview (Release notes) |
macOS 10.12 'Sierra' | ✔️ 2.1 (Release notes) | ❌ 3.1 (Release notes) | ❌ 5.0 Preview (Release notes) |
Unsupported releases
The following versions of .NET Core are ❌ no longer supported. The downloads for these still remain published:
- 3.0 (Release notes)
- 2.2 (Release notes)
- 2.0 (Release notes)
Runtime information
The runtime is used to run apps created with .NET Core. When an app author publishes an app, they can include the runtime with their app. If they don't include the runtime, it's up to the user to install the runtime.
There are three different runtimes you can install on macOS:
ASP.NET Core runtime
Runs ASP.NET Core apps. Includes the .NET Core runtime.
Runs ASP.NET Core apps. Includes the .NET Core runtime.
.NET Core runtime
This runtime is the simplest runtime and doesn't include any other runtime. It's highly recommended that you install ASP.NET Core runtime for the best compatibility with .NET Core apps.
This runtime is the simplest runtime and doesn't include any other runtime. It's highly recommended that you install ASP.NET Core runtime for the best compatibility with .NET Core apps.
SDK information
The SDK is used to build and publish .NET Core apps and libraries. Installing the SDK includes both runtimes: ASP.NET Core and .NET Core.
Dependencies
.NET Core is supported on the following macOS releases:
.NET Core Version | macOS | Architectures | |
---|---|---|---|
3.1 | High Sierra (10.13+) | x64 | More information |
3.0 | High Sierra (10.13+) | x64 | More information |
2.2 | Sierra (10.12+) | x64 | More information |
2.1 | Sierra (10.12+) | x64 | More information |
Beginning with macOS Catalina (version 10.15), all software built after June 1, 2019 that is distributed with Developer ID, must be notarized. This requirement applies to the .NET Core runtime, .NET Core SDK, and software created with .NET Core.
The installers for .NET Core (both runtime and SDK) versions 3.1, 3.0, and 2.1, have been notarized since February 18, 2020. Prior released versions aren't notarized. If you run a non-notarized app, you'll see an error similar to the following image:
For more information about how enforced-notarization affects .NET Core (and your .NET Core apps), see Working with macOS Catalina Notarization.
libgdiplus
.NET Core applications that use the System.Drawing.Common assembly require libgdiplus to be installed.
An easy way to obtain libgdiplus is by using the Homebrew ('brew') package manager for macOS. After installing brew, install libgdiplus by executing the following commands at a Terminal (command) prompt:
Install with an installer
macOS has standalone installers that can be used to install the .NET Core 3.1 SDK:
Download Apple Os For Windows
Download and manually install
As an alternative to the macOS installers for .NET Core, you can download and manually install the SDK and runtime. Manual install is usually performed as part of continuous integration testing. For a developer or user, it's generally better to use an installer.
If you install .NET Core SDK, you don't need to install the corresponding runtime. First, download a binary release for either the SDK or the runtime from one of the following sites:
- ✔️ .NET 5.0 preview downloads
- ✔️ .NET Core 3.1 downloads
- ✔️ .NET Core 2.1 downloads
Next, extract the downloaded file and use the
export
command to set variables used by .NET Core and then ensure .NET Core is in PATH.To extract the runtime and make the .NET Core CLI commands available at the terminal, first download a .NET Core binary release. Then, open a terminal and run the following commands from the directory where the file was saved. The archive file name may be different depending on what you downloaded.
Use the following command to extract the runtime:
Use the following command to extract the SDK:
Tip
The preceding
export
commands only make the .NET Core CLI commands available for the terminal session in which it was run.You can edit your shell profile to permanently add the commands. There are a number of different shells available for Linux and each has a different profile. For example:
- Bash Shell: ~/.bash_profile, ~/.bashrc
- Korn Shell: ~/.kshrc or .profile
- Z Shell: ~/.zshrc or .zprofile
Edit the appropriate source file for your shell and add
:$HOME/dotnet
to the end of the existing PATH
statement. If no PATH
statement is included, add a new line with export PATH=$PATH:$HOME/dotnet
.Also, add
export DOTNET_ROOT=$HOME/dotnet
to the end of the file.This approach lets you install different versions into separate locations and choose explicitly which one to use by which application.
Install with Visual Studio for Mac
Visual Studio for Mac installs the .NET Core SDK when the .NET Core workload is selected. To get started with .NET Core development on macOS, see Install Visual Studio 2019 for Mac. For the latest release, .NET Core 3.1, you must use the Visual Studio for Mac 8.4.
Install alongside Visual Studio Code
Visual Studio Code is a powerful and lightweight source code editor that runs on your desktop. Visual Studio Code is available for Windows, macOS, and Linux.
While Visual Studio Code doesn't come with an automated .NET Core installer like Visual Studio does, adding .NET Core support is simple.
- Download and install Visual Studio Code.
- Download and install the .NET Core SDK.
- Install the C# extension from the Visual Studio Code marketplace.
Free Mac Os For Windows
Install with bash automation
The dotnet-install scripts are used for automation and non-admin installs of the runtime. You can download the script from the dotnet-install script reference page.
Download Mac Os X Free
The script defaults to installing the latest long term support (LTS) version, which is .NET Core 3.1. You can choose a specific release by specifying the
current
switch. Include the runtime
switch to install a runtime. Otherwise, the script installs the SDK.Note
The command above installs the ASP.NET Core runtime for maximum compatability. The ASP.NET Core runtime also includes the standard .NET Core runtime.
Java Jdk Download Mac Os X
Docker
Containers provide a lightweight way to isolate your application from the rest of the host system. Containers on the same machine share just the kernel and use resources given to your application.
.NET Core can run in a Docker container. Official .NET Core Docker images are published to the Microsoft Container Registry (MCR) and are discoverable at the Microsoft .NET Core Docker Hub repository. Each repository contains images for different combinations of the .NET (SDK or Runtime) and OS that you can use.
Microsoft provides images that are tailored for specific scenarios. For example, the ASP.NET Core repository provides images that are built for running ASP.NET Core apps in production.
For more information about using .NET Core in a Docker container, see Introduction to .NET and Docker and Samples.
Next steps
- How to check if .NET Core is already installed.
- Working with macOS Catalina notarization.
- Tutorial: Get started on macOS.
- Tutorial: Create a new app with Visual Studio Code.
- Tutorial: Containerize a .NET Core app.