On Sun, Dec 19, 2010 at 8:58 PM, David Brownell <davi...@pacbell.net> wrote: > Example: against a fresh clone of mainline. > > I think it ought to support "configure"next ... but instead it seems to > require more, and > thus is needlessly error prone... Folk won't often be > reading script output except to see and fix well-flagged errors, so > the need for two submodule commands is easily missed. (and > is also rather unusual ... folk wouldn't expect it. > > $ sh bootstrap > + aclocal > + libtoolize --automake --copy > + autoconf > + autoheader > + automake --gnu --add-missing --copy > configure.in:20: installing `./compile' > configure.in:28: installing `./config.guess' > configure.in:28: installing `./config.sub' > configure.in:8: installing `./install-sh' > configure.in:8: installing `./missing' > doc/Makefile.am:1: installing `doc/mdate-sh' > doc/Makefile.am:1: installing `doc/texinfo.tex' > src/Makefile.am: installing `./depcomp' > Makefile.am: installing `./INSTALL' > Bootstrap complete. Quick start build instructions: > > 1. Fetch Jim Tcl > > > Is "Fetch" a command, seems not; but the next > few things are .... it's not clear till after one > tries something and sees it fail (or work). > > (And as I said > above -- this hardly feels bootstrapped, if I've > got to do more than configure the result. Why does > it skip installing only Jim, and not the > rest of the stuff listed above ???? > > git submodule init > git submodule update
I'm thinking that bootstrap could be split in two: - a script that does what it does today and that can be invoked directly. - bootstrap would call this new script + "git submodule init/update" as this is what most, but not everybody, wants. -- Øyvind Harboe Can Zylin Consulting help on your project? US toll free 1-866-980-3434 / International +47 51 63 25 00 http://www.zylin.com/zy1000.html ARM7 ARM9 ARM11 XScale Cortex JTAG debugger and flash programmer _______________________________________________ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
