Navigation

    Qt Forum

    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular
    • Search
    • Unsolved
    1. Home
    2. Tags
    3. cross-compiling
    Log in to post

    • UNSOLVED Qt 5.15.2 cross compile with different glibc and glibcxx on host and target
      Mobile and Embedded • cross-compiling aarch64 x8664 • • Kiruseni  

      8
      0
      Votes
      8
      Posts
      287
      Views

      @Kiruseni honestly i dont know, i've never used nor seen this parameter until now actually. I always used the -sysroot parameter so far. But it seems it is set automatically anyways. I assume it just means that the compiler handles the sysroot (which gcc is capable of)
    • SOLVED adding qtimer with wiringPiISR
      Mobile and Embedded • raspberry threads cross-compiling timer wiringpi • • amina  

      12
      0
      Votes
      12
      Posts
      513
      Views

      @amina I posted this in an other forum because it has been a while that I am stuck and it has to be fixed .. I am going to share the solution it may help someone https://stackoverflow.com/questions/66869600/timer-couldnt-work-with-wiringpiisr-qtquick-application/66873812?noredirect=1#comment118230663_66873812 static instances of QObject are also not supported so the instance vitesse should be created after QApplication. this will fix the problem : static void isrInput_vitesse(); static Capteur_Input *vitesse = nullptr; static void isrInput_vitesse() { if(!vitesse) //not initialized yet return; QMetaObject::invokeMethod( vitesse, "isrCallback", Qt::QueuedConnection ); //or blockingQueue if you need to handle it directly in Qt way. } and in the main fucntion int main(int argc, char *argv[]) { QApplication a(argc, argv); //..... your main application body vitesse = new Capteur_Input(Pin_vitesse,PUD_OFF,INT_EDGE_RISING,isrInput_vitesse); ctx->setContextProperty("vitesse", vitesse); //... } the function isrCallback should be a slot
    • SOLVED could not add wiringPi to Qt after cross compiling
      Mobile and Embedded • cross-compiling wiringpi raspberry pi4 • • amina  

      13
      0
      Votes
      13
      Posts
      586
      Views

      @amina said in could not add wiringPi to Qt after cross compiling: I just need to synchronize the /usr/include and /usr/lib or all the sysroot? It depends on the changes you do, and if you know exactly what folders were modified. Some people perform the sync for the whole sysroot just in case.
    • UNSOLVED Android settings error- Platform SDK not found
      Installation and Deployment • windows 10 cross-compiling android sdk build failed • • san_qt_enthusisast  

      3
      0
      Votes
      3
      Posts
      153
      Views

      @san_qt_enthusisast I guess you should be using Java 8
    • UNSOLVED problem with cross compiling for raspberry pi 4
      Installation and Deployment • eglfs cross-compiling raspberry pi 4 • • amina  

      1
      0
      Votes
      1
      Posts
      339
      Views

      No one has replied

    • UNSOLVED Building qtdeclarative Gives "fxc.exe: No such file or directory"
      Installation and Deployment • cross-compiling qtdeclarative • • Kurausukun  

      2
      0
      Votes
      2
      Posts
      326
      Views

      I ran into this problem trying to compile ffmpeg with a QT dependancy.... to get past the not found I had to have a path to windows kit that held the fxc.exe file in my case C:\Program Files (x86)\Windows Kits\8.1\bin\x64. the cause seems to be in my case ? \qtdeclarative-git\plugins\scenegraph\d3....the make file has 26 shader header files it is trying to create with fxc.exe . Adding the path gets rid of the file not found BUT it does not get rid of the compile error the command in the make file does not execute correctly at this point it gives a too many files error . (I am still working on that part of it before I bug report it . This is assuming I am using the right fxc.exe and it can be run correctly from inside the build environment in my case mingwin. So if you have any feedback on how you got this working (IF) it would be appreciated here as well . I suspect that the make file has a TAB before the command that is causing the problem because if i cut and paste the commands with the tab i get errors but if i remove the tab it runs fine .
    • UNSOLVED Qt 5.15.1 for Raspberry Pi 4 (cross)
      Mobile and Embedded • cross-compiling raspberry pi 4 pkg-config • • mneg  

      5
      0
      Votes
      5
      Posts
      1730
      Views

      FYI: the issues vanished with the previous version Qt 5.14.2 and the 7.5.0 Linaro toolchain (but not the others!). Suddenly the tests are being run. My cross development toolchain now is up and running, however, I still find it odd that there are no error messages in Qt's build system.
    • UNSOLVED "Segmentation fault (core dumped)" error after running executable file on the Android device (using Android Clang (C++,aarch64) compiler)
      Mobile and Embedded • cross-compiling qtandroid aarch64 arm64-v8a clang++ • • morteza ali ahmadi  

      7
      0
      Votes
      7
      Posts
      997
      Views

      @morteza-ali-ahmadi I'm not an Android expert. Maybe somebody else knows more.
    • UNSOLVED segmentation fault
      Mobile and Embedded • qt 4.8 cross-compiling mqtt armv7 • • Milav  

      61
      0
      Votes
      61
      Posts
      7470
      Views

      @Milav said in segmentation fault: the difference between host pc and Embedded target board is only QT source. Host pc => qmake (qt version 5.4.0 ) Embedded target => qmake (qt version 4.8.7) You should have stated these settings from the very beginning... :-) Anyway, could it be possible that you build Qt 4.8.7 for PC (host) and build your example again with that Qt version and run in PC to see what happens.
    • UNSOLVED Cross Compilation error
      Installation and Deployment • arm cross-compiling cortexa8 • • Milav  

      6
      0
      Votes
      6
      Posts
      754
      Views

      @sierdzio Okay Thank You. :)
    • UNSOLVED Error During QT (5.7.1) Cross Compilation
      Installation and Deployment • arm cross-compiling build error cortexa8 qt5.7.1 • • Milav  

      2
      0
      Votes
      2
      Posts
      224
      Views

      Hi, Two question: Why Qt 5.7.1 ? The current LTS is 5.12.5 Can you use a more recent version of GCC ? 4.4 is a bit old.
    • SOLVED RPI cross-compilation errors : lGLESv2,cannot find id and xcb
      Installation and Deployment • cross-compiling ubuntu 16.04 raspberry eglfs xcb opengl lglesv2 • • vishbynature  

      4
      0
      Votes
      4
      Posts
      556
      Views

      It's not a problem of Qt Creator. The mkspec used for the RPI3 is still valid unless your sysroot comes from a Debian Stretch were they have changed the library name. You need to modify the mkspec under devices that matches the Rpi3
    • UNSOLVED How to Cross Compile QT5 Libraries
      Mobile and Embedded • arm libraries cross-compile cross-compiling crosscompile • • closx  

      4
      0
      Votes
      4
      Posts
      492
      Views

      Hi, If you copy the files over your target respecting the same folders as your desktop machine, then you won't have anything special to do.
    • UNSOLVED Absolute paths to EGL library in libQt5Gui.so since Qt 5.12.1
      Installation and Deployment • qmake eglfs cross-compiling • • eglimi  

      15
      0
      Votes
      15
      Posts
      2743
      Views

      @ruisebastiao well this is a rather hacky workaround to fix something Qt has broken within a LTS version. The thing is that libmali uses a unified lib which contains all symbols for EGL, OpenGL ES etc. so it would be wrong to apply a single .so name. It worked fine in 5.12.0 so it's probably time to come up with a solution for this "use absolute paths" nonsense has introduced. it works once you duplicate the unified lib & patch it. So Qt needs to deal with this kind of libs instead of forcing users to patch stuff. https://forum.qt.io/topic/104015/cross-compilation-generates-full-paths-in-libqt5gui-so-for-libglesv2-so-and-libgl-so-then-cannot-be-found-in-execution-time/3
    • UNSOLVED Unknown modules QT:Charts, QT:quick.
      General and Desktop • qtquick qtcharts cross-compiling qtvirtualkeyboa qtraspberrypi • • Andrex_Qt  

      7
      0
      Votes
      7
      Posts
      4671
      Views

      @SGaist thanks I‘ll bookmark that as well I was just googleing qtcharts source and took the firts link 🙈
    • UNSOLVED Cross compiling Qt Everywhere Raspberry Pi
      Mobile and Embedded • raspberry cross-compiling raspberry eglfs raspbian • • herionoid  

      2
      0
      Votes
      2
      Posts
      789
      Views

      Did you try the this https://bugreports.qt.io/browse/QTBUG-62216 For the pi2 configuration the change should be something like this: -QMAKE_LIBS_EGL = -lEGL -lGLESv2 -QMAKE_LIBS_OPENVG = -lEGL -lOpenVG -lGLESv2 +QMAKE_LIBS_EGL = -lbrcmEGL -lbrcmGLESv2 +QMAKE_LIBS_OPENGL_ES2 = -lbrcmEGL -lbrcmGLESv2 +QMAKE_LIBS_OPENVG = -lbrcmEGL -lbrcmOpenVG -lbrcmGLESv2
    • UNSOLVED Which is Yocto meta layer branch(morty?) for Qt5.9 cross compiler toolchain?
      Mobile and Embedded • qt5.9 cross-compiling toolchain armv7 • • Mahesh Kumar Kodanda  

      1
      0
      Votes
      1
      Posts
      742
      Views

      No one has replied

    • UNSOLVED Raspberry Pi Beginners Issue: toolchain or QMakeSpec is broken
      Tools • cross-compiling toolchain armhf • • CybeX  

      7
      0
      Votes
      7
      Posts
      16497
      Views

      Because I had the same Issues with the same Tutorial and often came along this discussion while searching for possible solutions, I took the privilege to dig up this old thread. With the help of What would be a pratical example of sysroot and prefix options for Qt and especially the mentioned option, quote:" -no-gcc-sysroot very specific hack for compilers that can't find their own crt inside --sysroot passes sysroot to pkgconfig and others, but not to gcc so that gcc will be called with -L/sysroot/lib/ correctly, but doesn't try to find implicit paths (crt) here. ", I was able to fix the problem.
    • UNSOLVED Setting up a cross-compiling ide allowing cross platform and mutiple architecture development
      General and Desktop • cross platform cross-compiling armhf x64 x86 • • CybeX  

      6
      0
      Votes
      6
      Posts
      3133
      Views

      @CybeX 1:I saw on google that someone else had this error with gcc 4.8. Upgrading solved it. Not saying it will for you. But was the only errors i could find in your log. 2: Sorry I don't know how to solve this. People are compiling for the PI but I never got around to try one so the details of getting it to work is also unknown to me. Update: I have a good eye to https://www.ics.com/blog/configuring-qt-creator-raspberry-pi but no board so didnt try yet.
    • UNSOLVED How to compile linux app using windows
      General and Desktop • linux windows qt quick cross-compiling • • orzel1244  

      7
      0
      Votes
      7
      Posts
      1622
      Views

      To build QtCharts calling qmake CONFIG+=debug_and_release make debug make release make install should be enough to build and install it
    • UNSOLVED Cross-compiling 5.7 on Windows
      QtonPi • qt 5.7 raspberry pi windows 7 cross-compiling • • amura.cxg  

      4
      0
      Votes
      4
      Posts
      3350
      Views

      @BruceNaylor Hmm that's interesting! I posted on the C++ Gurus forum and a couple guys there suggested I use the MinGW that gets installed with QT Creator (when you select that option) and that actually fixed my issue with registry keys. I was going to give cross compiling another try on Windows, maybe your fudges will fix some other issues I've into. I appreciate the suggestions!
    • SOLVED Error while loading shared libraries during cross-compiling
      QtonPi • cross-compiling • • feniks_fire  

      4
      0
      Votes
      4
      Posts
      1908
      Views

      Yeah, I have right. I copy all Qt library to RPI and use this in rpi terminal: export LD_LIBRARY_PATH="/home/pi/QtBase-5.7.0/lib" ./Test and everything work. Tomorrow I'll try just install qt in rpi, and this should work without terminal. Another topic solved.