Qt Creator and other tools

Qt Modeling should create class diagram for Qt Projects so we don't need to use other programs like power amc to generate c++ code then edit it manualy to adapt it with Qt thank you for your help andreyc :)

[quote author="debugg" date="1392520256"]Wow, fuck!! Those little...!!!!!!!!! I disabled some process called search protect conduit, which is supposedly a malware and now it's working. LOL THOSE LITTLE WORMS!!! Sorry. I was getting seg fault probably because they were getting access to some protected parts of the memory or something.[/quote]Ouch! I hate malware. I'm glad that you've found a solution. All the best with your projects, and feel free to post back if you have any other questions.

good I solve my problem

Well, the answer is, of course, simple-stupid... When I configured the project, I chose "Qt Quick 2.0" (or maybe 2.1), which was the default. Little did I know that there was another option "Qt Quick Controls 1.0". I found selecting that added <code>import QtQuick.Controls 1.0</code> into the QML file. I added that line, and now, lo and behold the controls are visible! Is this documented anywhere? If not, it should be :)

I get a Qmake not executable error

Run "qmake -query". That will dump all the information it has on the Qt it came with, including all kinds of directories containing binaries/headers/examples and whatnot.

Sweet ! I went through the video quickly, looks like it's a very nice introduction to Qt Creator :)

[quote author="tesmai4" date="1390909774"]Download link is not working. where can I download this Add-in for Visual Studio 2012 Professional (I am using QT version 4.8)? Regards, Tariq[/quote] http://qt-project.org/downloads There is currently no version that supports Qt 4.x for Visual Studio 2012.

Yes, I know. So, I set an custom executable in the Project Settings. Then, the executable loads the plugin, and I can debug it. But with a remote linux target, I can't choose a remote custom executable!?

I have already built qml2puppet and I have it in /usr/local/Qt-5.2.2/qml2puppet. The problem here is - why does Qt Creator search for qml2puppet in /bin/ directory instead of /usr/local/Qt-5.2.2/bin/ directory. [quote author="EricRFMA" date="1391902793"]I just went through the same thing with no issues. I think the only difference is that I don't have QT_DIR set. In the qml2puppet directory I did : @/Volumes/Projects/Qt5.2.1/bin/qmake make -r@ Then, the qml2puppet executable appears in <code> /Volumes/Projects/Qt5.2.1/bin/qml2puppet.app/Contents/MacOS</code> as advertised. Is your <code>qmake</code> in <code>/usr/local/Qt-5.2.2/bin</code>? The bin directory where the <code>qmake</code> resides seems to be pivotal in deciding where the build results land. In this case it seems that <code>qml2puppet.app</code> lands in the same directory where the <code>qmake</code> binary resides. Hope this helps...[/quote]

Hi, Qt Creator's GUI needs improvement for the management of kits/Qt-versions/debuggers. In the meantime, you can rename/remove the debugger entry by editing @C:\Users[Username]\AppData\Local\Roaming\QtProject\qtcreator\debuggers.xml@ [quote author="ArbolOne" date="1391922129"]I would like to know if there is a way to use the Qt library, but without the "Creator"[/quote]You can integrate Qt into Visual Studio (Professional version and higher) using the VS Add-In. You can even build your projects from the command line if you want.

The .pro files use the "qmake syntax.":http://qt-project.org/doc/qt-5/qmake-manual.html In general you should use Qt creator to add files (e.g. Add Existing Files). The build is often done in a build directory which is separate.

As side note: The debugger settings need to point to a gdb, not gdbserver.

There seems to be a QT += network missing somewhere, possibly in tizen.pro.

Please report that at bugreports.qt-project.org.

You could try asking on the mailing list, i.e. http://lists.qt-project.org/mailman/listinfo/qbs . The forums are usually not monitored by developers.

You're welcome ! Surprising indeed. You also need to ensure that you are all using the same Qt version

You have to specify a 'Kit' to get it working. In my case no kit was specified but developing was possible nevertheless. A message would be nice at this place to inform the user about the problem because the buttons at the bottom of the dialog had no effect. There was no hint.

self answer: When a linux app loads it need to be able to access all the libXXX.so it needs. "ld" will look for them in any directory declared in the "LD_LIBRARY_PATH" variable However Qt seems to load its plugins dynamically from some paths which can be found there: @QCoreApplication app(argc,argv); qDebug() << app.libraryPaths();@ which printed @("/my/App/Path","/Qt/Dir/Path" )@ And from one of this path it should load the plugins. So if in qtDir you have @/Qt/Dir/Path/plugins/sqldrivers/libqsqltds.so@ You want to make sure to deploy something like: @/my/App/Path/sqldrivers/libqsqltds.so@ this worked fine because the app path is always in "app.libraryPaths()". However, where things get complicated it that libqsqltds.so requires "libsybdb.so.5" to work properly. Which I knew so there also was a @/my/App/Path/sqldrivers/libsybdb.so.5 @ which was wrong because Qt loads dynamically libqsqltds.so but not its dependency, which it seems ld expects to find the usual way ( e.g. in the LD_LIBRARY_PATH ) The fact is that in my dev/integration environments I had libsybdb.so.5 in my path, but not in my production environment. So whatever Qt plugins you need make sure to copy the plugin directory ( with only the .so inside ) to your production environment. And Also make sure that performing: @ldd /my/App/Path/sqldrivers/libsybdb.so.5@ will not print any "not found" as these dependency will not appear with: @ldd /my/App/Path/myAppBin@