Hi Rob,
> I think I may need some more help. > I think I need some more details... > > Finally again, reading generate_one_sample function it seems it can take > > a "deleteiffailed" argument. Set it to False and you should get your > > sample (yes you still have to modify code within jallib.py). > > I thought my test results were good enough to prepare for commit. > After I changed the device files in /jallib/include/device/ and some > board files in /jallib/test/board I ran (from /jallib/tools) > python jallib.py sample -a /jallib/sample > (this is the original jallib.py) > This creates a lot of console output and 88 more sample than were in > /jallib/sample before. When I compile all samples 71 of the new samples > have compile errors. What am I doing wrong? Why are there suddenly so > many more samples and how is it possible that so many of these do not > compile but still appear in /jallib/samples? > Are you sure you're running the original jallib.py (sorry to ask but sometime double-checking...) ? Then, "a lot of console output" is something you should post here, at least for one sample expecting to fail at compilation. Did you try to explicitly generate a sample expecting to faile (with -t option IIRC) ? What's the result ? Ultimately I'd need all jal files involved (or enough I can play with) so I can reproduce here what you have. 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 -~----------~----~----~----~------~----~------~--~---
