[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [avr-libc-dev] Re: AW: [avr-gcc-list] multiple -Tdata options passed
Re: [avr-libc-dev] Re: AW: [avr-gcc-list] multiple -Tdata options passed to the linker forsome AVRs
Wed, 8 Mar 2006 12:33:45 +0100
address@hidden wrote on Mittwoch, 8. März 2006 14:10 :
> ----- Original Message -----
> From: "Haase Bjoern (PT-BEU/EMT) *" <address@hidden>
> Date: Wednesday, March 8, 2006 2:02 am
> Subject: AW: [avr-gcc-list] multiple -Tdata options passed to the linker
> forsome AVRs
> > The code of this "database" program would extract the required data
> > and generate device specific header files that are needed for all of
> > thedifferent projects. I'd suggest to make avr-libc the main host
> > projectof this file so that it could be easily changed.
> > Periodically, one would
> > commit updates of it to the other projects.?
> > My hope is, that this way one would be having only some initial work,
> > but would have less maintenance problems.?
> IMHO, the maintenance problem is not so much generating the patches, but
> as you mentioned above: "Periodically, one would commit updates of it to
> the other projects.".
> Well, committing to avr-libc is not bad at all. But committing to
> Binutils and GCC can be a hassle.
This would not change the present situation a lot. Also right now, it requires
somebody with write privileges for adding support for a new device to