Hi Rob, 2010/2/25 Rob Hamerling <[email protected]>: > > These are slightly different figures than here. My numbers might not be accurate, I just did a quick count. It does not change the issue at hand though.
> Back to your numbers: what do you mean by 'regenerate'? If that means > creating samples from board and test files: not all samples are created that > way! Does that explain your 'missing' 123? That is what I mean. It might explain the difference (although I doubt it explains all the difference). But it also raises the question why we don't generate more (all) samples with test/board files. An other issue is the generation proces itself. What I do now is generate all samples in a subdirectory and copy the ones I need (understand and know to be changed) to the sample directory. This is error-prone. The alternative - generate all samples into the sample directory will renew all samples, regardless if they have changed or not (same content, other date). Would it be dificult for buildbot to generate all samples and only copy the ones that changed to the sample directory? > PS: 87 blink samples and related device files are not (yet) released because > not at least one PIC of their group (PICs sharing the same dataseet) was > tested. There are 17 of such groups in my 'missing' list. I would be happy > to show this list to sponsors..... Is 16f688 or 16f690 on this list? I tested the new serial libraries on the first one and will build a testboard for the second one (when I get to it ;). Joep -- 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.
