1,018
edits
Changes
Jump to navigation
Jump to search
= Current state of binaries in minimals =< [[ConTeXt Standalone]] | [[ConTeXt Standalone/Structure]] >
{| border="1"
! program
| windows || linux || linux-64 || mac-intel || mac-ppc || latest || TL || recommended
|-
! metapost
| latest (A/M) || 1.002 (SVN #202) || 1.002 || 1.002 || 1.00x || 1.002 (SVN #202) || 0.993 || any
|-
! pdfTeX
| latest (A/M) || 1.50.0/#326 (M) || 1.40.5 (M) || 1.50.0/#326 (M) || 1.50.0/#326 (M) || 1.40.7/SVN #371 or 1.50.0 || 1.40.2 || any
|-
! XeTeX
| latest (A/M) || 0.997/#601 (M) || 0.997/#539 (M) || 0.997/#600 (M) || 0.997/#526 (M) || 0.997/SVN #601 || 0.996 || 0.997/SVN #526 (#543) or later
|-
! xdvipdfmx
| latest (A/M) || 0.5/#xetex (M) || 0.5/#102 (M) || 0.5/#xetex (M) || 0.4/#96 (M) || 0.5/SVN #merged with xetex || 0.5 || 0.5/SVN #102
|-
! luatex
| latest (A/M)
|| 0.22.1 (M)
|| 0.22.0 (M)
|| 0.22.1 (M)
|| 0.22.1 (M)
|| 0.22.1
| --
|| 0.22.1/SVN #10xx
|-
|}
A = automatic, M = manualBinaries can now be built from svn co http://svn.contextgarden.net/suite/build-binariesIt might take some time to propagate the changes and auto-update this page :)
=== pdfTeX ===* SVN: svn://scm.foundry.supelec.fr/svn/pdftex* VieCV: http://foundry.supelec.fr/plugins/scmsvn/viewcvsw32tex.php/?root=pdftexorg
=== XeTeX ===* http://scriptswww.siltug.org/texlive/svn-public/xetex/TRUNK
After rsync-ing binaries, one One needs to executeset set CYGWIN=noNTsecbefore syncing binaries or
It might be after that numbers smaller than 777 are OK as well, but I didnelse binaries won't want to riskwork. From rsync bundle one needs to have at least
== building XeTeX and xdvipdfmx ==
(This might need to be moved to some better place, for example under XeTeX, but I needed to leave a note on building process before we all forget it.)
SVN sources are available at: http://scripts.sil.org/svn== Cross-public/xetex/TRUNK http://scripts.sil.org/svn-public/xdvipdfmx/TRUNKcompiling on Mac OS X ==
Prerequisits: You In order to cross-compile for PPC on a Intel Mac, you need to have give the runtime libraries for fontconfig compiler and zlib installed, as well as the devel package for fontconfiglinker the following additional switches:
=== Taco's notes (for linux) === -arch ppc
XeTeX's build process needs the tex binaries directory in the path So all you have to deduce an installation directory from.On the contextgarden, that should be do is set <code>CFLAGS</optcode> and <code>LDFLAGS</texlive2007/bin/i386-linuxcode> before you run <code>configure</code> (as well as <code>CXXFLAGS</code>,because if applicable). Of course it assumes may be that some Makefiles don't honor these variables and override them with something of their own, and this is the path major inconvience you will have to deal with (this is TDS compliant (i.e., it ends with 'actually what the Makefile for lua does; here you would have to set something like <code>MYCFLAGS</bin/code> or <<platform>code>XCFLAGS</code>'in addition).
$ export PATH=/opt/texlive2007/binObviously, you can also use a similar instruction to cross-compile the other way round (build for Intel on a PPC host); it's called <code>-arch i386</i386code>; and if you give both at the same time, it results with a so-linuxcalled ''universal'' binary (the size of which being approximately the sum of the size of both individual binaries). [[User:Arthur|Arthur]] 17:$PATH20, 30 September 2007 (CEST)
=== ArthurFor pdfTeX it's notes (for xdvipdfmx) ===enough to say $ export XETEX=location-of-xetex-TRUNK $ CFLAGS="-I$XETEX/texk -I$XETEX/Work/texk -I$XETEX/libs/freetype2/include -I$XETEX/libs/freetype2arch ppc" \ LDFLAGS="-L$XETEX/Work/texk/kpathsea/.libs arch ppc" CXXFLAGS="-L$XETEX/Work/libs/freetype2arch ppc" ./configurebuild.sh
== CrossXeTeX supports the syntax ./build-xetex "-arch ppc"for cross-compiling for PPC on Intel Mac ==.
I see that Mojca has left homework for me It is also adviced to do over the week-end <code>;-)</code> so here goes:use gcc_selectand select gcc 3.3 to be more backward compatible, as well as setting export MACOSX_DEPLOYMENT_TARGET=10.3
In order to cross-compile for PPC on a Intel Mac, you need to give the compiler and the linker the following additional switches:== Compiling TeX Live binaries ==
Pretty damn simple, isnTo compile ppc and i386 binaries for Tiger on 10.6: export ARCH=i386 export MACOSX_DEPLOYMENT_TARGET=10.4 export MYCFLAGS='t?-arch $ARCH -isysroot /Developer/SDKs/MacOSX10.4u.sdk' export LDFLAGS='-arch $ARCH' export CC=gcc-4.0; export CFLAGS=$MYCFLAGS export OBJC=gcc-4.0; export OBJCFLAGS=$MYCFLAGS export CXX=g++-4.0; export CXXFLAGS=$MYCFLAGS
So all you have to do is set <code>CFLAGS<Or alternatively: export MACOSX_DEPLOYMENT_TARGET=10.4 export MYCFLAGS='-isysroot /code> and <code>LDFLAGS<Developer/code> before you run <code>configure<SDKs/code> (as well as <code>CXXFLAGS</code>, if applicable)MacOSX10.4u. Of course it may be that some Makefiles donsdk't honor these variables and override them with something of their own, and this is the major inconvience you will have to deal with (this is actually what the Makefile for lua does export CC=i686-apple-darwin10-gcc-4.0.1; export CFLAGS=$MYCFLAGS export OBJC=i686-apple-darwin10-gcc-4.0.1; here you would have to set something like <code>export OBJCFLAGS=$MYCFLAGS</code> or <code>XCFLAGS</code> in addition) export CXX=i686-apple-darwin10-g++-4.0.1; export CXXFLAGS=$MYCFLAGS
Obviously, you can also use a similar instruction to cross-compile the other way round (build for Intel on a PPC host); it export MACOSX_DEPLOYMENT_TARGET=10.4 export MYCFLAGS='s called <code>-arch i386<isysroot /Developer/SDKs/code>; and if you give both at the same time, it results with a so-called ''universal'' binary (the size of which being approximately the sum of the size of both individual binaries)MacOSX10.4u. [[User:Arthur|Arthur]] 17:20, 30 September 2007 (CEST) For pdfTeX itsdk's enough to say export CC=powerpc-apple-darwin10-gcc-4.0.1; export CFLAGS="$MYCFLAGS export OBJC=powerpc-apple-darwin10-gcc-arch ppc" LDFLAGS4.0.1; export OBJCFLAGS="$MYCFLAGS export CXX=powerpc-apple-arch ppc" CXXFLAGS="darwin10-g++-arch ppc" 4./build0.sh1; export CXXFLAGS=$MYCFLAGS
ConTeXt Standalone/Implementation (view source)
Revision as of 13:14, 13 December 2014
, 13:14, 13 December 2014fix links to metapost
== Binary sources ==
We take binaries from the following sources:
=== MetaPost ===
* SVN: https://foundry.supelec.fr/svn/metapost* ViewVC: https://foundry.supelec.fr/scm/viewvc.php/?root=metapost* files: http://foundry.supelec.fr/gf/project/metapost/frs/<code>tags/XXX</code> === LuaTeX ===* SVN: https://foundry.supelec.fr/svn/metapostluatex* ViewVC: httphttps://foundry.supelec.fr/plugins/scmsvnscm/viewcvsviewvc.php/?root=metapostluatex* Files: http://foundry.supelec.fr/gf/project/luatex/frs/<code>tags/beta-XXX</code> === W32TeX ===
=== luaTeX TeX Live 2012 ===* SVN: svn://scm.foundry.supelec.fr/svn/luatex* ViewVC: http://foundry.supelec.fr/plugins/scmsvn/viewcvs.php/?root=luatex* Files: http://foundry.supelec.fr/frs/?group_id=10
=== xdvipdfmx Others (not used any more) === We also used to compile pdfTeX and XeTeX, but stopped doing so as there was no need to use a version newer than what's in TeX Live. ==== pdfTeX ====* SVN: http://scriptsfoundry.silsupelec.orgfr/svn-public/xdvipdfmxpdftex* VieVC: http://foundry.supelec.fr/gf/project/pdftex/scmsvn/<code>branches/stable/source</code> ==== XeTeX ====* GIT: git://git.code.sf.net/p/xetex/code* Gitweb: http://xetex.git.sourceforge.net/<code>master</TRUNKcode>
== rsync ==
Rsync on Windows behaves a bit weird. We fetched binaries from
* http://www.itefix.no/cwrsync/
chmod 777 tex/texmf-win/bin/*
chmod.exe
cygiconv-2.dll # for chmod
cygwin1.dll
rsync.exe
to be able to use rsync from the garden properly. I have no idea what happens if cygwin is in PATH, but it is asking for problems.
To compile 64-bit binaries on 10.6 or later: ./Build --disable-xdvipdfmx --disable-xetex --disable-xdv2pdfTo select the latest compiler on Lion: CC=clang OBJC=clang CXX=clang++ ./Build <options>If we want to compile for 10.6 on 10.7 we additionally need: export MACOSX_DEPLOYMENT_TARGET=10.6 # or add -mmacosx-version-min=10.6 to CFLAGS # most of the time optional; usually not needed, but one never knows export MYCFLAGS='-arch ppcisysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.6.sdk' export CC=llvm-gcc-4.2; export CFLAGS=$MYCFLAGS export OBJC=llvm-gcc-4.2; export OBJCFLAGS=$MYCFLAGS export CXX=llvm-g++-4.2; export CXXFLAGS=$MYCFLAGS ./Build <options>
= Non-Polish Fonts =
* \definefontsynonym [RalfSmithFormalScript] [rsfs10]
* \definefontsynonym [MartinVogel] [fmvr8x]
== Building plain formats (to be done) ==
''This text will disapear from page, but until we put some additional files to the distribution, here are some notes for me.''
There are no CMR fonts in the distribution (more or less on purpose), but you can use LM replacement instead.
% pdftex.ini
\pdfoutput=1
\pdfcompresslevel=9
\pdfdecimaldigits=3
\pdfpagewidth=210 true mm
\pdfpageheight=297 true mm
\pdfhorigin=1 true in
\pdfvorigin=1 true in
\pdfpkresolution=600
\input plain
\dump
\endinput
pdftex -ini pdftex.ini
One needs to use:
\pdfmapfile{+lm-rep-cmtext.map}
'''Bold text'''
[[Category:Standalone|Implementation]]
