avr-libc-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc


From: Weddington, Eric
Subject: RE: [avr-libc-dev] Adding (some) Procyon AVRlibfunctionalitytoavr-libc
Date: Fri, 18 Sep 2009 13:40:22 -0600

 

> -----Original Message-----
> From: 
> address@hidden 
> [mailto:address@hidden
> org] On Behalf Of Joerg Wunsch
> Sent: Friday, September 18, 2009 1:28 PM
> To: address@hidden
> Subject: Re: [avr-libc-dev] Adding (some) Procyon 
> AVRlibfunctionalitytoavr-libc
> 
> As Weddington, Eric wrote:
> 
> > Regarding naming, here's another thought: Why does it even have to
> > have a separate name? If it's part of avr-libc, then let it be that:
> > just a part of avr-libc. The library that is built could be named
> > 'libavr.a' and one links to it with '-lavr', but it's still
> > avr-libc.
> 
> I think it makes sense to have a separate project name just for
> "marketing reasons".  It is really added functionality which goes
> beyond the current avr-libc scope, and I think it should be an
> "opt-in" item rather than always be there.

I was wanting to include it into avr-libc for other marketing reasons. ;-)

If it ships as an object code library, then people can always opt-in or opt-out 
just by linking to the library, or not. Really, I don't see that if such a 
library does exist, then how a user would NOT want to have it at least already 
available.

Including it as part of avr-libc would lend a certain amount of weight to the 
project, which would also assist in adoption of the project.

 
> Also, keeping it distinct allows for other development models.  One
> thing that already has been mentioned is that it might ship as just
> source code modules, rather than an object library.  It might also
> feature a different organization of the documentation.


.... I think at this point, it doesn't matter too much to me whether it's 
included in avr-libc or not, or whether it has it's own project.

Certainly, a hosting location needs to be picked. If Savannah is too difficult, 
it's certainly easy to get a project started on SourceForge, and of course it's 
a popular hosting site. I suppose Google would be ok, though it's not as well 
known. In looking at Frederic's project, I don't see a mailing list capability 
on Google and I think that would be essential. I would volunteer to setup a 
project on SourceForge.

Eric Weddington




reply via email to

[Prev in Thread] Current Thread [Next in Thread]