Hi Rob, It's also used to build "jallib" standard packages (eg. jallib-0.6.0.tar.gz, tested device files and samples). One could ask why not putting pdf doc in this package. I would answer "yes why not, but anyway current building process isn't clean and should be reworked, with, in the end, as many TORELEASE files as package types". This way you know what's in packages and extract some filtering logic from build Makefile (search for TORELEASE and grep...).
I've also discovered a packaging bug in "all_devices" package. There's an alien sample: 18f4585_canopen_blink.jal. Wrong regex while picking blink samples... Also see error in building log, I didn't mention them. Cheers, Seb 2010/9/7 Rob Hamerling <[email protected]> > > Seb, > > I saw you added the starters guides to TORELEASE with a comment 'only in > jallib-pack'. What does that mean? I thought TORELEASE as a whole is meant > to specify what goes into the Jallib pack, or is TORELEASE used for > something else as well? > > Regards, Rob. > > -- > R. Hamerling, Netherlands --- http://www.robh.nl > > -- > 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]<jallib%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/jallib?hl=en. > > -- 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.
