Re: make.tcl vs configure/autoconf (was: Re: OpenBSD 3.3 notes)

["David N. Welton" <da...@dedasys.com>]

Nicholas Brawn <nc...@users.sourceforge.net> writes:

> On Fri, 08 Aug 2003 23:24:01 +0200, David N. Welton
> <da...@dedasys.com> wrote:

> > My original reasoning was something like this:

> > *) Configure doesn't run on windows.  Well, it does, but you have
> > to get a bunch of cygwin stuff.

> > *) I hate configure and the auto* tools.  With a passion.  I
> > wanted to try my hand at making something that works better.

> > After having used make.tcl it for a while...

> > *) It doesn't appear to work on windows, because Tcl doesn't
> > include the right information in tclConfig.sh anyway.  Most
> > windows people just want a binary build in any case.

> This could be approached the same way Tcl itself handles it. One
> build subdirectory for Unix, another for Windows.

Those aren't just for builds though - Tcl has different files on each
system, so those directories are very useful to keep the files
seperated out.

> > *) I think we still have a lot of room to maneuver, and would
> > still rather figure out how to make this work for you than install
> > a bunch of clunky conf* stuff.  How does configure pick up the
> > information about libcrypt?

> I think configure would possibly identify the base OS, and from that
> recognise which library name the OS calls OpenSSL.

SSL?  Nope. crypt() is just to be able to do one-way encryption, say,
for passwords.  I guess I didn't catch that in your original email...

I had a look at a few configure scripts, and they just try and do a
compile with -lcrypt.  Does OpenBSD just have crypt() 'built-in',
or...?

> > *) One thing that needs to happen is to keep pressuring the TCT to
> > include information in Tcl about how Tcl was built.  TIP #59 was a
> > start to this (I think that's the right number).

> We could steal what Expect uses in its configure script for
> this. You simply give the configure script the path to your
> tclConfig.sh and I believe it picks up the relevant information.

That's what the current build scripts do, basically.  A shell script
is not the greatest way of comunicating the information though, IMO.

-- 
David N. Welton
   Consulting: http://www.dedasys.com/
     Personal: http://www.dedasys.com/davidw/
Free Software: http://www.dedasys.com/freesoftware/
   Apache Tcl: http://tcl.apache.org/

---------------------------------------------------------------------
To unsubscribe, e-mail: rivet-dev-unsubscribe@tcl.apache.org
For additional commands, e-mail: rivet-dev-help@tcl.apache.org