This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: Can we remove bison output from cvs?
- To: "'egcs at cygnus dot com'" <egcs at cygnus dot com>
- Subject: RE: Can we remove bison output from cvs?
- From: Jan Reimers <janr at molienergy dot bc dot ca>
- Date: Thu, 14 Jan 1999 15:46:56 -0800
> ----------
> From: Joern Rennecke[SMTP:amylaar@cygnus.co.uk]
> Sent: Thursday, January 14, 1999 2:34 PM
> To: ddsinc09@ix.netcom.com
> Cc: pfeifer@dbai.tuwien.ac.at; egcs@cygnus.com; bothner@cygnus.com;
> ghazi@caip.rutgers.edu
> Subject: Re: Can we remove bison output from cvs?
>
> > Can the repository be split? I.e. the main repository contains the
> > hand crafted text files and a secondary repository contains derived
> text
> > for people without the "proper" tools. Releases would, of course,
> > have to contain a merge of the trees. For anyone to build without
> > all the development tools, they would have to cvs-get both trees and
> > do a symlink merge a la "mkmerge" or a fairly straight forward
> script.
>
> can handle multiple modules which may overlap in directory trees. So
> if things are handled that way, you'd just check out a different
> module
> to get the generated files alongside with the source.
> The main cost is checking in the generated files whenever the source
> files
> are changed.
> Although it should be possible to do this automatically on the server
> side, but that'll need someone to tinker with the configuration to get
> it running.
Could this be extended to make chill/java/objc/testsuites optional for
CVS checkout?
JR