Re: [Tcllib-devel] BWidget configuration/installation question

[Damon C. <da...@tc...>]

    Agreed.  I think the config / make stuff was always in there to try 
and create some kind of consistency with other packages.  Was there 
every defined a standard method for distributing Tcl-only extensions?  
TEA seems like overkill on something that just needs to be copied somewhere.

D


Joe English wrote:
> Larry Virdern wrote:
>
>   
>> When I fetch the cvs head tar file for bwidget from the activestate ftp
>> site, I understand why I need to run an autoconf to create the
>> configure.  But shouldn't bwidget include the config directory, with the
>> tcl.m4, install-sh, and mkinstalldirs scripts in them, if it requires
>> them to build the configure script and to install the code?
>>     
>
> BWidget ought to not require a 'make install' step at all --
> you should be able to just extract the tarfile in-place
> (anywhere on $::auto_path) and it's ready to go.
>
>
> --Joe English
>
>   jen...@fl...
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
> for problems?  Stop!  Download the new AJAX search engine that makes
> searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
> _______________________________________________
> Tcllib-devel mailing list
> Tcl...@li...
> https://lists.sourceforge.net/lists/listinfo/tcllib-devel
>