There seems to be a BSP related issue when using the newest qtcreator 4.8.0 (tested on Ubuntu 18.04 and Ubuntu 18.10).
First of all, building our application works as expected, so these are only visual errors. However, qtcreator shows many of them, because the file gnu/stubs-soft.h cannot be found. So these seems to be a BSP related issue.
When I open any file of our project using the Toradex Kit, I get the following error:
stubs-32.h:7:11: fatal error: 'gnu/stubs-soft.h' file not found
main.cpp:1:1: note: in file included from /home/christian/sources/project/src/main.cpp:1:
main.cpp:1:10: note: in file included from /home/christian/sources/project/src/main.cpp:1:
mainwindow.h:4:10: note: in file included from /home/christian/sources/project/src/mainwindow.h:4:
QMainWindow:1:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/qt5/QtWidgets/QMainWindow:1:
qmainwindow.h:43:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/qt5/QtWidgets/qmainwindow.h:43:
qtwidgetsglobal.h:43:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/qt5/QtWidgets/qtwidgetsglobal.h:43:
qtguiglobal.h:43:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/qt5/QtGui/qtguiglobal.h:43:
...
os_defines.h:39:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/c++/7.3.0/arm-angstrom-linux-gnueabi/bits/os_defines.h:39:
features.h:447:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/features.h:447:
stubs.h:53:10: note: in file included from /usr/local/oecore-x86_64/sysroots/cortexa9t2hf-neon-angstrom-linux-gnueabi/usr/include/gnu/stubs.h:53:
Then I took a look into the stubs-32.h:
/* This file is automatically generated.
This file selects the right generated file of `__stub_FUNCTION' macros
based on the architecture being compiled for. */
#if !defined __ARM_PCS_VFP
# include <gnu/stubs-soft.h>
#endif
#if defined __ARM_PCS_VFP
# include <gnu/stubs-hard.h>
#endif
So as we can see, there is no stubs-soft.h, however there is a stubs-hard.h, so the errors can be resolved with a simple #define __ARM_PCS_VFin every file - yeah. (ATTENTION: I don’t know the effects of this change!).
However, this is something, that should be fixed in the BSP itself.
Please let me know, if you need further information.
There seems to be a BSP related issue when using the newest qtcreator 4.8.0 (tested on Ubuntu 18.04 and Ubuntu 18.10). First of all, building our application works as expected, so these are only visual errors. However, qtcreator shows many of them, because the file gnu/stubs-soft.h cannot be found. So these seems to be a BSP related issue.
What did you build exactly and how?
Could you check where this is defined in your SDK or QT creator Environment?
I setup a Ubuntu 18.04 as a VM and installed qtcreator 4.8.0 with the installer from the Qt FTP. I manually created the toolchain with our bitbake buildsystem (“bitbake meta-toolchain-qt5”) and installed it on the VM. I configured the qt creator kit/compiler/etc. as described in your tutorials on developer.toradex.com. And finally: i tried to compile our custom application. The compilation - as I already mentioned - works just fine. There are just really many “visual errors”: alt text
Could you check where this is defined in your SDK or QT creator Environment?
Sure, there you go (sorry for the formatting, somehow, I don’t get it right…)
Further information: qtcreator 4.7 has the same problem qtcreator 4.6 does NOT have the problem It seems like the QtCreator-Teams switched on their Clang code model by default with qtcreator 4.7, which doesn’t sallow this error anymore.
BR Christian
As you said, this seems to only a visual error, then this shouldn’t be that important. For the solution you wrote:
So as we can see, there is no stubs-soft.h, however there is a stubs-hard.h, so the errors can be resolved with a simple #define __ARM_PCS_VFin every file - yeah. (ATTENTION: I don’t know the effects of this change!).
Adding define in every file will be very time consuming. It will be better to find a common file for all the files which have this missing file error or just create a empty stubs-soft.h in the gnu folder.
Thanks for the respone. Yeah, it isn’t that important, just really annoying.
Adding define in every file will be very time consuming. It will be better to find a common file for all the files which have this missing file error or just create a empty stubs-soft.h in the gnu folder.
Didn’t thought about that, but yeah that should work to. Thanks for the hint.
