[TCLCORE] Re: An article about the Cygnus tree

[Jim I. <ji...@ap...>]

Jeff,

On Tuesday, September 5, 2000, at 10:23 AM, Jeffrey Hobbs wrote:

> This is an interesting thread that came through Slashdot about the way 
> that the Cygnus CVS tree works.  What started off as another CVS repo 
> for Cygnus has become the dependent build tree for gcc.  This is an 
> interesting read because as we focus on how we would build a Tcl SDK, 
> we want to make sure to avoid the politics and pitfalls that hit the 
> Cygnus gcc guys.  One basic thing being that Tcl should always be able 
> to work independent of the Tcl SDK (and its build framework). 
>  

The main point of an article that Michael Sokolov sent out (ftp://ivan.Harhan.ORG/pub/embedded/cygnus-tree-intro) on as a part of this thread was that the lack of a coherent unified tree was a real pain in the neck for most GNU tools developers.  So while I agree with your last statement, this quite nice article from the discussion you are citing has kind of the opposite thrust (which I ALSO agree with :-) namely that we should work to provide a coherent toplevel configure/make  for Tcl/Tk/Itcl/BLT/TclX/... that works like the Cygnus tree does for the Gnu tools.  This makes the whole suite SO much easier to manage, and avoids duplication of work in the least interesting & most tedious parts of any software project, the build & install machinery...  It can also (through the use of a unified configure cache) make the configure part of the whole tree MUCH faster.  Then if we are clever about writing a good modules file, extracting bits of the tree, and for instance making sure th!
at things don't get too tightly bound, will be easy as well.

Jim
--
Jim Ingham                                   ji...@ap...
Developer Tools - gdb
Apple Computer

--
The TclCore mailing list is sponsored by Ajuba Solutions
To unsubscribe:  email tcl...@aj... with the 
                 word UNSUBSCRIBE as the subject.