This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: How about breaking out the big system case construct from configure.in?


Hans-Peter Nilsson wrote:
> 
> Into (say) config.gcc a' la bfd/config.bfd et al.  I'm thinking
> of everything inside the "for machine in $build $host $target; do".
> 
> No more regenerating configure "every time a new target is added". ;-)
> No more changequote errors.  It doesn't need autoconf constructs.

Also a big bonus for submitted patches, no massive line-number-change
diff to filter out.

Anyway, I did this for GDB several years ago, splitting out both a
configure.host and configure.tgt (since GDB has separate case
statements for host and target configure decisions), and it's been
very convenient.  I always wondered if GCC had some subtle reason
for not doing a similar split...

Stan

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]