RE: [avr-gcc-list] Problem with avr gcc compiler ? No warningofmixeddata types

[Weddington, Eric]

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Dan Roganti
> Sent: Sunday, April 19, 2009 1:47 PM
> To: address@hidden
> Subject: Re: [avr-gcc-list] Problem with avr gcc compiler ? 
> No warningofmixeddata types
> 
> 
> 
> Weddington, Eric wrote: 
> 
>        
>       
>         
> 
>               -----Original Message-----
>               From: 
>               
> address@hidden 
>               
>                       That's what libraries are for. Perhaps 
> you should build 
>               your own vt100 library. See the avr-libc manual 
> for more information:
>                       
>               
> <http://www.nongnu.org/avr-libc/user-manual/library.html> 
> <http://www.nongnu.org/avr-libc/user-manual/library.html>  
>               
> <http://www.nongnu.org/avr-libc/user-manual/library.html> 
> <http://www.nongnu.org/avr-libc/user-manual/library.html>  
>               
>               That would be nice to have, but I usually get 
> stuck working 
>               on the next project than upgrading the programming 
>               environment.  Perhaps this could be a good 
> suggestion to add 
>               into the next upgrade for the avr-libc.
>                   
> 
>       
>       What are you suggesting we add to avr-libc?
> 
> 
> Just what you mentioned before, a vt100 library.

No, I didn't suggest that we add it to avr-libc. That is not where a vt100 
library belongs.

I suggested that *you* build a vt100 library. The link to the documentation 
shows you how to build a library on your own. With a properly designed and 
built library, the linker will only link in what is being referenced.