Qt Creator and other tools

Thank you.

@koahnig said in Include another MinGW compiler into Qt creator: @aha_1980 Thanks for your suggestions. I have decided to compile Qt with the new compiler just to include it to creator. Was quite easy and possibly less of struggle than trying to use CMake. Cool!

MinGW and boost may not be considered as best friends. That is for sure. MinGW 5.3 delivered by Qt seem to have a library, which is linked to boost, causing these issues. Probably more a "fault" of MinGW. However, I do not plan to dig deeper. The plain installation of MinGW through mingw-w64-install.exe, as downloaded from webpage mentioned above, seem to be the pure mingw32 as it is hinting at the end of its installation path. This becomes apparent when following links to https://sourceforge.net/p/mingw-w64/wiki2/Building Boost/ where the compilation of boost is addressed. Therefore, the 7.2.0 MinGW compiler I have installed is also 32 bit. After generating a qmake with this compiler I can easily a homogenous tool chain and it is working with the boost libs. For MinGW it would be appreciated to make more obvious what is used. However, that is a different story.

Ok, I will take a look at that tomorrow. Thanks.

Hi and welcome to devnet, I’d say it’s likely not. I’d recommend bringing this excellent question to the Qt Creator mailing list. You’ll find there Qt Creator’s developers/maintainers. This forum is more user oriented.

Thank you, @SGaist, I followed you advise and community helped to find a solution. The way is simple: Open ssh session to remote host with X forwarding enabled ssh -X user@host. And get know the DISPLAY variable. For example with echo $DISPLAY. It should look like localhost:10.0. Set environment variable DISPLAY in QtCreator -> Projects -> YourConfiguration -> Run -> RunEnvironment to known value from (1). Run and enjoy remote debug with GUI on local machine. Note: closing ssh session will make forwarded display inaccessible and invalid.

@SGaist Thank you for your help. The problem is solved. I just move files from DISTFILES excluding .cpp_ext files to OTHER_FILES and then clear DISTFILES variable. Now the snippet from .pro file looks like this: NEW_COMP_FILES += $$find(DISTFILES, .*\.cpp_ext$) DISTFILES -= $$NEW_COMP_FILES OTHER_FILES += $$find(DISTFILES, .*\.(?!cpp_ext$).*$) DISTFILES =

You can dump the content of a Postgresql/MySQL database into a file if wanted and load that file again on another instance however that still means that you have to have one of these server running somewhere accessible.

@Asperamanca Cool! Thanks for reporting back. Please mark this thread as solved now.

I posted the issue in GitHib. Unfortunately I can't understand the answer. Can someone help? Building a Mer/Sailfish OS project within Qt Creator relies on the definition and use of qtc_* macros inside the .spec file, which is not the case of lipstick library. Opened #122 to let mb2 issue warning when qtc_* macros are not used in the .spec file.

@jsulm thanks man , it is working only with 64 bit application.but it shouldn't be like that.the whole qt application running on 32bit and this little demo use such dll that works only on 64bit! for those who has problem with the cluster example of qt 3d studio:( how to install qtstudio3d plugin) 1-download qt3dstudi module from here: http://download.qt.io/online/qtsdkrepository/windows_x86/desktop/tools_qt3dstudio/qt.tools.qt3dstudio/0.2.1-0-201710111138qt3dstudio.7z 2-then copy all the folders inside the Qt3DStudio folder . 3-past them in <your qt directory>\Qt5.10.0\5.10.0\msvc2015_64 (i tested with msvc2017_64 to and worked) "note that do not replace any file.skip them" 4-then you need to download windows build tools and install it : https://go.microsoft.com/fwlink/?LinkId=691126 5-config application only with 64bit kits and run.

@aha_1980 Thanks! I thought that debug|release was a bitwise or, saying "do this in debug or release modes". I don't understand the syntax at all, but blindly copying the syntax as you wrote works. More information on the syntax can be found here: What does the syntax CONFIG(debug,debug|release) mean? What does the 1st argument specify and similarly what is the 2nd?

Hi and welcome to devnet, Can you do X forwarding through your SSH connection ?

For me $$basename(anything) always returns empty string :( So I use SPEC = $$system(basename $$QMAKESPEC). Sure this will fail on windows.

@webzoid There is a really old thread on this topic. After using Gerolf's/Gisbert approach (see in first post) I have changed to this git driven approach. However, the git approach requires a restart of qmake and certainly an update in git for each new built. Possibly you are looking more into a combination of both. If you are more in having an integrated updating in Qt creator, I believe there is already some request in JIRA on this Feel free to check out the feature request, update and upvote for it. That is the only where you get features included. The forum here is not actively monitored for such cases.

@aha_1980 Thanks, just added my vote to the issue. I think it would be a welcome addition to be honest as I mostly flesh out a class first then take on the implementation - a simple shortcut key or Refactor option would greatly speed things up.

OK, finally solved by PATH1 = $$OUT_PWD PATH2 = $$PWD !equals(PATH1, $$PATH2) {