Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision		 Previous revision
download:sac2c [2021/05/24 09:40] – update binary release hnvdownload:sac2c [2022/02/03 10:58] (current) – removed sbs
Line 1: Line 1:
-===== Download Binaries ===== 
  
-<callout type="primary" icon="true"> 
-=== Latest Release === 
-The latest release of the compiler and standard library as of 08.04.2021 is [[https://gitlab.sac-home.org/sac-group/sac-packages/-/releases/v1.3.3-659-1|v1.3.3-659-1]] 
-</callout> 
- 
-Binary releases of the compiler and the standard library are provided via our package repository, at https://gitlab.sac-home.org/sac-group/sac-packages/-/releases. We support most //UNIX*// operating systems, including 
-**RPM**, **DEB**, and **MacOS**. Running on Windows is possible using [[https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux|WSL]]. 
- 
-Other operating systems may have packages, see [[:download:sac2c#rd-party_packages|3rd-party packages]]. 
- 
-Please message use on the [[:mailing_lists#user_mailing_lists|user mailing list]] if you encounter any problem. 
- 
-//Note, you can compile the standard library yourself if you prefer, see below.// 
- 
-=== Package Variants === 
- 
-We provide two types of packages variants, **basic** and  **full**. 
- 
-<callout type="primary" icon="true"> 
-=== Which variant should I use? === 
-For normal usage, the **basic** variant is sufficient to try out all of the features of the Single Assignment C language. 
-</callout> 
- 
-<HTML> 
-<dl> 
-  <dt><b>Basic package</b></dt> 
-    <dd>&mdash; package excludes special features, like the GPU backend or advanced multi-threading scheduling.</dd> 
-    <dd>&mdash; makes use of minimal external dependencies: <em>gcc, libc, uuid-lib</em>.</dd> 
-  <dt><b>Full package</b></dt> 
-    <dd>&mdash; package includes GPU backend and advanced multi-threading scheduling.</dd> 
-    <dd>&mdash; more external dependencies: <em>gcc, libc, uuid-lib, hwloc, cuda<em>*</em></em></dd> 
-    <dd>* <i>CUDA must be installed as per the recommended guidelines of the distribution. Our packages are built using <a href="https://hub.docker.com/r/nvidia/cuda">docker containers</a> provided by NVIDIA, look there for their installation procedure.</i></dd> 
-</dl> 
-</HTML> 
- 
-=== 3rd-Party Packages  === 
- 
-We also have some //user-contributed// packages --- as these are packages outwith the project, we can not provide any support on these. Please communicate with the package maintainers directly. 
- 
-{{tablelayout?colwidth=","}} 
-^ OS ^ External Link ^ 
-| ArchLinux | via [[https://aur.archlinux.org/packages/sac-compiler-weekly|sac-compiler-weekly]] and [[https://aur.archlinux.org/packages/sac-stdlib-weekly|sac-stdlib-weekly]] | 
-|NixOS | via [[https://github.com/cxandru/sac-nix|sac-nix]] (thank you cxandru) | 
- 
-==== Installing ==== 
- 
-Please make sure that your system is properly setup to run SaC --- at the very least you need to have a working C-compiler. 
- 
-Note that on MacOS you must have Xcode installed and configured for command line usage. If you use [[https://www.brew.sh|brew]] or [[https://www.macports.org|macports]], this may already be done for you. 
- 
-<accordion> 
-<panel type="default" title="RPM (RedHat Based distributions)"> 
-The ''rpm'' release of the compiler is designed to be installed on RedHat based distributions of Linux (e.g. RedHat, CentOS, Fedora, etc.) using the ''dnf'' or ''rpm'' tool set. 
- 
-Installation: 
-<code> 
-$ sudo dnf install sac2c-VERSION-RELEASE.rpm 
-</code> 
-or 
-<code> 
-$ sudo rpm --install sac2c-VERSION-RELEASE.rpm 
-</code> 
-</panel> 
-<panel type="default" title="DEB (Debian based distributions)"> 
- 
-The ''deb'' package is meant to be installed on Debian based distributions (e.g. Debian, Ubuntu, etc.) using the ''dpkg'' or the ''apt'' tool set. 
- 
-Installation: 
-<code> 
-$ sudo dpkg --install sac-VERSION-RELEASE.deb 
-</code> 
-or 
-<code> 
-$ sudo apt install sac-VERSION-RELEASE.deb 
-</code> 
-</panel> 
-<panel type="default" title="Pkg (Apple MacOS)"> 
-The ''pkg'' is an installer that will place the SaC files in the correct location on your system. Symbolic links to the SaC binaries are created in ''/usr/local/bin'' for your convenience. 
- 
-The SaC binaries are postfixed by their release type (production or debug), so there is a ''sac2c_p'' and ''sac2c_d'' respectively, ''sac2c'' is simply a link to ''sac2c_p''. 
- 
-Installation: 
-  - Double click the downloaded ''pkg'' file 
-  - A dialog box should appear that will guide you through the install process 
-  - Confirm that you agree with our license, and click //Install// to install SaC 
-  - The binary ''sac2c_p'' should be in your ''PATH'' 
-</panel> 
-<panel type="default" title="TAR.GZ (Unix-like operating systems)"> 
-The ''.tar.gz'' archive is intended for arbitrary installs, meaning that if you can't install ''sac2c'' using one of the other packages due to system permissions, you can use this archive to install it under you home-directory. The libraries of the compiler can be placed anywhere so long as the ''sac2c'' binary (and related) know where to find them. For this reason the archive provides the ''sac2c'' binary (and related) as source code to be compiled by the end-user. 
- 
-For simplicities sake, an install script is provided. It supports several flags, but the most important one is ''-i'' to indicate where you want to install everything (for example ''~/.local''). 
- 
-<alert type="warning" icon="fa fa-warning">**Be Aware** Please remember to install all dependencies of the compiler before attempting to use it</alert> 
- 
-Installation of the compiler is as simple as extracting from the archive: 
-<code> 
-$ mkdir ~/temp_extract && cd ~/temp_extract 
-$ tar -xzf sac2c-VERSION-RELEASE.tar.gz 
-$ nano README                            # if you want more information on the install 
-$ bash ./install.sh -i INSTALL_DIR       # and thats it 
-$ cd ~ && rm -rf temp_extract 
-</code> 
-</panel> 
-<panel type="default" title="Windows 10"> 
-While we do not currently support a native Windows version, you can still use it through a virtualisation layer 
-of your choosing. The easiest way to use ''sac2c'' on a Windows 10 system is to use Window's own virtualisation 
-for Linux support, the Windows Subsystem for Linux (WSL). 
-To do this, you have to do four things: 
-  - You need to activate the developer mode of Windows. (Settings -> Update & Security -> For developers -> tick the Developer Mode) 
-  - You need to activate the WSL. (Control Panel -> Programs -> Programs & Features -> Turn Features On & Off -> tick Windows Subsystem for Linux) 
-  - Go to the Microsoft Store and choose a Linux Distribution of your choice, e.g, Ubuntu 18.04 LTS. 
-  - Download the //basic// version of ''sac2c'' and ''sac-stdlib'' that matches the Linux version you have chosen and install it. For Ubuntu, you download the corresponding ''.deb'' files and then run 
-<code> 
-$ sudo apt update 
-$ sudo apt install sac2c-VERSION-RELEASE.deb 
-$ sudo apt install sac-stdlib-VERSION-RELEASE.deb 
-</code> 
- 
-After that, you should have the sac system up and running: 
-the SaC binaries are postfixed by their release type (production or debug), so there is a ''sac2c_p'' and ''sac2c_d'' respectively, ''sac2c'' is simply a link to ''sac2c_p''. 
-</panel> 
-</accordion> 
- 
-==== Contribute? ==== 
- 
-Interested in contributing to the project? You can do so in several ways, by either telling us about bugs or by contributing code to the project. 
- 
-=== Reporting bugs === 
- 
-Head over to the [[:bugzilla|community]] page and follow the guidelines there on how to submit a bug. 
- 
-=== Contributing code === 
- 
-  * Create an account on this site by [[:index?do=register|registering]], 
-  * and send an email to [[info@sac-home.org]] indicating that you'd like to have access to the compiler sources.