TIP 203: Create tclConfig.sh-Equivalent in Tcl

EuroTcl/OpenACS 11 - 12 JULY 2024, VIENNA
Author:         Colin McCormack <[email protected]>
Author:         Don Porter <[email protected]>
Author:         Colin McCormack <[email protected]>
State:          Withdrawn
Type:           Project
Vote:           Pending
Created:        17-Jun-2004
Discussions-To: http://mini.net/tcl/tclConfig.sh
Keywords:       configuration,installation
Tcl-Version:    8.5


This proposal requires the registration of information about the built process, currently stored in tclConfig.sh, by means of the Tcl_RegisterConfig mechanism set out in [Tip 59].


Packages such as Critclhttp://www.equi4.com/critcl.html , and indeed anything written in pure tcl which tries to build extensions under Tcl need more introspection to discover the ground rules of construction in the installation in which they find themselves.

In order to facilitate such future build tools, the build information should be made available to Tcl scripts.


Every variable defined in the unix tclConfig.sh should be registered using Tcl_RegisterConfig, with the following exceptions:

Because Windows and other platforms don't have a tclConfig.sh, the following fields are desirable for hand construction:


Stub Support:


How about converting this proposal into a proposal listing the values found in tclConfig.sh and proposing that Tcl should pass those values into Tcl_RegisterConfig during initialization? That would make all the values available to scripts via the ::tcl::pkgconfig command. -- Good idea. Done.

Several of the assigned values in tclConfig.sh contain references to other variables - should these be reproduced verbatim, or evaluated prior to registration? I'm leaning toward verbatim storage: let the people who need the data construct an evaluation which serves their purposes because (a) the form is easy enough to evaluate, as in the parser I threw together http://mini.net/tcl/tclConfig.sh , (b) there might be information in the verbatim form which needs to be preserved. Comments welcome.


Joe English points out that those parts potentially useful to a pure-tcl builder are not necessarily applicable, since the build and installation machines may/will differ substantially, and that those parts universally applicable are available via some combination of info and ::tcl::pkgconfig. Given this insight, I withdraw this TIP.


This document has been placed in the public domain.