[Bf-committers] Collada library version now available in separate file
sergey.vfx at gmail.com
Tue Oct 1 13:21:18 CEST 2013
Thanks for the info :)
For now i'm leaving collada unchanged for until next update request in the
Makes me wondering tho, is there some API call in collada to get it's
version? If so, IMO it'll make sense to add this info to Help -> System
On Tue, Oct 1, 2013 at 4:18 PM, Gaia <gaia.clary at machinimatrix.org> wrote:
> Hi, Sergey
> On 01.10.2013 11:05, Sergey Sharybin wrote:
> > Hi,
> > >From what i could see, there's no actually a call to update collada
> > to 463ba8a2ef5a021ce21df614dde29e0ee800e10b for release builder
> > environments and the latest call was done
> > for 18da7f4109a8eafaa290a33f5550501cc4c8bae8.
> > This is not gonna to be a good practice to silently update hash in the
> > file without call for platform maintainers to update release environment.
> Yes, i have to apologize. You are right, from now on we will always send an
> update request to the bf-mailing list when a new build becomes necessary.
> > And now, shall collada be updated from
> > 18da7f4109a8eafaa290a33f5550501cc4c8bae8 to
> > 463ba8a2ef5a021ce21df614dde29e0ee800e10b?
> Actually it does not matter at the moment, because the changes between
> the 2 versions are not affecting the libraries themself (OpenCollada just
> fixed some build issues). So actually you can use either version for
> building the libs.
> Bf-committers mailing list
> Bf-committers at blender.org
With best regards, Sergey Sharybin
More information about the Bf-committers