Re: [Development] Distributing 3rd party closed source libs
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 conflicts. Also, I believe there is a provision in the Autodesk FBX library which forbids inclusion in free/open source software. (Anti-blender provision) As a result, I believe Blender and some other applications (UE4) have done their own implementation, perhaps QT could borrow from that? Thanks, Chris Gilbert Knald Technologies, LLC On 10/30/2016 10:11 AM, Thiago Macieira wrote: 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 libraries (and in the case of MySQL, since they change the soname often, it's a difficult proposal). We do not ship compiled plugins for the proprietary databases, like OCI, Interbase and TDS. People who want one of those can download the sources and compile themselves. That's just the plugin, no need to recompile all of Qt. With my OSS hat on, I would say we shouldn't ship even a non-working binary. People who want it should download the source for the module and compile themselves. It is, after all, just a qmake && make. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Distributing 3rd party closed source libs
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 libraries (and in the case of MySQL, since they change the soname often, it's a difficult proposal). We do not ship compiled plugins for the proprietary databases, like OCI, Interbase and TDS. People who want one of those can download the sources and compile themselves. That's just the plugin, no need to recompile all of Qt. With my OSS hat on, I would say we shouldn't ship even a non-working binary. People who want it should download the source for the module and compile themselves. It is, after all, just a qmake && make. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Distributing 3rd party closed source libs
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 packages but require the user to install the fbx SDK? > The database plugins need to be compiled separately iirc, but another option would be to dlopen the autodesk shared library. Cheers Rich. ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Distributing 3rd party closed source libs
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 files. Guillermo and Mauro have been making the QMesh geometry loading component plugin based to help support more formats. One of the formats we'd like to support is FBX. For developers building from git, this is manageable, although not ideal, by downloading the fbx sdk and pointing the build at it. 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 packages but require the user to install the fbx SDK? I guess this is similar to the database driver plugins. Cheers, Sean -- Dr Sean Harmer | sean.har...@kdab.com | Managing Director UK KDAB (UK) Ltd, a KDAB Group company Tel. +44 (0)1625 809908; Sweden (HQ) +46-563-540090 Mobile: +44 (0)7545 140604 KDAB - Qt Experts ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
