texlive[56229] Build/source/doc: (Build one engine): update doc
commits+karl at tug.org
commits+karl at tug.org
Tue Sep 1 00:05:09 CEST 2020
Revision: 56229
http://tug.org/svn/texlive?view=revision&revision=56229
Author: karl
Date: 2020-09-01 00:05:09 +0200 (Tue, 01 Sep 2020)
Log Message:
-----------
(Build one engine): update doc
Modified Paths:
--------------
trunk/Build/source/doc/ChangeLog
trunk/Build/source/doc/build-tools.txt
trunk/Build/source/doc/tlbuild.info
trunk/Build/source/doc/tlbuild.texi
Modified: trunk/Build/source/doc/ChangeLog
===================================================================
--- trunk/Build/source/doc/ChangeLog 2020-08-31 22:01:34 UTC (rev 56228)
+++ trunk/Build/source/doc/ChangeLog 2020-08-31 22:05:09 UTC (rev 56229)
@@ -1,3 +1,8 @@
+2020-08-31 Karl Berry <karl at freefriends.org>
+
+ * tlbuild.texi (Build one engine): rewrite procedure.
+ * build-tools.txt: bison 3.7.1.
+
2020-05-14 Karl Berry <karl at freefriends.org>
* tlbuild.texi: remove poppler references.
Modified: trunk/Build/source/doc/build-tools.txt
===================================================================
--- trunk/Build/source/doc/build-tools.txt 2020-08-31 22:01:34 UTC (rev 56228)
+++ trunk/Build/source/doc/build-tools.txt 2020-08-31 22:05:09 UTC (rev 56229)
@@ -1,6 +1,6 @@
autoconf (GNU Autoconf) 2.69
automake (GNU automake) 1.16.2
-bison (GNU Bison) 3.6.1
+bison (GNU Bison) 3.7.1
flex 2.6.0
ltmain.sh (GNU libtool) 2.4.6
m4 (GNU M4) 1.4.18
Modified: trunk/Build/source/doc/tlbuild.info
===================================================================
(Binary files differ)
Modified: trunk/Build/source/doc/tlbuild.texi
===================================================================
--- trunk/Build/source/doc/tlbuild.texi 2020-08-31 22:01:34 UTC (rev 56228)
+++ trunk/Build/source/doc/tlbuild.texi 2020-08-31 22:05:09 UTC (rev 56229)
@@ -441,7 +441,7 @@
Here is an example from start to finish for working on
@code{dvipdfm-x}. (Unfortunately, this does not suffice for building
-one, or a subset, of the @TeX{} engines; see the next section.)
+the @TeX{} engines; see the next section.)
@example
mkdir mydir && cd mydir # new working directory
@@ -537,23 +537,34 @@
(or other Web2c programs).
The simplest way to do this is to disable everything and then
-explicitly specify what to make. For example, to build only Lua at TeX{}:
+explicitly specify what to make. For example, to build only the
+original @TeX{}:
@example
-./configure --disable-all-pkgs # or ./Build
-cd Work/texk/web2c # build directory
-make luatex # specify target
+cd Work # top build directory
+../configure --without-x --disable-shared --disable-all-pkgs \
+ --enable-tex --disable-synctex -C CFLAGS=-g CXXFLAGS=-g
+make
+cd texk/web2c # cd engine build directory
+make tex # must specify target
@end example
-This works because the @code{make} automatically runs @code{configure}
-as necessary for the dependencies and target. Furthermore, the source
-tree can be cut down to just what is needed for the given engine
-(the separate pdf at TeX{} and Lua at TeX{} source repositories do this, if
-you want to peruse examples).
+The first @code{make} run will configure everything, and even build
+the libraries, even though the packages are disabled.
+The source tree can be cut down to just what is needed for the given
+engine (the separate pdf at TeX{} and Lua at TeX{} source repositories do
+this, for example), but see caveats in previous section.
-We hope to improve the situation in the future. Patches are welcome.
+If you want to debug an X-related program or shared library setup, or
+other variants, change the @code{configure} options
+accordingly. Either @code{../Build} or @code{../configure} can be run.
+Then it is necessary to again specify the target engine (@code{tex},
+in the above) in the @code{make}.
+All this is somewhat unfortunate. We hope to improve the situation in
+the future. Patches are welcome.
+
@node Cross compilation
@section Cross compilation
@@ -702,6 +713,7 @@
Building @code{xindy} requires running the host system @code{clisp}
binary, thus cross compilation is painful, but possible.
+
@node Installing
@chapter Installing
More information about the tex-live-commits
mailing list.