Hi all;
After the recent confusions about which OpenCollada version should be used
i now have added a file:
blender/source/blender/collada/version.conf
This file contains the sha1 hash key of the OpenCollada Commit that
shall be used
for building Blender with Collada.
After a bit of trial
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks Gaia!
/Nathan
On 1.10.2013 0:30, Gaia wrote:
> Hi all;
>
> After the recent confusions about which OpenCollada version should
> be used i now have added a file:
>
> blender/source/blender/collada/version.conf
>
> This file contains the sha1
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 t
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.
>
> Th
Thanks for the info :)
For now i'm leaving collada unchanged for until next update request in the
ML.
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
Info operator.
On Tue, Oct 1, 2013 at 4:18 PM, Gaia
