Qt Creator and other tools

Hi, The correct repository is http://code.qt.io/cgit/qt-creator/qt-creator.git/

Only a subset of QVariant types are supported by the designer plugins. Scroll down here for a list.

Check the Qt Creator instructions for snippets. I just followed the instructions and modified the auto-completed code for Q_PROPERTY so that the getter follows my company's coding style of "get" + Uppercased property name. You can probably create a snippet for what you want.

QDockWidget and QMainWindow are tied. That doesn't prevent you to use another QMainWindow as a central widget for your QMainWindow even though that would be a bit strange. Note that if you only want to work with dock widgets nothing forbids you to not use any central widget.

got answers from creator mailing list. 1. copy/paste resources: Actually if you open the qrc file in an editor in Qt Creator (e.g. “Open in Editor” from context menu in project tree, or through locator (ctrl+k)), and choose Add > Files there, then you are asked if you want to copy the files to the location of the qrc file if the files that you choose are not already located there. 3. copy/paste src code: Qt Creator does not provide “file explorer” functionalities (beside the remove and rename, which are there because they are actually .pro/.pri file editing features). Note that there are e.g. “Show in Explorer/Finder” in the context menu for nodes in the project tree. 4. generated code: That sounds like a sensible approach to me. (Note that you should use $$PWD/..... to refer to files with a relative to the .pri file). now I can go on and prepare my blog

@jsulm Ok..

@auroraqt How does the UI look in the designer on Ubuntu?

@salimoneus We are dynamically linking. Our project also builds on Windows and we do not see this problem on there. So far we've seen this problem on OSX 10.9, 10.10 and 10.11. What doesn't make sense to me is that it shouldn't matter what builds of Qt are being linked against. Somehow Qt 5.5.1 has broken breakpoints in my own code.

Hmmm, maybe try upgrading to Qt 5.5.1.

I think I nailed it. It has to do with auto_moc(on) in cmake as well as the fact I do introduced big ass projects (ITk&VTK&BOOST) on board. Also I tried linux with gnu-makefiles and moc runs fast. So it is also specific to VS. Having one monolithic application (single cmake target) does not help either. I did split the project in a few static libs and it seems better already, though a clean rebuild still takes forever :( So the only solutions I can think of: Disable auto moc and do manual moc in cmake. People have reported some auto_moc problems before. Switch to dev in Linux. Right now it takes equal time to build all my dependencies and the project to just building the project under win :D Note: Not a Qt issue. I posted here cause my initial feeling was it was occurring only in Qt5 (Qt4 is affected too however). So might escalate on cmake mailing lists.

Hi, For Windows, either modify the PATH environment variable for the check part to also point the to the folder where your DLLs are or put the tests destination folder in the same folder as the DLLs

@GinoMan2440 said: However for any other libraries, you have to add the library just to that specific project, instead of for example just being able to reference it by typing... Your libraries (or more correctly headers) are not in system-wide recognized location. Question: How can I make the headers for the library globally available to Qt so that it suggests the headers and suggests the types and symbols of that header in their proper contexts like it does for the STL, OpenGL, and the Windows SDK as well as pass those headers to the compiler so that the compiler knows where they are? You can create a feature for qmake, where you add the paths to the headers and the binaries. You can use my repo where I've susbstituted the compilers as a template. The .prf file you copy in $QTDIR/mkspecs/features and you can use it with the CONFIG variable in your project, like this: CONFIG += my_cool_curl_feature Kind regards.

Hi, for a normal Qt installation, starting your app outside of Qt Creator should not be possible, because there are no path set to Qt dlls, or because you have not yet run windeployqt on your app. So Dependency Walker is just guessing what bit flavor of Qt5 dlls the app needs. To start your app outside of Qt Creator, you can open a CMD window: C:\Qt\5.5\msvc2013_64\bin\qtenv2.bat then cd to your build project and try starting your app from the same CMD window.

what about poppler? the qt5 backend is pretty good.

I've found the response. There is a positionIndependentCode property in the cpp module. So on can remove -fPIC by adding cpp.positionIndependentCode: false. This property is supposed to be undefined by default, but it seems to resolve to true for my toolchain.

@kshegunov Many thanks, i had the eariler version of qtCreator.

I found a solution. In case anyone has the same problem just add the following to you CMakeLists.txt: if(WIN32) set(GUI_TYPE WIN32) elseif(APPLE) set(GUI_TYPE MACOSX_BUNDLE) endif() then add ${GUI_TYPE} to your target. My CMakeLists.txt is now project(Win32App) cmake_minimum_required(VERSION 3.0.2 FATAL_ERROR) if(WIN32) set(GUI_TYPE WIN32) elseif(APPLE) set(GUI_TYPE MACOSX_BUNDLE) endif() set(SRC main.cpp ) set(HDR) set(RES) add_definitions(-DWIN32 -D_WINDOWS -D_UNICODE -DUNICODE) set(CMAKE_EXE_LINKER_FLAGS "${CMAKE_EXE_LINKER_FLAGS} /SUBSYSTEM:WINDOWS,5.01") add_custom_target(${PROJECT_NAME}_HEADERS SOURCES ${HDR}) add_executable(${CMAKE_PROJECT_NAME} ${GUI_TYPE} ${SRC} ${RES})