Hi Seb,
Sebastien Lelong wrote:
If you have a look at last jallib-bee failure, some samples are failing to compile, related to last added device files. I think this is due to compiler 2.4n being required for these PICs (got a freaking error "Unsupported core: 5"...)
Ah yes, I forgot about the bee packages. I'll remove the extended midrange (2.4n dependent) samples from TORELEASE.
Or... because weekly build are bleeding edge jallib, we can decide to always put last compiler (William will be happy :)). This means jallib SVN should be updated for each compiler beta/release.
I don't think this is a good idea. Removing the samples from TORELEASE is the best option: all 'released' samples will compile and when we keep the samples in the users of 2.4n-beta can still download these from the trunk.
Regards, Rob. -- Rob Hamerling, Vianen, NL (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]. For more options, visit this group at http://groups.google.com/group/jallib?hl=en.
