Done, as of revision 864. You can be an adventurer and force test generation, whatever the filename, by specifying all parameters (-b, -t, -o).
I've also noticed USB tests were also included in sample generation, where they shouldn't. They aren't anymore since they're not prefixed with "test_" so that's good news. I've also noticed a "usb_board.jal" in "include" map, where it should probably go to "board" map (it includes a device files). Anyway, I guess there are quite a lot of things to get done here, we need to go step by step (starting by having a USB PIC :)). I also wonder if we'll have enough material (lib themselves, samples, doc, ...) to include USB stuff in next release. Albert, can you give your point of view on this ? Cheers, Seb 2009/3/16 Joep Suijs <[email protected]> > > Good! > > I do have a question about sample generation. Does it use each file in > the test directory or files that start with test_ only? > > The reason I ask is that I tend to create more complex test programs. > This is good for testing, not so good as sample. And especially when > there are also other test programs (like for lcd's), it would be an > option to have test-only testfiles, eg with the tst_ prefex. > > Joep > > > > -- Sébastien Lelong http://www.sirloon.net http://sirbot.org --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
