On Tue, Sep 30, 2008 at 8:33 PM, Zack Rusin <[EMAIL PROTECTED]> wrote: > On Tuesday 30 September 2008 14:21:10 Stephane Marchesin wrote: >> Hi again, >> >> I've adapted (but didn't push it) gallivm to llvm 2.4 (svn) API >> changes. But then there's an obvious question about what we're doing >> with those API changes ? Do we settle on a given version, or do we >> want to adapt it as the llvm API changes ? > > I think what we want to do is just use 2.4 from now on. There was a couple of > fixes there that are very useful to us. So I say push it. > > From now on until we find some kind of a blocking bug in LLVM 2.4 I suggest we > stick with it so that we don't have keep compiling LLVM from svn and just use > the official packages. And we'll keep on using the official packages until: > - we find a serious bug that really blocks us and we get LLVM guys to fix it > in > svn, > - there will be features in svn that we really need and lack of them would > block as well > Does that sound ok? >
Yeah, sounds like the thing to do except for clang issues as I said in the previous email. clang seems a bit fragile from playing with it a bit. I guess we'll see... Stephane ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Mesa3d-dev mailing list Mesa3d-dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mesa3d-dev
