Hi guys, hi Rob,

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"...)

The problem is 2.4n is still beta, thus can't be added in weekly bee
packages (that is, not in "compiler" directory), as we release only stable
compiler. These samples (and device files) should be removed from TORELEASE.

Or, if all device files aren't compatible anymore with 2.4m, we need to
update "compiler" in jallib anyway... but that doesn't honor previous rule.

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.


Cheers,
Seb
-- 
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.

Reply via email to