New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sdk package not working (qt) #20
Comments
I'll dig into this when the eMMC boot works |
I'll take a look into this at the weekend |
Sounds like a linking issue. Did you add the modules to your .pro file? |
Yes, this is not the problem (i use project that works before with the older version qt5.6 or example). I think it's a problem with mkspec (use linux-g++ but we needs linux-oe-g++) ! see this comparison between an older qmake that worked with the new generated. |
Personally I use that layer : https://github.com/meta-qt5/meta-qt5. It has nothing to do with meta-freescale. |
Yes i use also meta-qt5, but on meta-freescale they have otavio salvador who is a maintainer of meta-qt5. If you know a mailing list, forum ... on meta-qt5 let me know please. |
Hi, what branch are you using? For krogoth a krogoth branch in meta-qt5 is recommended. It could be possible names of tools changed and so the qt5 tutorial needs an update. If you find some time to create a minimal example we can provide this and refer to it |
Hi graugans, i use master for meta-qt5 and krogoth for the other (but this is the same result with krogoth branch, tested). The only thing that is needed to change is to add linux-oe-g++ to Qt mkspes field. I can create an example but can you preceise your ask ? Would you like a tutorial to configure QtCreator or deployment example ? |
I close this issue, another user have tested it (mailing list meta-freescale) and works too for him. |
@graugans , @cyrilfr about this problem i posted on yocto mailing list this issue. Someone post me a private message that explain this : From the patch:
Since QT_CROSS_COMPILE then it sets the SPEC to linux-g++. To test if you have the same problem as me. Remove the patch from the recipe nativesdk-qtbase_git.bb and rebuild.
In my last build i did this and this resolve the problem (no need to change QT mkspecs in qtcreator). Do you think we push this on the recipe ? |
…ing for SDK The patch 0008-configure-paths-for-target-qmake-properly.patch seems to be intended for the target, not for native/nativesdk, as it breaks the mkspec setting (sets linux-g++ instead of linux-oe-g++) by default. This issue is also described here: graugans/meta-udoo#20 (comment) Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
…ing for SDK The patch 0008-configure-paths-for-target-qmake-properly.patch seems to be intended for the target, not for native/nativesdk, as it breaks the mkspec setting (sets linux-g++ instead of linux-oe-g++) by default. This issue is also described here: graugans/meta-udoo#20 (comment) Signed-off-by: Frieder Schrempf <frieder.schrempf@exceet.de> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
I have build a sdk package for sa62 (build with qt5.6.2, meta-qt5 layer krogoth branch). The sdk build fine. After install the package and configure qt creator for the kit, i have this error when i try to deploy an app :
/usr/bin/ld: cannot find -lQt5Widgets /usr/bin/ld: cannot find -lQt5Gui /usr/bin/ld: cannot find -lQt5SerialPort /usr/bin/ld: cannot find -lQt5Core /usr/bin/ld: cannot find -lGLESv2 collect2: error: ld returned 1 exit status make: *** [terminal] Error 1
if i use the neo kit (qt 5.6.1) that i already have the app compile and i can deploy
if i compare the qt5 details of this 2 conf, i can see a difference with mkspec :
neo : linux-oe-g++
secoA62 : linux-g++
i don't know if is the problem ...
The text was updated successfully, but these errors were encountered: