OK so it seems that restarting by restarting QT creator resolved the issue. No more exclamation and it seems to compile and deploy to the pi zero. However, when the application tried to run in QT creator it reports an error QXcbConnection: Could not connect to display.
I've tried setting the following variables in the Run environment, but it made no difference.
DISPLAY to :0
XAUTHORITY to /home/pi/.Xauthority
Some explanation on this would be helpful as I only tried this as a such in Google with people having a similar issue.
The connection is OK as it transfers to the Pi Zero target. However it doesn't run. When run from a terminal a segmentation fault is reported and nothing else.
I'm not a linux guru so I'm sure I'm missing something stupid!
For me, that would really be helpful as I have some projects that definitely not work with Clang.
My other observation is, that Clang overall works better and faster on Linux than in Windows. However, with every Creator update some of my projects break in one or another use case and it's no fun finding the reason for that again and again.
of course you should know, before that I had several problems with the configure command so i couldn't continue, eventually i solved them and removed all the files or folders related to them and tried again and created raspi file at home and continued
i used bellow link: https://wiki.qt.io/RaspberryPi2EGLFS
so i think that it have not build before in the same directory
When I add /home/dave/Qt/5.6.3/Src as the Target path (with Tools -> Options... -> Debugger -> General -> Add Qt sources...), the Source path is automatically set to /home/qt/work/qt. And no, /home/qt/work/qt does not exist on my Ubuntu machine.
Similarly, none of the four directories which were automatically added as Source path when I added C:\Qt\5.6.3\Src as the Target path (that is: C:/work/build/qt5_workdir/w/s, Q:/qt5_workdir/w/s, c:/Users/qt/work/install and c:/users/qt/work/qt) exists on my Windows machine.
I suppose that these source paths are directories in which the Qt versions I installed were built. The debugger then maps those directories to the directory where I have installed Qt. The mapping works in Windows, not in Ubuntu.
i know you can add buttons into the button bar but what about a check box just above it? how ?
It is in principle possible with some black magic incantations. However, if you want to customize it further than already suggested, I advise you to make your own custom message box dialog in designer and take it from there.
So what you need is a custom link stage under the project file; something that references the external object .o files. I'd generally store them outside of the project folder tree, and create a project file that knows how to find them.
It runs on the following platforms: X86/Linux, AMD64/Linux, ARM/Linux, ARM64/Linux, PPC32/Linux, PPC64/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, X86/Solaris, AMD64/Solaris, ARM/Android (2.3.x and later), ARM64/Android, X86/Android (4.0 and later), MIPS32/Android, X86/Darwin and AMD64/Darwin (Mac OS X 10.12).
@Patrick-Fromberg Agree, it would be good to have the possibility to update after using offline installer to install.
Regarding compilers: you can configure them as well in QtCreator and then select the correct compiler in your Kits.
@koahnig Yeah, I used the one distributed with the installer, but I think the reason that it failed was because there might have been paths for the linker that wasn't properly set up if you selected to install the Qt Creator and the Qt kit at the same time.
When I installed the older computer I think I installed the kit afterwards because I wasn't aware of that I needed to manually select it at installation time.
Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.