• State
  • Locked Locked
  • Replies 10 replies
  • Subscribers 99 subscribers
  • Views 821 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

PROCESSOR-SDK-AM437X: Qt remote objects compiler repc missing from sdk toolchain

James Pawlyk
Expert 1075 points
Part Number: PROCESSOR-SDK-AM437X


I understand this may be outside TI's support domain, but any help would be appreciated.    Our team is using Qt remote objects. I was able to modify recipes so that the plug-ins show  up in the toolchain.  For the life of my i cannot figure out how to get the repc tool that is required for the toolchain to be included. 

I noticed that the following are in the toolchain, but not the host repc compiler:

builder@rover:~/sdks/sdktoolkit$ find . -name repc
./sysroots/armv7at2hf-neon-linux-gnueabi/usr/src/debug/qtremoteobjects/5.11.3+gitAUTOINC+92ae729691-r0/build/tools/repc
./sysroots/armv7at2hf-neon-linux-gnueabi/usr/src/debug/qtremoteobjects/5.11.3+gitAUTOINC+92ae729691-r0/git/tools/repc
./sysroots/armv7at2hf-neon-linux-gnueabi/usr/bin/.debug/repc

  • 0
    TI__Mastermind 44965 points

    Hello,

    As an experiment, I am wondering if you could please include the following statement in your target recipe: 'BBCLASSEXTEND = "native"'. 

    Regards,
    Krunal

  • 0 in reply to Krunal Bhargav34
    Expert 1075 points

    No, that did not help,  I cleaned my target image and meta-toolchain-arago-tisdk before I rebuilt.

  • 0 in reply to James Pawlyk
    Expert 1075 points

    Krunal, you seem to have experience with toolchain/sdk questions.  Any chance I could ask a few general questions?

  • 0 in reply to James Pawlyk
    TI__Mastermind 44965 points

    Hello,

    I apologize for the delayed response but with regards to your original question, I recommend you to reach out to Qt/meta-qt for more details on adding host compilers for the target recipes. Yes, please feel free to ask any general questions you may have with regards to TI SDK. 

    Regards,
    Krunal

  • 0 in reply to Krunal Bhargav34
    Expert 1075 points

    Since my last note I figured out some of my issues, one lingering thing I have found is that the qmake built by arago-base-tisdk-image has hard coded paths to the bitbake directories so it is not really practical to give the sdk to a application developer running on their own machine.  Or am I missing something?

  • 0 in reply to James Pawlyk
    TI__Mastermind 44965 points

    Hello,

    Could you please provide an example of the hard coded paths?

    Regards,
    Krunal

  • 0 in reply to Krunal Bhargav34
    Expert 1075 points

    sorry it took so long to get back  to you... stuff like this "strings qmake | grep mybitbakeusername (jsp)"   

    home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/library/proitems.h
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/option.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/project.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/library/ioutils.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/library/qmakeevaluator.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/library/qmakeparser.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/generators/makefile.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/generators/projectgenerator.h
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/generators/win32/msvc_objectmodel.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/qmake/generators/xmloutput.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/src/corelib/codecs/qutfcodec.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/src/corelib/global/qglobal.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/src/corelib/global/qrandom.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/src/corelib/io/qbuffer.cpp
    /home/jsp/projects/refsdk_6_0/build/arago-tmp-external-arm-toolchain/work/x86_64-nativesdk-arago-linux/nativesdk-qtbase/5.11.3+gitAUTOINC+08de243eaa-r0/git/src/corelib/io/qdir.cpp

    the stuff you see with qmake -query is correct:  (user == builder)

    QT_SYSROOT:/home/builder/sdks/tooltisdk/sysroots/armv7at2hf-neon-linux-gnueabi
    QT_INSTALL_PREFIX:/home/builder/sdks/tooltisdk/sysroots/armv7at2hf-neon-linux-gnueabi/usr

  • 0 in reply to James Pawlyk
    TI__Mastermind 44965 points

    Hello,

    Please correct me if I am wrong but you are implying that the QT_SYSROOT and QT_INSTALL_PREFIX are pointing to a hard coded path unlike the qmake -querry?

    Regards,
    Krunal

  • 0 in reply to Krunal Bhargav34
    Expert 1075 points

    i am not sure i understand your questions.  qmake -query reports paths to the installed sdk.  but if i do strings on the qmake binaries i see paths to original bitbake environment.  not sure if these are overridden latter.

  • 0 in reply to James Pawlyk
    TI__Mastermind 44965 points

    Hello,

    In our SDK, we have the following file "environment-setup" under the directory "<psdk_dir>/linux-devkit". In the file, we configure all the environments and usually it is recommended to source the file, in order to set the qmake path correctly.

    Regards,
    Krunal