Re: [Development] Distributing 3rd party closed source libs

2016-10-30 Thread Chris Gilbert
Greetings, We use both QT5 and the Autodesk FBX loader in our application - and we would strongly prefer Qt to NOT link it in. There is a need quite often for us to update the Autodesk FBX SDK asymmetrically to QT, and it would be preferable QT doesn't use it in order to avoid potential conf

Re: [Development] Distributing 3rd party closed source libs

2016-10-30 Thread Thiago Macieira
On domingo, 30 de outubro de 2016 09:03:59 PDT Sean Harmer wrote: > I guess this is similar to the database driver plugins. Right. We ship the compiled plugins for both MySQL and PostgreSQL, but not their libraries, so the plugins can't be loaded unless the user installs the required client lib

Re: [Development] Distributing 3rd party closed source libs

2016-10-30 Thread Richard Moore
On 30 October 2016 at 09:03, Sean Harmer wrote: > What can we do in terms of pre-compiled release builds of Qt? Is it > feasible for us to distribute the runtime lib required by the plugin from > the fbx SDK? Or do we need to find some other solution such as build the > plugin for the release pac

[Development] Distributing 3rd party closed source libs

2016-10-30 Thread Sean Harmer
Hi, a very common request is for Qt 3D to support the Autodesk FBX file format which is a pretty standard format for exchanging 3D meshes, and animations. Unfortunately the format is undocumented and proprietary but Autodesk does provide a free (as in beer) SDK that can be used to parse FBX f