Re: GCC multi-version development layout

Heime via Gcc-help <[email protected]> Sun, 19 Apr 2026 17:14:12 +0000
Newsgroups gmane.comp.gcc.help
Message-ID <5W5RFIyk7lbnPvY9iumZ_j2-qoYdnAwFDbePC3j2BeiYBMEN2tjfVXeawOCBAIlMuxWRWFZOhkB9p-7YhaTFhj9yfB_7mdAAkE-1Dbs__b0=@protonmail.com>
On Sunday, April 19th, 2026 at 6:42 PM, Basile STARYNKEVITCH <[email protected]> wrote:

> On Sun, 2026-04-19 at 16:33 +0000, Heime via Gcc-help wrote:
> > ----------------------------------------------------------------
> >
> > When building GCC from a cloned Git source tree using separate
> > directories (as recommended), the directory structure follows
> > a clean separation of source, build artifacts, and final
> > installation.
> >
> > With different version of gcc, how would be the typical layout
> > for specific branches to make patch changes to different gcc
> > versions with multiple builds and install?
> >
> > What are good books to read about version control useful for
> > work on gcc branches.
> 
> 
> I would suggest reading some good books on git

What would be a good book with many diagrams and examples?  
And for reference?
 
> I actually recommend having several source trees and build trees. and
> proposing your patches (by email to
> https://gcc.gnu.org/mailman/listinfo/gcc-patches ...) at least daily.
> Small incremental patches have better chances to be read and reviewed.
> 
> Thanks
> --
> 
> Basile STARYNKEVITCH
> <[email protected]>
> 8 rue de la Faïencerie
> http://starynkevitch.net/Basile/
> 92340 Bourg-la-Reine
> https://github.com/bstarynk
> France
> https://github.com/RefPerSys/RefPerSys
>                   https://orcid.org/0000-0003-0908-5250
>