Using a TEA package
in [TCL]
|
From: jh on 18 Sep 2009 14:55 On Sep 18, 2:44 pm, "Larry W. Virden" <lvir...(a)gmail.com> wrote: > On Sep 18, 8:42 am, jh <jvh75...(a)gmail.com> wrote: > > > Package has no configure script but does have configure.in. Do I need > > to install and run autoconf. I hope not, its documentation says it > > requires m4 and perl, which will require ..., which will require.... > > Yes, if you can't find a release of the software, with the configure > already generated, then you have to go down the rabbit hole of finding > all the pieces. > Ahh. So that wascally wabbit has my pieces.
From: Jeff Hobbs on 18 Sep 2009 17:59
On Sep 18, 5:42 am, jh <jvh75...(a)gmail.com> wrote: > On Sep 18, 5:06 am, "Larry W. Virden" <lvir...(a)gmail.com> wrote: > > > On Sep 17, 2:26 pm, jh <jvh75...(a)gmail.com> wrote: > > > > I have found some > > > documentation (Welch, et al) on constructing TEA packages but little > > > for dumb newbies on how use one. With the MSys + MinGW build process > > > thrown in I feel like I have two simultaneous equations with 2+ > > > unknowns. > > > The steps are, basically, > > 1. Install MSys and MinGW build commands. > > 2. Read README and INSTALL type files to understand what needs to > > happen > > 3. Run the package's configure command to create a Makefile. > > Package has no configure script but does have configure.in. Do I need > to install and run autoconf. I hope not, its documentation says it > requires m4 and perl, which will require ..., which will require.... > > Also within the package's tclconfig directory there is a file named > install-sh. Is this found and used by "make install"? install-sh isn't actually necessary anymore. Also, the 'configure' _should_ be generated by the developer and be part of the source package. You can use autoconf to generate it (another piece that installs in the extended Msys developer toolset), but it is always recommended that the TEA package developer provide 'configure'. Jeff |