Subject: Re: binary sets and USE_NEW_TOOLCHAIN
To: None <firstname.lastname@example.org>
From: James Chacon <email@example.com>
Date: 10/17/2001 12:34:57
>On Wed, Oct 17, 2001 at 03:20:50AM -0400, James Chacon wrote:
> > 1. Move all new toolchain bits into <set>/tc.mi
> > 2. Move all deleted toolchain bits into <set>/tc.old
> > 3. Change makeflists to check for USE_NEW_TOOLCHAIN being on and pull in
> > either the mi file (for the on case) and tc.old for all other platforms.
> > The main advantage here is that it's easy to see in one place which bits got
> > added/deleted between the 2 toolchain areas (and I caught a few minor missed
> > files this way). Once the toolchain is completely cutover the tc.old files
> > can be converted into the obsolete files and the tc.mi files can go back into
> > their respective mi files.
> > Thoughts?
>Sounds fine. (Though, don't see why "tc.mi" can't just remain -- might
>make future toolchain updates easier to deal with.)
I didn't pull all the toolchain bits out of mi right now. Mainly due to not
wanting to maintain the bits in 2 places (both the old/new tc.* files). Once
the old toolchain is dead moving everything into tc.mi makes sense.