1,018
edits
Changes
Jump to navigation
Jump to search
m
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
ConTeXt Standalone/Implementation (view source)
Revision as of 15:02, 9 March 2008
, 15:02, 9 March 2008→Current state of binaries in minimals: ppc binaries update
|-
! XeTeX
| latest (A/M) || 0.997/#601 (M) || 0.997/#603 (M) || 0.997/#600 (M) || 0.997/#526 604 (M) || 0.997/SVN #603 604 || 0.996 || 0.997/SVN #526 (#543) or later|-! xdvipdfmx| latest (A/M) || 0.5/#xetex (M) || 0.5/#xetex (M) || 0.5/#xetex (M) || 0.4/#96 (M) || 0.5/SVN #merged with xetex || 0.4 || 0.5/SVN #102600
|-
! luatex
=== xdvipdfmx ===
(not used any more - sources are included in xetex now)
* http://scripts.sil.org/svn-public/xdvipdfmx/TRUNK
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.
== building XeTeX and xdvipdfmx ==
For pdfTeX it's enough to say
CFLAGS="-arch ppc" LDFLAGS="-arch ppc" CXXFLAGS="-arch ppc" ./build.sh
XeTeX supports the syntax
./build-xetex "-arch ppc"
for cross-compiling.
It is also adviced to use
gcc_select
and select gcc 3.3 to be more backward compatible.
= Non-Polish Fonts =
