Forums - VISLAM compilation and executiion on flight board

2 posts / 0 new
Last post
VISLAM compilation and executiion on flight board
sdyavarasetti
Join Date: 6 Jan 17
Posts: 22
Posted: Mon, 2018-03-12 00:43

Hi,

I am trying to compile VISLAM code with some minor changes on APQ8074. Not able to compile. Getting error like :

make: Warning: File `main.cpp' has modification time 1.5e+09 s in the future
/prj/atlanticus/releases/ecosystem/intrinsyc3.1.2/qrlSDK/dst//gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux/bin/arm-linux-gnueabihf-g++ -std=c++11 -mthumb -fdata-sections -Wa,--noexecstack -fsigned-char -Wno-psabi -Wall -Wextra -Wno-unused-function -include limits.h -Wno-unused-local-typedefs -O3 --sysroot=/prj/atlanticus/releases/ecosystem/intrinsyc3.1.2/qrlSDK/dst//sysroots/eagle8074 -DISA_8x74_v7a -isystem ./ -isystem ../../inc -isystem ../mvGateway/platform -c -o main.o main.cpp
make: /prj/atlanticus/releases/ecosystem/intrinsyc3.1.2/qrlSDK/dst//gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_linux/bin/arm-linux-gnueabihf-g++: Command not found
make: *** [main.o] Error 127

How to solve this error

What are different modes CAPTURE MODE, VIO mode and both.?

Can we get VISLAM code-flow?

Thanks in-advance.

SaiKrishna

  • Up0
  • Down0
gmcgrath
Join Date: 21 Aug 13
Posts: 59
Posted: Wed, 2018-03-14 10:53

The Makefile was left with a path in it to an interal cross-compile toolchain that you would not have access to.  One should edit the Makefile.8x74 and change SDK_ROOT to "/usr/bin" and CXX to just "g++".

  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.