Re: GCC multi-version development layout
Jonathan Wakely via Gcc-help <[email protected]> Sun, 19 Apr 2026 18:49:45 +0100
| Newsgroups | gmane.comp.gcc.help |
|---|---|
| Message-ID | <CAH6eHdRuikOvMbMMjVreSrgLryZGmff85_+r4SufVMW2tS-afA@mail.gmail.com> |
On Sun, 19 Apr 2026, 17:57 Xi Ruoyao via Gcc-help, <[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? > The layout doesn't matter at all. Anything will work. I have a directory ~/src/gcc/gcc for the git repo, where I work on trunk and then directories ~/src/gcc/gcc-15 and ~/src/gcc/gcc-14 etc for each release branch, using git worktree. I install each version to ~/gcc/X where X is 16, 15, 14 etc. But it really doesn't matter, anything works. > See https://git-scm.com/docs/git-worktree. > This is definitely the best way to manage the repo, so that every release branch is just a worktree using the same repository metadata and config settings.