Thanks for the info.  I'm trying to upgade from Tcl Dev kit 3.2 to TclDev
Kit 5.  So, I'm going through a bit of a learning curve with
teapot/teacup.

To answer your question, yes it would be helpful if you provided this "hint"?

Would it help to understand this if the 'for architecture' label would get
>  a
>  'prefix not set' hint if none is set and only Tcl packages are shown ?

Thanks again.

Al Silverstein

>  Allan Silverstein wrote:
> 
> >> What is the architecture shown at the top, above the edit field ?
> > tcl
> >>
> >> Have you set a basekit yet ?
>   > No
> >>
> >> If not, do that, then try the package selection again. Have the
> >> architecture(s)
> >> shown above the edit field changed ?
> 
> > After setting basekit in "Prefix File", the architectures changed to
> > "tcl or
> > win32-ix86" and the expect Package now shows up.
> 
>  Wonderful ...
> 
>  An explanation ... Basically TclApp shows only packages which work for the
>  current settings, and without a basekit it assumes/knows 'starkit', thus
>  tcl-only. By setting a prefix TclApp then knows that you are generating a
>  'starpack' instead and pulls the platform information from it, then
>  showing the
>  packages for these platforms.
> 
>  Going back to 'starkits', you can also set the architecture explicitly
>  (Basic
>  Tab), even multiple, i.e. you can generate a multi-architecture starkit
>  which
>  can be used on all the given platforms, because TclApp will pull the
>  binaries
>  of a package for all the given platforms.
> 
>  Would it help to understand this if the 'for architecture' label would get
>  a
>  'prefix not set' hint if none is set and only Tcl packages are shown ?
> 
> 
> > However, I am not able to
> > get "Expect to show up if I only specify an "Interpreter" and not a
> > "Prefix
> > File".
> >
> > Can you explain?
> 
>  Prefix is the basekit you wish to use as runtime for your starpack.
> 
>  Interpreter is when you are creating a starkit, i.e. (no prefix). The
>  default
>  interpreter for a starkit is 'tclsh'. Using -interpreter you can switch
>  this to
>     'wish', 'tclkit', etc.
> 
>  Prefix becomes part of the generated application, it is the integrated
>  runtime.
>  Interpreter is the name for the _external_ runtime to execute the
>  generated
>  starkit, which is without an integrated runtime.
> 
> 
> 
>  http://docs.activestate.com/tdk/5.0/TclApp.html#interp
>  ... 2nd to last paragraph ...
> 
>  	If -prefix PATH is specified, that file will be used to run the
>  	application. However, within the Prefix file, it is possible to specify
>  	an interpreter. If the prefix file contains the string
>  	@__interpreter__@ in the first 200 characters of the file, then the
>  	value specified by the -interpreter setting will replace the
>  	@__interpreter__@ string during wrapping.
> 
>  Does this help?
> 
> 
>  --
>  Sincerely,
>       Andreas Kupries <andreas@[...].com>
>       Developer @    <http://www.activestate.com/>
> 

_______________________________________________
TDK mailing list
TDK@[...].com
http://listserv.ActiveState.com/mailman/listinfo/tdk