Hi Louai,
Thank you for returning this thread back to the original topic. I think what you propose there is very good idea indeed! Why make JavaScript libraries more complex to handle than any other library? - Pasi On 19/01/15 13:19, "Al-Khanji Louai" <louai.al-kha...@theqtcompany.com> wrote: >The thread seems to have derailed quite badly, so let's reboot it and >return to the original topic of how to bundle the javascript code. > >If I understand correctly, there is a desire to be able to provide the >modified three.js code as a separate package. > >We have an existing solution for this, the configure script. Wouldn't the >whole issue be solved by just adding a compile-time check for the >library? If it's found on the system, fine, use that code. If not, use >the code bundled with Qt. Add a switch to override the selection. Treat >like any other library, because it is. > >-- Louai > >_______________________________________________ >Development mailing list >Development@qt-project.org >http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development