Hi Nuno, > This is the .pro > [...] > LIBS += > /Users/nsantos/Qt/5.4/clang_32_static/qml/QtQuick.2/libqtquick2plugin.a > LIBS += > /Users/nsantos/Qt/5.4/clang_32_static/qml/QtQuick/Window.2/libwindowplugin.a > LIBS += > /Users/nsantos/Qt/5.4/clang_32_static/qml/QtQuick/Controls/libqtquickcontrolsplugin.a > }
You probably have to add the following somewhere: LIBS += /path/to/libqmldbg_tcp.a Then you should be able to to link the final library or application also with QML debugging enabled. Mind that this way your application has the QML debug server built in and whenever you start it with the right arguments or call QQmlDebuggingEnabler::startTcpServer() it will open a debug port and accept connections from anywhere. With a dynamically linked Qt you have the option to delete the plugin in order to prevent this. regards, -- Ulf Hermann, Software Engineer | The Qt Company The Qt Company GmbH, Rudower Chaussee 13, D-12489 Berlin Geschäftsführer: Mika Pälsi, Juha Varelius, Tuula Haataja Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B Email: ulf.herm...@theqtcompany.com | Mobile: + 49 151 68964561 | Phone: +49 30 63 92 3255 www.qt.io |Qt Blog: http://blog.qt.digia.com/ | Twitter: @QtbyDigia, @Qtproject | Facebook: www.facebook.com/qt _______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
