[NickD2039]

I’m not attempting to fix any build issues at this stage, I just need to know _how_ to import a qmake based existing project to VisualGDB.

Is it possible?

When I go through the wizard and select Import project/Import a project built with other tools I only get the option to specify a directory with source files. My project structure is not a simplistic as that. The .pro files switch in features depending on the variant and subdirectories (.pri files) are selectively included based on the configuration of whichever variant is being built. The .pro files also set multitudes of DEFINES based on the configuration.

I’m going to assume that VisualGDB is not designed to support existing qmake based projects and give up on it.

 

• This reply was modified 4 years, 5 months ago by NickD2039.

[NickD2039]

I haven’t attempted it yet as I hit a roadblock with VisualGDB and am in the process of setting up a QtCreator-based cross-compile environment. Not sure how to drive that version of qmake manually as it’s all behind the scenes with VisualGDB (e.g. what makespec do I pick? where are the makespecs??)

EDIT: In fact, when I attempt it, it fails because it’s looking for things below /home/nick/ instead of \Users\Nick\ so VisualGDB must do some secret stuff behind the scenes to drive that version of qmake.

But my question was not related to that; I just wanted to know if there was a way to generate the VisualGDB vcxproj from my existing .pro files (all project maintenance is performed on the pro files, I never use the VisualStudio UI to add/remove source/header files etc.). If that’s not possible (which I strongly suspect is the case) then undortunately I’ll have to give up on VisualGDB which is a shame because it is otherwise super slick.

Thanks,

Nick

• This reply was modified 4 years, 5 months ago by NickD2039.

[NickD2039]

The problem is that the version of qmake that VisualGDB downloads is very old (Qt 5.4.x) which is why it doesn’t work. A later version of qmake (say 5.11.3) would definitely work with that toolchain. Where does VisualGDB download the Qt tools from?

[NickD2039]

Hi,

I think you may have misunderstood: I meant what is the timeframe for fixing the bug with VisualGDB where it downloads an out-of-date qmake? Or are you dropping support for qmake altogether? (which would be a deal-breaker for me).

Also, are you saying that Raspberry Pi is an unsupported platform as far as VisualGDB is concerned?

Nick

• This reply was modified 4 years, 5 months ago by NickD2039.

[NickD2039]

Hi,

Thanks for the swift reply.

What’s the timeframe for addressing the issue with QMake in VisualGDB?

Thanks,

Nick

 

• This reply was modified 4 years, 5 months ago by NickD2039.
• This reply was modified 4 years, 5 months ago by NickD2039.

[NickD2039]

Hi Support,

Unfortunately the objective is to port a large qmake-based project to the Pi and it has a complicated qmake pro-file structure that would be very impractical to port to cmake.

Is there another workaround for this? I’m prepared to compile Qt (at least the tools) from source but would need guidance on doing this.

It’s a shame as VisualGDB looks very promising and I would definitely spring for a licence after a successful evaluation.

Thanks,

Nick

[NickD2039]

UPDATE: I installed Qt 5.11.3 MinGW and tried to use the tools from that: Configure Qt Settings, Use qmake.exe etc. from a MinGW build of Qt, entered the qmake location (in my case C:\Qt\Qt5.11.3\5.11.3\mingw53_32\bin) hit Ok and then Finish. Same error occurs as it still uses the qmake from the cross-compile toolchain instead of the one I selected. If I re-open the Configure Qt Settings dialog I see that it has changed to ‘Use previously configured Qt tools for cross-compilation’. I can change it back but it always reverts to that when I hit Finish.

Would really like to find a solution to this as otherwise I’m super-impressed by VisualGDB and would love to use it 😉

Remote complation is not an option due to the size of the project that I’m attempting to port.

TIA

[NickD2039]

I think the problem is due to the version of the Qt tools that were downloaded by VisualGDB when I setup the Qt project.

Running \SysGCC\raspberry\Qt\v5\qmake.exe -v results in:

QMake version 3.0
Using Qt version 5.4.0 in c:/sysgcc/raspberry/arm-linux-gnueabihf/sysroot/usr/lib/arm-linux-gnueabihf

Which is very old. I tried bypassing it by manually calling qmake from a windows installation of Qt and the next compile attempt complained that ‘take_first' is not a recognized replace function.‘ And a google of that yielded a result in https://forum.qt.io/topic/93633/qmake_use-prf-6-take-first-is-not-a-recognized-replace-function/14

Where one commenter said ‘take_first() is part of the qmake language since Qt 5.8.0‘ so the toolchain.prf is incompatible with the qt tools that VisualGDB downloaded.

How can I reconfigure VisualGDB to use a specific version of the Qt tools?

[Author]

Posts