Not really sure what exactly means by "in GIT source". If you're using latest OSL from it's repository then nothing extra required. If you use latest blender git, then you'll need to run install_deps.sh to make sure your OSL is all fine (you'll need to do it once we're finished with preparing libs and making needed changes).
On Wed, Nov 19, 2014 at 4:20 PM, AIBlender <[email protected]> wrote: > On 19/11/14 11:06, Sergey Sharybin wrote: > > Hi, > > > > There was a bug in the OSL library which lead to some heisen-crashes of > > Blender. The patch has been now accepted to the upstream of OSL, so we > > should use it for the next release. > > > > It doesn't seem safe to use current git version of the library and likely > > it wouldn't be released before we go to the freeze. So the idea would be > to > > use Release-1.5.11 tag of the OSL repository and apply the patch on top > of > > it. > > > > Here's the patch itself: > > > https://github.com/imageworks/OpenShadingLanguage/commit/bcaf5778e2d778b72615e5c49269b59671cf0d91 > > > > I'll take care of linux, but i need maintainers' help with OSX and > Windows. > > > > Once the OSX and Windows libs are up i'll do changes needed to be done in > > Blender itself. > > > Hi, > > Does this mean for people like me that has OSL enabled in GIT source > builds that i will need to get Osl Release version 1.5.11 and apply that > patch. Or can I just wait and install_deps will be updated and all will > need to do is rerun it? > > Terry Wallwork > _______________________________________________ > Bf-committers mailing list > [email protected] > http://lists.blender.org/mailman/listinfo/bf-committers > -- With best regards, Sergey Sharybin _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
