On 10/27/15, Jan Stan?k <jstanek at redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi, > with the recent replacement of awk build scripts with tclsh ones, a > problem has risen. The tcl is not commonly available when building the > environment/distribution from ground up (bootstrap), and as a > consequence, SQLite can no longer be built in these early stages. > > Would it be possible to bring back the awk-based build scripts? >
No tclsh dependency has been added as there has always been a tclsh dependency. What we have done is remove the awk dependency by converting all awk scripts into tclsh scripts. Dependencies before the change: C-compiler, make/nmake, awk, tclsh Dependencies after the change: C-compiler, make/nmake, tclsh The driver for this change was Windows users, who now only have to install VC++ and ActiveState TCL in order to compile SQLite from canonical sources, whereas before they also had to locate and install awk.exe. The fact that SQLite is a TCL extension that has "escaped into the wild" is also a consideration. Hmmm... It appears that there used to be a some build targets that only used awk and not tclsh in the older makefiles for unix. So if you were only using the build targets that constructed SQLite from individual source files, and not the amalgamation, you could get by with just awk and without tclsh. I see your point. However, the amalgamation builds are faster (faster in the sense that the resulting libsqlite3.a file uses about 7% fewer CPU cycles). I think it is better for us to try to make life easier for the millions and millions of Windows users than for the handful of people who are bootstrapping Linux. Is it really that difficult to build tclsh first? -- D. Richard Hipp drh at sqlite.org
