> > BTW: we talked about samples vs test & board files. Now tests are not > always documented well enough to be a sample, but with a few tests and > board file, one could create a lot of samples.
Yeah, that's the idea ! The most basic way is just to create any possible combination of a > test and boardfile and save the ones that compile. That's the way the testing matrix is filled automatically. for each board file, it tries to compile every tests, and keep those which compile. I thought at first reading you meant to "cut" the board into different pieces, try to assemble some randomly with test files, and keep those which compile ok. Sounds like artificial intelligence :) Need to find the one which contains the most minimum lines of code (minimum minimorum). Sounds fun ! Anyway, I was thinking about a way to structure the board file. In this type of file, you have: * PIC conf (clock,...) * pin definition and other setup for each test If we annotate board files with parsable tags in comments (eg. <conf>...</conf>, <test serial,blink>...</test>), one (me for instance) could produce a script to parse these blocks and generate samples (eg. pic conf + blink conf + blink code = blink sample). I know this can be quite boring to write these tags, but it can worth to do it. Writing a new test file would then only require to... well write the test, then register the test into existing tags and/or create new block in the board file corresponding to the setup needs. In addition to this, you can still combine a whole board file and a test file to compile them, as you're currently doing. I think it can be feasible. At least, it's worth give a try. Looking at the 3 lcd samples from Rob, there's only the pic conf + pins which differ (as expected, you may say). These could be generated using these parsable blocks. > I am new to python and struggling with my program to do auto-indent, > so for me it would be a huge project to remove the unused defines. But > maybe it is feasable for some else??? I guess. Someone. Yes... :) Cheers, Seb --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
