On 8 Oct 2008, at 19:58 , Sebastien LELONG wrote:

>
>> We 'guarantee' that the samples work for the combination of  
>> libraries,
>> the device file and the specific PIC. But I'm sure there will be  
>> users
>> who want to use the samples and libraries for other PICs. When we  
>> don't
>> distribute the other device files they have a problem! If we can we
>> should try to avoid any disappointments, so I'll vote for  
>> distribution
>> of all device files.
>
> IIRC, this is not what we've stated, we may need to discuss this  
> again.
> I *strongly* disagree about releasing all device files. For me, the  
> release
> package is something stable, which we have tested.

Seeing two blink files fail, I have to agree. When we release there  
will be plenty of pointers (in every file!) to the repository.
We owe it to newbies to distribute working, tested code.


> Using the release package
> is a guarantee you know where you are, there's no surprise. To be  
> precise,
> the test result page is here to show, even to measure how confident  
> you can
> be using a given configuration (device file with other libs).
I agree.


> I think at the beginning we have put expection too high about the  
> tests
> (something like: this file should be tested at least on 3 different  
> PIC
> family to be validated, etc...). My take is the device should at  
> least be
> used once. The blink sample is perfect. You may say "but you did  
> not test
> with a lib ?". That's right, and the test result page for this PIC  
> will
> reflect this (poorly tested). And the user know where he is. But at  
> least,
> something has been validated by a human.
>
> Now, I understand you want people to be able to find your device  
> file. jallib
> website is here to help, with the SVN tool via the web interface.  
> We will
> mention it. Another option is to release another package, dedicated  
> to device
> files (so they could integrated so the compiler distrib for  
> instance, I
> dunno). Yet another option would to release a "unstable" release,  
> with all
> device, and libraries (with for instance only libraries which are JSG
> compliant, but which were not tested, again I dunno, we need to  
> decide).
>
> But, at least, there should one stable release, with only tested  
> files. That's
> for me very important (as you guess), because the quality that  
> we'll provide
> with this package will help jallib be the new standard libraries  
> (...).
>
>
>>> cd tools
>>> make compile
>>
>> Sorry, I should have looked better. Unfortunately this doesn't  
>> work in
>> my environment. I don;t know if it is the different make or an
>> incomplete path or something else. I'll see if I can get it to work.
>
> I could include this in the jallib wrapper, but this wrapper needs  
> much more
> work, so this won't be available soon...
>
> Seb
> -- 
> Sébastien LELONG
> http://www.sirloon.net
> http://sirbot.org
>
> >
>
>

---
ir EE van Andel [EMAIL PROTECTED]  http://www.fiwihex.nl
Fiwihex B.V. Wierdensestraat 74, NL7604BK Almelo, Netherlands
tel+31-546-491106 fax+31-546-491107



--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to