I am using Docker to cross compile a project in QTCreator. The project is actually a CMake project which needs to build in different environment, for which the Docker step is. To trigger the build I use a custom build step which invokes the build process within the Docker container like this: docker exec -t centosbuild /bin/bash -c 'cd /path/to/my/build/debug; make -j4' The Docker container and the docker host share the same directory so QTCreator does see the source files which CMake uses. This setup works well, but unfortunately the Issues tab remains empty when there are compile errors. I have searched extensively on the topic and my guess is that the GCC error parser is not correctly triggered. Could you provide me with some suggestions. I have created the project in QTCreator by using Import existing CMake project. Thanks.

Sorry for the necropost, but I found the solution to this problem! QtCreator parses errors in stderr, but ssh is outputting to stdout. You need to redirect ssh output by appending "1>&2" (no quotes) to your command and QtCreator will now parse your errors. Hope this helps whoever else is interested

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Qt Creator does not parse compile output on remote build

Unsolved Qt Creator and other tools

4 Posts 4 Posters 1.9k Views

Y Offline

Y Offline
YordanP
wrote on last edited by A Former User

#1

I am using Docker to cross compile a project in QTCreator. The project is actually a CMake project which needs to build in different environment, for which the Docker step is. To trigger the build I use a custom build step which invokes the build process within the Docker container like this:

docker exec -t centosbuild /bin/bash -c 'cd /path/to/my/build/debug; make -j4'

The Docker container and the docker host share the same directory so QTCreator does see the source files which CMake uses. This setup works well, but unfortunately the Issues tab remains empty when there are compile errors. I have searched extensively on the topic and my guess is that the GCC error parser is not correctly triggered. Could you provide me with some suggestions.

I have created the project in QTCreator by using Import existing CMake project.

Thanks.
1 Reply Last reply
1
E Offline

E Offline
elldekaa
wrote on last edited by

#2

Any news about this ?
I'm interested in the same workflow...
1 Reply Last reply
0
S Offline

S Offline
SGaist Lifetime Qt Champion
wrote on last edited by

#3

Hi and welcome to devnet,

Since it's a pretty particular setup you should rather bring this question to the Qt Creator mailing list. You'll find there Qt Creator's developers/maintainers. This forum is more user oriented.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

1 Reply Last reply
2
M Offline

M Offline
Matias N. Goldberg
wrote on last edited by

#4

Sorry for the necropost, but I found the solution to this problem!

QtCreator parses errors in stderr, but ssh is outputting to stdout.
You need to redirect ssh output by appending "1>&2" (no quotes) to your command and QtCreator will now parse your errors.

Hope this helps whoever else is interested
1 Reply Last reply
3