standard builds use the version I decide to install for buildbot. It can be anything, it's not related to embedded compiler. This is "by design", so I can switch to whatever compiler I want (if we need to test a beta for a while, go back to an older one, ...) without dealing with SVN "compiler" map.
bee builds use embedded compiler, and that's "by design", too ! If you check a bee package (by compiling samples) with different from the one you'll provide, how can you be confident about what you're releasing ? If it workds with a recent compiler, but doesn't work with an older one which is in the package, result is a bee package unusable... Bee package policy is "what is released has been tested with what's been released", a full self-tested package. So... I understand you want to use 2.4m compiler version. I'll install this for standard builds. If you want bee to use this last compiler, you have to update SVN "compiler" directory. Cheers, Seb > > Hi Seb, Wayne, > > Sebastien Lelong wrote: > > > Bee builds aren't discontinued, but have failed this WE due to errors in > > TORELEASE file. Compiler version doesn't change between standard and bee > > builds. > > The bee packages contain the latest Jallib developments, which could be > seen as 'beta' for the next release. Wouldn't it be better to test the > bee package with the next (beta) compiler version too? This will avoid > last moment surprises. The bee package itself can still contain the > latest official compiler version. > > Regards, Rob. > > -- > Rob Hamerling, Vianen, NL (http://www.robh.nl/) > > > > -- 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 -~----------~----~----~----~------~----~------~--~---
