Hi Rob,
> > > Jallib's -help function is pretty brief for a dummy like me > > Well, typically a case of short-sightness: it turns out Jallib.py has > more info than I thought.... > I'm happy you finally found it :) > Because of changes in the device files - ic the fuse_defs - I need to > change board files, generate new samples not overwriting those in the > /sample directory, and compile these with new the device files (another > set than those in the current /include/device). As far as I understand > it this is not possible with the current jallib.py script. So I made a copy of jallib.py, commented out the compiler invocation, in > particular the possible unlink() from the function > generate_one_sample(). In fact I use only the merge facility which > leaves all generated samples in the -o directory. Now I can compile > these with my own compiler options, like specific include directories. > You can play with env variable JALLIB_JALV2 and pass some parameters. Mine looks like: JALLIB_JALV2="/home/sirlon/bin/jalv4l -long-start" (did I already mention I tend to forgot this option ?) Also, setting JALLIB_REPOS to a different location will compile using libraries in this directory. Finally, generating explicit sample by passing board + test files (no auto) will keep your sample merged, even if compilation fails. 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). 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 -~----------~----~----~----~------~----~------~--~---
