Changes

We wanted to provide:* an easy to (no-need-to-)install Sometimes ConTeXt distribution* a '''fast and convenient way to update beta releases have issues. The ConTeXt and binaries 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''' ''(no need to fetch 100 MB when only minimal modifications have been made in the distribution)''* and a refence ConTeXt distribution* an easy way to revert beta version to an older ConTeXt (run in case the latest one is broken)* probably some combination of rsync and svn will be used, but parallel on the exact concept is still not completely clearsame computer.

We do not plan to provide:* LaTeX packages ''(perhaps the really-basic-latex as an add-on packageConTeXt is also included in TeXlive. The ConTeXt suite is updated continuously, but only if someone else has time to investigate what whereas ConTeXt in TeXlive is needed)''* extensive support for whatever updated less often. In particular, <code>luatex</code> and <code>metapost</code> are under active development and their binaries or packages which are otherwise standard 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. The ConTeXt suite is self-contained and can happily coexist alongside another installed TeX distributions: use TeX Live or MikTeX for that purposedistribution.

= Supported platforms General Information =

* Windows* Linux* Linux, 64 bit* Mac OS X Intel* Mac Os X PPC* other == Supported platforms on request (please send a mail to the ntg-context mailing list)==

{| style= Installation "border:1px solid #DDDDDD;"|- align="left" ! Platform! Short name! Notes|- align="left" style="background-color:#EEEEEE;"! Windows| mswin| 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|- align="left"! Windows, 64 bit| win64| |- align="left" style="background-color:#EEEEEE;"! Linux, 32-bit| linux| Debian 8|- align="left"! Linux, 64-bit| linux-64| Debian 8|- align="left" style="background-color:#EEEEEE;"! Linux, ARM (low end.)| linux-arm| Raspbian 8|- align="left"! Linux, musl| linuxmusl-64| Alpine|- align="left" style="background-color:#EEEEEE;"! Mac OS X, Intel (64-bit)| osx-64| Mac OS X 10.6|- align="left"! FreeBSD, 32-bit| freebsd||- align="left" style="background-color:#EEEEEE;"! FreeBSD, 64-bit| freebsd-amd64||- align="left"! OpenBSD 6.4, 32-bit| openbsd6.4||- align="left" style="background-color:#EEEEEE;"! OpenBSD 6.4, 64-bit| openbsd6.4-amd64||- align="left"! OpenBSD 6.5, 32-bit| openbsd6.5||- align="left" style="background-color:#EEEEEE;"! OpenBSD 6.5, 64-bit| openbsd6.5-amd64||- align="left"! Solaris, Intel| solaris-intel| Solaris 10 on [http://www.opencsw.org/about/ OpenCSW]|- align="left" style="background-color:#EEEEEE;"! Solaris, Sparc| solaris-sparc| Solaris 10 on [http://www.opencsw.org/about/ OpenCSW]|}

This is a description of how * If you run into problems installing, check the first installation and any subsequent updates should work available architectures in the minimal’s [http://minimals.contextgarden.net/setup/ setup folder]!* OpenBSD 6.4 binaries are compiled but are missing in the setup folder ATM (or how it would be nice if they worked that way2019-07):

One should be able If you want to support a new platform, please write to download <code>setup.zip</code> (approx. 2MB) which would download all the other things (selected engines, fonts, modules, ...) on demand. It should contain:* some really basic documentation (README, INSTALL)* setup script* texmf-[os[Mailing Lists]/bin/luatex + texlua symbolic link* ... [finishme]

We need to:== Dependencies ==* create files <code>README INSTALL</code>Rsync (The windows binary of rsync is distributed within the suite)

* create a file <code>first-setup(.sh, .bat)</code> (or with some other self-explanatory name), which:** checks if rsync exists (if The following programs are not, an error is issued, saying <code>please install rsync first</code>)** checks required for perl and ruby and issues a similar error/warning (in fact, we can still proceed to the next step and download things even if perl & ruby are not installedrunning ConTeXt, but that doesn't make much sense)** detects the platform (straightforward for windows, for unix-like platforms the same kind of detection is used as later in <code>setuptex</code>)** does rsync to installation files themselves (in case mtx-update has changed in the mean time)** reads in <code>context-minimals-seetings.lua</code> (which engines, formats, fonts, modules to download ...) if interactive is set to true, ask for default settings again, otherwise respect those settings and continue** asks for their installation location** creates (or updates) the file with settings (if interactive)** fetch files with rsync** create formats** suggest what to put into <code>adds additional functionality.bash_profile</code> (or equivalent locations) to have context initilized automatically

Binaries == Disc space required ==ConTeXt macro files are mostly taken from TeX Live 2007small (less than 10MB), but new ones are used whenever availablethe suite comes with various free fonts which considerably increase the size of the distribution (to around 200MB).

== Sources Multiple instances of binaries 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.

* TeX Live 2007 for most binaries and most platforms* Akira's W32TeX for windows binaries (including metapostSo as not to get carried away under this approach, LuaTeXone can eventually group projects by vintage, pdfTeX and XeTeX) - automatic* for pdfTeXperiod or season, XeTeX, LuaTeX and metapost for other platforms added manually whenever possible (nice if it could be automated, but no idea how)* texmf/scripts/context/stubs from ConTeXtaccording to cycles of productivity.

== List of included binaries Standalone ==

=== Core binaries ===''We will do our best to keep them as up to date as possible. If they're still not up to date for your platform and you know where to find them, please notify us, we will fix that. We might provide XeTeX and LuaTeX in separate packages (on TODO list).''* pdftex[[ConTeXt Standalone/FAQ|Standalone/FAQ]] * luatex[[ConTeXt Standalone/Structure|Standalone/Structure]] * texlua, texluac ''(only symlinks on "unix" platforms, in Akira's distribution luatex.dll is used + 3 small executables)''[[ConTeXt Standalone/Implementation|Standalone/Implementation]]* xetex, xdvipdfmx[[ConTeXt Standalone/TODO|Standalone/TODO]] * ''metapost''[[ConTeXt Standalone/Contents|Standalone/Contents]] ** dvitomp[[ConTeXt Standalone/TeX Live|Standalone/TeX Live]]** makempx** mpost** mpto ''(can this be replaced by ConTeXt's variant in future?)''Browse the [http://minimals.contextgarden.net installation tree]

=== FontUnix-related like platforms (Linux/MacOS X/FreeBSD/Solaris) ===''Might be removed or moved to a special category of "font-related binaries", and only available as an additional package.''* ''only left for testing** afm2pl** afm2tfm** ttf2afm* Knuth's** pltotf** tftopl** vftovp** vptovf

=== Might-be-removed-soon (MacOS X) Using the Command line: Terminal.app ===* dvipdfmx* dvips

=== Windows-only ===''Additional standard toolsIf you do not what a command tool is, such do not worry. It is simply a program in which commands are entered as unzip etctext and then executed. TODOThe needed Terminal.app can be found in the Utilities-folder of the Applications-Folder.''

Fonts are split in three packages:* used in both pdfTeX and XeTeXexecute (Linux/FreeBSD/LuaTeX: mostly math (pfb, map, enc, tfmSolaris)* used in pdfTeX only: pfb, map, enc, tfm (those that are not present in "common")* used in XeTeX/LuaTeX only: otf

Currently we have ({{note|You almost certainly want to [[Installation|install the latest versionnewer ConTeXt LMTX]]. This guide is for installing the older, in sync with CTAN):* Latin Modern* Antykwa Torunska* Iwona & Kurier* TeX Gyre* amsrarely-updated MkIV distribution.}}

Other fonts to be added<pre> mkdir ~/context cd ~/context wget http://minimals.contextgarden.net/setup/first-setup.sh* TODO</pre>

It is possible that we'll provide or (MacOS):<pre> mkdir ~/context cd ~/context rsync -av rsync://contextgarden.net/minimals/setup/first-setup.sh .</pre>Since the Mac does not have `wget` pre-installed. Now run the `first-setup.sh` script:<pre> # Install the latest beta of ConTeXt # This takes a long time, so go have a really minimal package with LM 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 onlyMkIV, and additional three packages (common, for new TeX, for old TeX) with all leave out MkII # # This shrinks the other fonts.install from 270 MB to 200 MB

= Third sh ./first-setup.sh --party modules & Other =all</pre>

* TODO* also cont== System-* from Hans's pagewide installation ==

* upload <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 binaries 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 Delta 270 MB to 200 MB  sh ./first-setup.sh --modules=all  # change ownership to real rather than effective id chown -R `id -r -u`:`id -r -g` .</pre> ===Cache=== To customize the cache directory and other options, see the [[Custom_Configuration|Custom Configuration]] page. ===Font Directory=== Add the OSFONTDIR into ./tex/setuptex. Go to under the line:  # TODO: we could set OSFONTDIR on Mac for example (if you don't have the line above, go to the end of the file) and add there:  export OSFONTDIR="/usr/local/share/fonts;$HOME/.fonts" For more information: [[Fonts in LuaTeX]] == Apache webserver installation == 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 a user and group without a login shell, e.g., <code>www-data:www-data</code> this prevents a web application from invoking a ConTeXt installation done using either the single-user or system-wide method listed above. In this case the solution is to install ConTeXt within the website tree, and 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. For example, in the case of the PHP web framework Laravel, ConTeXt can be installed alongside other assets in the <path-to-document-root>/public/context directory: <pre> cd <path-to-document-root>/public mkdir context cd context wget http://minimals.contextgarden.net/rsyncsetup/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=all</pre> 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</windowscode> privileges or root access): * reorganize fonts into fonts<pre>$ cd <path-to-document-root>/public$ sudo chmod -R www-data:www-datacontext</pre> Now as part of your application's invocation of ConTeXt, you will need to set up the shell environment. This is easily done by creating a simple BASH shell script, also to be installed in the public part of the document tree: <pre> #!/usr/bin/env bash  # # proccontext.sh # # To be installed in <path-to-document-root>/public/bin  . <path-to-document-root>/public/context/tex/setuptex <path-to-document-root>/public/context/tex  cd tex/spool context $1 > /tmp/context_run.log</pre> Here the dynamically generated ConTeXt source file is expected to be found in the <code><path-to-document-root>/tex/spool</code> directory. Now within your application, you can invoke this shell script (in this case using PHP): <pre> $cmd = "bin/proccontext.sh $input_filename"; $last_line = system($cmd, $ret_val);</pre> And the output will once again be found in <code><path-to-document-root>/tex/spool</code>. ==Arch Linux==There’s a [https://aur.archlinux.org/packages/context-minimals-git PKGBUILD] inthe AUR, provided by Aditya [https://github.com/adityam/context-pkgbuild].Install it using your favorite AUR frontend, e.g. <pre>yaourt -S context-minimals-git</pre> This will get you a fresh, up-to-date Context tree in<tt>/opt/context-minimals</tt>. == The funtoo way == If you are using [http://funtoo.org funtoo] there are ebuilds that will make an installation as easy as installing any other package from portage. Take a look at the [[ConTeXt Standalone Funtoo]] Howto. This might also work for [http://www.gentoo.org gentoo], but is untested right now. == Proxy settings == The installation script uses <code>rsync</code> to fetch the required files. So, if you are behind a proxy server, you need to tell the details to rsync. The easiest way to set this is to set <code>RSYNC_PROXY</code> variable in the terminal or your startup script (<code>.bashrc</code> or the corresponding file for your shell). Replace username, password, proxyhost and proxyport with the correct information  export RSYNC_PROXY=username:password@proxyhost:proxyport Sometimes, when behind a firewall, port 873 may be closed for outgoing TCP connections. If port 22 is open for ssh connections, a trick that can be used is to connect to a computer located somewhere outside of the firewall and to tunnel port 873 (using the program <code>nc</code>).  export RSYNC_CONNECT_PROG='ssh tunnelhost nc %H 873' where <code>tunnelhost</code> is the machine outside of the firewall on which you have <code>ssh</code> access. Of course, this machine must have <code>nc</code> and port 873 open for outgoing TCP connections. == Usage == ConTeXt suite works in a non-interfering manner because it does not put anything in your <code>$PATH</code> and does not set any system variables. This in turn means that in order to use it, you need to do some initialization. An intialization script called <code>setuptex</code> is provided in <code>installation-dir/tex/</code>.  === Terminal/Command line === To run context from a terminal, source <code>setuptex</code>:  source /installation-dir/tex/setuptex === Exclusive usage === If you always use ConTeXt suite and '''never''' use LaTeX or plain TeX provided by another TeX distribution, you can add the following line to the startup script of your shell (For bash, the startup script is <code>$HOME/.bashrc</code>; for zsh it is <code>HOME/.zshrc</code>).  source /installation-dir/tex/setuptex Then <code>setuptex</code> will always be sourced in your terminal. === Integrating with an editor === The 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'''. Another option is to add {{code|/installation-foundrydir/texgyretex/texmf-<platform>/bin}} to the {{code|$PATH}} that the editor searches. The details vary depending on the editor. See [[Text Editors]] for instructions on integrating ConTeXt with various editors. == Updating == For updating the ConTeXt suite, first update <everythingcode>first-setup.sh</code>, then run it. You couldalso create an alias or a little script “ctx-update”with the following example contents:<pre>cd /opt/contextrsync -ptv rsync://contextgarden.net/minimals/setup/first-setup.sh .sh ./first-setup.sh --modules=all</pre> To update retain currently-installed modules:<pre>sh ./first-setup.sh --keep</pre> == Uninstalling == ConTeXt suite does not touch anything outside its installation folder. So to uninstall it, you can simply remove the installation folder. == Remaking formats == Normally, the update script should create the formats for you. If for some reason you need to recreate the formats, you can do the following: * For making MKII format.  mktexlsr texexec --make --all  * list For making XeTeX format  mktexlsr texexec --make --xtx --all  * For making MKIV format  mtxrun --generate context --make = Windows = If you want to use ConTeXt suite alongside MikTeX/TeXLive (needed if you also run LaTeX), follow the command-line installation method.  == Installation == === Command line method ===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 contentsand run {{note|You almost certainly want to [[Installation|install the newer ConTeXt LMTX]]. This guide is for installing the older, rarely-updated MkIV distribution.}}  first-setup.bat This takes a long time, so go have a coffee.  * list By default, the suite installs ConTeXt beta. If you want the stable version of ConTeXt, you can use   first-setup.bat --context=latest By default, the suite does ''not'' install modules and other third party content. If you want the modules (and have the bandwidth), you can use  first-setup.bat --modules=all  If the above installation instructions don't seem to answer your questions, see page [[Windows_Installation:_ConTeXt_Suite_with_SciTe| Windows Installation: ConTeXt Suite with SciTe]] for more detailed information. == Proxy settings == The installation script uses <code>rsync</code> to fetch the required files . So, if you are behind a proxy server, you need to tell the details to rsync. The easiest way to set this is to set <code>RSYNC_PROXY</code> variable in the terminal as (replace username, password, proxyhost and proxyport with the correct information)  set RSYNC_PROXY=username:password@proxyhost:proxyport or set the variable permanently as a Windows environment variable. Sometimes, when behind a firewall, port 873 may be closed for outgoing TCP connections. If port 22 is open for ssh connections, a trick that can be used is to connect to a computer located somewhere outside of the firewall and to tunnel port 873 (using the program <code>nc</code>).  export RSYNC_CONNECT_PROG='ssh tunnelhost nc %H 873' where <code>tunnelhost</code> is the machine outside of the firewall on which you have <code>ssh</code> access. Of course, this machine must have <code>nc</code> and port 873 open for outgoing TCP connections. == Usage == Before running ConTeXt, you need to run <code>setuptex.bat</code> which is provided in <code>installation-dir\tex\</code>. This can be done by typing installation-dir\tex\setuptex.bat on cmd.exe before you run ConTeXt. To avoid always having to type this, you can create a shortcut to cmd.exe and edit the command line to read (assuming you installed the suite in <code>C:\Programs</code>; otherwise replace <code>C:\Programs\</code> with your installation directory)  C:\WINDOWS\System32\cmd.exe /k C:\Programs\context\tex\setuptex.bat 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. === Use ConTeXt with Cygwin ===After installing the ConTeXt suite, you can run it under Cygwin. With Cygwin, you may use gmake and other Unix tools for your automated workflow. # Run <code>setuptex.bat</code> in DOS command prompt# In the same DOS prompt, enter Cygwin by running <code>cygwin.bat</code> (in your Cygwin installation directory)# Under Cygwin prompt, run <code> context.cmd test.tex </code>. Note that the <code>.cmd</code> extension is needed under Cygwin. == Updating == If you used the command line method, just run <code>first-setup.bat</code> again to update the suite.  == Uninstallation == If you used the command-line installer, you can just delete the installation directory to fetch uninstall the suite.  == Troubleshooting == * rsync sometimes has problems with paths with uppercase letters (like <code>c:\Temp</code> or <code>C:\Documents and Settings</code>). Installing into all-lowercase paths without spaces sometimes helps.* Directory-name length may also have an old effect, due to Windows's 8.3 filename conventions. An indicator is if running "texexec --lua" on a file produces missing-file warnings containing Windows-created 8-character directory names, such as "C:\CONTEX~1\tex", where your ConTeXt directory is really "C:\context_minimals\tex". Be conservative and choose a short name like "C:\ctm\tex". Also, this may even work when an 8-character-or-less directory name like "C:\ctexmin\tex" doesn't.* If you're behind firewall and rsync times out, you need to open port 873 for outgoing TCP connections.* If you update luaTeX occasionally you may get something like  <code>engine mismatch (luv: This is LuaTeX, Version beta-<version>-<date1> (TeX Live 2013/dev)(rev <number1>) <> bin: This is LuaTeX, Version beta-<version>-<date1> (TeX Live 2012/W32TeX)(rev <number2>)), forcing remake</code> In which case your format will be remade every time you compile a file. In /texmf-mswin make sure that luatex.exe and texlua.exe have the same date; then also delete luatex.dll. This usually solves the problem. = Installing third party modules = The ConTeXt suite only comes with Taco's [[Bibliography|t-bib]] module. If you want to install [http://modules.contextgarden.net/ a new module], say Wolfgang's [[Letter|t-letter]] module, you can use first-setup.sh --modules="t-letter" If you want to install more than one extra module, you can separate them by commas. So, to install the t-letter and t-mathsets module, do sh ./first-setup.sh --modules="t-letter,t-mathsets" If you want to install all extra modules at once, do sh ./first-setup.sh --modules=all = Reverting to an older installation = If, for some reason, you want to revert to an older installation, you can do that by  sh ./first-setup.sh --context=date where <code>date</code> is the date of one of the stable releases of ConTeXt. The complete list of old releases that are available is [http://minimals.contextgarden.net/current/context/ here].  = Moving the installation tree around =  According to this post, http://archive.contextgarden.net/message/20101129.144331.d721372f.en.html it's safe to move the installation tree across directory or machines (say you don't have broadband access). You just have to clean and regenerate the cache (./tex/texmf-cache/luatex-cache) with mtxrun --generate = Notes =<references/> {{Installation navbox}} [[Category:Installation]][[Category:Standalone]]