[manoncloud9]

Thanks for the guidance and fixes to the tutorial, I now have the files copied to the Beaglebone as instructed and ready to build.

The next issue occurs when I get to step 7 of the tutorial.  According to the documentation reopening the project should straighten out IntelliSense so I can compile.  What happens if that doesn’t work and I’m still stranded unable to build the demo?

If I can get through this issue and actually compile and run both on the local platform and on the Beaglebone, I’m inclined to go ahead and purchase the product and get started on my project.  Your assistance is greatly appreciated!

[manoncloud9]

Great!  I downloaded the toolchain and loaded it successfully.  Now when I create the demo project I have to find the toolchain by selecting the option (Select toolchain manually by locating gdb.exe) because a new entry for the installed toolchain does not show up in the “Cross-toolchain” drop down of the “New Linux Project” dialog box.  I assumed it was referring to arm-linux-gnueabihf-gdb.exe which I found in C:\SysGCC\Beaglebone\bin.

I then followed the instructions to “configure QT settings” finding the appropriate Qmake binary and Cross-specs directory and press OK.  The “Mismatching environment detected” dialog box did not appear so I pressed “Finished” and received the following Error Message:

“Test program appears inconsistent. Expected return code 108. Actual return code 127”

and in the detailed log box:

Tool arguments:
/home/debian/VisualGDB_ToolchainTestProgram_Deployed: error while loading shared libraries: libQt5Widgets.so.5: cannot open shared object file: No such file or directory

Are these problems now a result of having loaded the incorrect toolchain to begin with?

What course of action should I pursue from here?

Thanks

 

[Author]

Posts