Changes

The '''ConTeXt develops at suite''' is a fast pacecomplete, and sometimes beta releases have serious bugs. ConTeXt suite allows you up-to test the latest -date ConTeXt release without having to worry if an upgrade will mess an critical projectdistribution that can be upgraded efficiently. You It can have two (or multiple) also be used in parallel ConTeXt suiteswith existing TeX installations such as MikTeX, TeXLive, and freeze one for your critical projects, so forth. The suite does not include LaTeX packages and use the other one for experimentingbinaries.

Sometimes ConTeXt beta releases have issues. The ConTeXt suite allows you to test the latest ConTeXt release without worrying whether upgrading will corrupt a critical project. Multiple ConTeXt suite installations are possible. This allows, for example, a stable version and a beta version to run in parallel on the same computer. ConTeXt is also included in TeXlive. The ConTeXt suite is updated continuously, whereas ConTeXt in TeXlive is updated less often. In particular, <code>luatex</code> and <code>metapost</code> are under active development and their binaries are updated frequently. ConTeXt follows these developments, indeed often drives development. As the binaries included in the TeXlive distribution are only updated yearly, ConTeXt on TeXlive will necessarily be less current than the ConTeXt suite. (ConTeXt on TeXlive can be kept somewhat more current using the http://tlcontrib.metatex.org repository.) The ConTeXt suite is self-contained and can happily coexist alongside another installed TeX distribution.

| Akira Kakuto (from [http://w32tex.org W32TeX])|- align="left"! Windows/CygWin| cygwin| same binaries as mswin|- align="left" style="background-color:#EEEEEE;"! Windows, 32 bit| win32| Alias for mswin

! Windows, 64 bit| win64| |- align="left" style="background-color:#EEEEEE;"! Linux, 32-bit

| Hans Hagen, Mojca Miklavec, Alan Braslau| compiled with glibc 2.3.6Debian 8|- align="left" style="background-color:#EEEEEE;"

| Peter Münster||- align="left"! Linux, PowerPC| linux-ppc| Piotr Kopszak|Debian 8

! Linux, Arm ARM (low end.)| linux-armelarm| Boris Veytsman| in progressRaspbian 8

! Mac OS XLinux, Intel (32-bit)musl| osxlinuxmusl-intel| Richard Koch, Mojca Miklavec64|Alpine

| Richard Koch, Mojca Miklavec|Mac OS X 10.6

! Mac OS XFreeBSD, PowerPC| osx32-ppcbit| Richard Koch, Mojca Miklavecfreebsd

! Mac OS XFreeBSD, Universal Binaries64-bit| osxfreebsd-universal| Richard Koch, Mojca Miklavecamd64

! FreeBSDOpenBSD 6.4, 32-bit| freebsd| Alan Braslauopenbsd6.4

! FreeBSDOpenBSD 6.4, 64-bit| freebsdopenbsd6.4-amd64| Alan Braslau|

! kFreeBSD| kfreebsdOpenBSD 6.5, 32-i386bit| Alan Braslauopenbsd6.5| FreeBSD + glibc (Debian)

! kFreeBSDOpenBSD 6.5, 64-bit| kfreebsdopenbsd6.5-amd64| Alan Braslau| FreeBSD + glibc (Debian)

| Marco Patzer|Solaris 10 on [http://www.opencsw.org/about/ OpenCSW]

We need volunteers for providing * If you run into problems installing, check the available architectures in the minimal’s [http://minimals.contextgarden.net/setup/ setup folder]!* OpenBSD 6.4 binaries for other platforms. are compiled but are missing in the setup folder ATM (2019-07) If you want to support a new platform, please write to the [[ConTeXt Mailing Lists]]

* graphicsmagick (convert) : for converting GIF and TIFF images

* curl zip or 7zip : for including remote contentEPUB generation

ConTeXt macro files are small (less than 10MB), but the suite comes with various free fonts which considerably increase the size of the distribution (to around 200MB). == Multiple instances of the installation ==Please note from the start that we recommend installing a complete ConTeXt installation for each project in a production environment. The installation tree is portable (see Moving the Installation Around, below) and can be located under the project's own directory. The advantage is to allow each project to use an instance of ConTeXt that is adapted to its coding and that only gets updated purposely. Since the ConTeXt Standalone is "bleeding edge" and subject to development, certain details in commands, syntax or rendering may evolve slightly. Having a vintage ConTeXt tree for each production project insures that one can come back years later and produce identical results. So as not to get carried away under this approach, one can eventually group projects by vintage, period or season, according to cycles of productivity.

For Mac installation see also [http=== (MacOS X) Using the Command line://wikiTerminal.contextgardenapp === If you do not what a command tool is, do not worry.net/Mac_Installation Mac installation page]It is simply a program in which commands are entered as text and then executed. The needed Terminal.app can be found in the Utilities-folder of the Applications-Folder. Once you have started Terminal, all you have to do is enter a command and press the RETURN-key and the command will be executed.

Select a folder where you want to install ConTeXt. We recommend that you can use your <code>$HOME/context</code> directory. Create this folder. Then download [http://minimals.contextgarden.net/setup/first-setup.sh first-setup.sh] and place it in <code>$HOME/context</code> directory. Open a terminal, then:...

execute (Linux/FreeBSD/Solaris):<pre> mkdir ~/context cd ~/context wget http://minimals.contextgarden.net/setup/first-setup.sh</pre>

Then make or (MacOS):<codepre> mkdir ~/context cd ~/context rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh.</codepre> executable and run it to download Since the whole distribution and make formats:Mac does not have `wget` pre-installed.

chmod +x Now run the `first-setup.sh` script:<pre> # Install the latest beta of ConTeXt # This takes a long time, so go have a coffee sh ./# Flags you can add to the first-setup.shcall: # --modules=all # Install all third-party modules # --context=latest # Install latest stable version # --engine=luatex # Install only MkIV, leave out MkII # # This shrinks the install from 270 MB to 200 MB

This takes a long time, so go have a coffee sh ./first-setup.sh --modules=all</pre>

sh A system wide installation is '''only''' recommended for experienced users./firstYou will need administrator rights on the Mac as only administrators are allowed to install programs in the Applications folder, or root (sudo) privileges on other unix-setuplike systems.sh --context=current

By default, the suite does ''not'' install modules and other third party content. If * on Linux you want the modules (and have the bandwidth), can use <code>/opt/context</code>* on MacOS X you can use<code>/Applications/ConTeXt</code>

sh Note that, at present, while ''using'' MkIV, you need to have write permissions for the <code>$TEXMFCACHE</code> directory./first-setupThis effectively means that only one user will be able to generate the formats unless you set the group permissions appropriately.sh --modules=allFor example:

sh <pre> # Create the /opt/context directory -- change as appropriate or desired if you # want a different installation directory. cd /opt mkdir context cd context # Fetch the install script (use rsync on the mac, see above) wget http://minimals.contextgarden.net/setup/first-setup.sh # Install the latest beta of ConTeXt # This takes a long time, so go have a coffee # Flags you can add to the first-setup.sh call: # --modules=all # Install all third-party modules # --context=latest # Install latest stable version # --engine=luatex # Install only MkIV, leave out MkII # # This shrinks the install from 270 MB to 200 MB

sh ./first-setup.sh --modules== Systemall  # change ownership to real rather than effective id chown -R `id -r -u`:`id -r -wide installation ==g` .</pre>

chown `whoami` -R Add the OSFONTDIR into ./opttex/context setuptex. Go to under the line:

(<code>`whoami`< export OSFONTDIR="/usr/local/share/fonts;$HOME/code> outputs your user name, you can type that directly, of course.)fonts"

In order to install the suite, open a terminal, go to the installation directory and download For more information: [http://minimals.contextgarden.net/setup/first-setup.sh first-setup.sh[Fonts in LuaTeX]]:

Then run that script Another common use case is invoking ConTeXt from within a web application. Because web directories are often self-contained, and in the case of Apache under Ubuntu, ownership of the directory and its contents are assigned to download the whole distribution a user and make formatsgroup without a login shell, e.g., <code>www-data: sh .www-data</firstcode> this prevents a web application from invoking a ConTeXt installation done using either the single-user or system-setupwide method listed above.sh

This takes a long timeIn this case the solution is to install ConTeXt within the website tree, so go have a coffeeand ideally in the public sub-tree. The public sub-tree is commonly the home directory for the application and relative pathnames are resolved as if immediately below it.

By defaultFor example, in the suite installs ConTeXt beta. If you want case of the stable version of PHP web framework Laravel, ConTeXt, you can usebe installed alongside other assets in the <path-to-document-root>/public/context directory:

sh <pre> cd <path-to-document-root>/public mkdir context cd context wget http://minimals.contextgarden.net/setup/first-setup.sh # Install the latest beta of ConTeXt # This takes a long time, so go have a coffee # Flags you can add to the first-setup.sh call: # --modules=all # Install all third-party modules # --context=currentlatest # Install latest stable version # --engine=luatex # Install only MkIV, leave out MkII # # This shrinks the install from 270 MB to 200 MB

By default, the suite does ''not'' install modules and other third party content sh ./first-setup. If you want the sh --modules (and have the bandwidth), you can use=all</pre>

sh .Once installed, you need to ensure that the permissions are correct for Apache to be able to access it (you will either need <code>sudo</first-setup.sh --modules=allcode> privileges or root access):

Normaly Now as part of your application's invocation of ConTeXt, you do not want will need to allow access in eset up the shell environment.g. /opt. but you like This is easily done by creating a simple BASH shell script, also to allow it be installed in /var/cache/*. So create the needed cache directory as a superuser viapublic part of the document tree:

mkdir /var/cache/context<pre> mkdir /var/cache/context/texmf-cache chmod 777 /var #!/cacheusr/contextbin/texmf-cacheenv bash

Change # # proccontext.sh # # To be installed in the file ./tex/texmf/web2c/texmfcnf.lua the value of TEXMFCACHE <path-to the directory you want (in this example -document-root>/varpublic/cache/context/texmf-cache).bin

Add the OSOFONTDIR into . cd tex/spool context $1 > /textmp/setuptexcontext_run. Go to under the line:log</pre>

Now within your application, you can invoke this shell script (if you don't have the line above, go to the end of the filein this case using PHP) and add there:

export OSFONTDIR<pre> $cmd ="bin/usr/local/share/fontsproccontext.sh $input_filename"; $HOMElast_line = system($cmd, $ret_val);</.fonts"pre>

For more information: [[Fonts And the output will once again be found in LuaTeX]]<code><path-to-document-root>/tex/spool</code>.

There’s a [httphttps://aur.archlinux.org/packages.php?ID=30398 /context-minimals-git PKGBUILD] in

If you === Terminal/Command line === To run context from a terminal, source <code>setuptex</code> like so:

=== Exclusive usage ===

The above method means that you always have to type <code>source /installation-dir/tex/setuptex</code> in a terminal before you can use typeset. If you always use ConTeXt suite and '''never ''' use LaTeX or plain TeX provided by another TeX distribution, you can add the above intialization following line to the startup script of your shell. (For bash, this means the startup script is <code>$HOME/.bashrc</code>; for zsh, this means it is <code>$HOME/.zshrc</code>; for (t)csh, this means <code>$HOME/.cshrc</code> or <code>$HOME/.tcshrc</code>. Then, <code>setuptex</code> will always be sourced in your terminal.

If you run ConTeXt from an editor, you need to source {{Then <code|>setuptex}} </code> will always be sourced in a terminal and then open your editor from the same terminal.

Depending on how your === Integrating with an editor initializes, you may still need to source {{code|setuptex}} in order to run ConTeXt directly from your editor. In theory, it is sufficient to add {{code|/installation-dir/tex/texmf-<platform>/bin}} to your {{code|$PATH}} in order to use the suite. You can try to add this to the paths that your editor searches.===

For information about configuring [http://smultronThe easiest way to run ConTeXt from an editor is to open a terminal, source {{code|setuptex}} in the terminal, and then open your editor '''from the same terminal'''.sourceforge.net Another option is to add {{code|/ Smultron] and [http:installation-dir/tex/www.uoregon.edutexmf-<platform>/~koch/texshop/obtainingbin}} to the {{code|$PATH}} that the editor searches.html TeXShop] (which are popular TeX editors The details vary depending on Mac) see [[ConTeXt Standalone/Mac Installation]]the editor. For a list of text editors with ConTeXt integration, see the article on See [[Text Editors|text editors]]for instructions on integrating ConTeXt with various editors.

sh ./first-setup.sh --modules=all</pre> To update retain currently-installed modules:<pre>sh ./first-setup.sh --keep

Download [http://minimals.contextgarden.net/setup/context-setup-mswin.zip context-setup-mswin.zip] or [[http://minimals.contextgarden.net/setup/context-setup-win64.zip context-setup-win64.zip]], and unzip to a directory where you want to install ConTeXt. It is recommended that you choose a directory that does not have a space in its full path. Then open <code>cmd.exe</code>, go to the installation directory and run

first-setup.bat --context=currentlatest

This starts up a new command shell with the environment pre-loaded. Within the new shell you can just type <code>context</code> to run ConTeXt. E.g.  C:\> context --version to check that you are running the version you think you're running.

If you used the command line method, just run <code>first-setup.bat</code> again to update the suite. If you have third party modules installed, you should use first-setup.bat --keepto upgrade. See [[ConTeXt_Standalone#Installing_third_party_modules| Installing third party modules]] for details.