topic Re: Out of box Euclid build of librealsense fails in Items with no label

Out of box Euclid build of librealsense fails

MCart5 — Tue, 05 Sep 2017 16:33:25 GMT

I get this error after following the doc/installation.md steps. Also

This also happens with "https://github.com/IntelRealSense/librealsense.git https://github.com/IntelRealSense/librealsense.git"

euclid@EUCLID_xxxx:~$ git clone https://github.com/IntelEuclid/librealsense.git https://github.com/IntelEuclid/librealsense.git euclid_librealsense

Cloning into 'euclid_librealsense'...

remote: Counting objects: 16532, done.

remote: Total 16532 (delta 0), reused 0 (delta 0), pack-reused 16531

Receiving objects: 100% (16532/16532), 22.19 MiB | 1012.00 KiB/s, done.

Resolving deltas: 100% (11728/11728), done.

Checking connectivity... done.

euclid@EUCLID_xxxx:~$ cd euclid_librealsense

euclid@EUCLID_xxxx:~/euclid_librealsense$ mkdir build

euclid@EUCLID_xxxx:~/euclid_librealsense$ cd build/

euclid@EUCLID_xxxx:~/euclid_librealsense/build$ cmake ../

-- Building in a ROS environment

-- The C compiler identification is GNU 5.4.0

-- The CXX compiler identification is GNU 5.4.0

-- Check for working C compiler: /usr/bin/cc

-- Check for working C compiler: /usr/bin/cc -- works

-- Detecting C compiler ABI info

-- Detecting C compiler ABI info - done

-- Detecting C compile features

-- Detecting C compile features - done

-- Check for working CXX compiler: /usr/bin/c++

-- Check for working CXX compiler: /usr/bin/c++ -- works

-- Detecting CXX compiler ABI info

-- Detecting CXX compiler ABI info - done

-- Detecting CXX compile features

-- Detecting CXX compile features - done

-- Using CATKIN_DEVEL_PREFIX: /home/euclid/euclid_librealsense/build/devel

-- Using CMAKE_PREFIX_PATH: /opt/ros/kinetic

-- This workspace overlays: /opt/ros/kinetic

-- Found PythonInterp: /usr/bin/python (found version "2.7.12")

-- Using PYTHON_EXECUTABLE: /usr/bin/python

-- Using Debian Python package layout

-- Using empy: /usr/bin/empy

-- Using CATKIN_ENABLE_TESTING: ON

-- Call enable_testing()

-- Using CATKIN_TEST_RESULTS_DIR: /home/euclid/euclid_librealsense/build/test_results

-- Looking for pthread.h

-- Looking for pthread.h - found

-- Looking for pthread_create

-- Looking for pthread_create - not found

-- Looking for pthread_create in pthreads

-- Looking for pthread_create in pthreads - not found

-- Looking for pthread_create in pthread

-- Looking for pthread_create in pthread - found

-- Found Threads: TRUE

-- Found gtest sources under '/usr/src/gtest': gtests will be built

<spa...

Re: Out of box Euclid build of librealsense fails

idata — Tue, 05 Sep 2017 20:58:42 GMT

Hello weaponeer,

Thank you for your interest in the Intel® Euclid™ Development Kit.

I reproduced the issue you are experiencing. But I'll be needing more time to come up with a solution.

As soon as I have relevant information I'll post it here.

Thank you for your patience.

Regards,

Andres V.

Re: Out of box Euclid build of librealsense fails

MCart5 — Tue, 05 Sep 2017 21:07:11 GMT

Andres,

Many thanks -- I tried adding lr200_mm.cpp back to the CMakeLists.txt -- but this caused other issues with Motion related includes. I started over at that point with a new clone, and decided to post -- as others must have found a way around this issue.

Thanks,

MarkC

Re: Out of box Euclid build of librealsense fails

idata — Wed, 06 Sep 2017 20:26:43 GMT

Hello MarkC,

The reason behind the error message has to do with the fact that the librealsense version on Github has components that are not compatible with the Euclid.

There is a version of librealsense that is already installed in the Euclid, it is located in /usr/lib/librealsense. Could you please tell me why are you trying to download the version on Github?

I'll be waiting for your response.

Have a nice day.

Regards,

Andres V.

Re: Out of box Euclid build of librealsense fails

MCart5 — Thu, 07 Sep 2017 16:46:04 GMT

Andres,

Thanks for the reply, I do appreciate it.

My reason for wanting a local git-based librealsense is to develop with the ability to debug at the source level, and to rapidly pick up fixes and extensions. Our motivation to explore this platform (Euclid) and its possible uses were driven to a great deal by the fact that there was an expectation that the software platform was open. And that it provided in a small package a broad and well integrated suite of sensors that would have otherwise required integration at several levels.

I'm not trying to be difficult here, but to me it does not seem unreasonable to expect the publicly available SDK to build on the target designed to demonstrate it ?

Working around this is acceptable, but I hope you can see my point -- I have too many orphaned platforms in the "drawer of obsolescence" -- and too little time to resuscitate them.

Are there any plans to address this, or suggestions as to how I might approach fixing it myself ?

Mark

Re: Out of box Euclid build of librealsense fails

idata — Thu, 07 Sep 2017 17:16:05 GMT

Hello Mark,

I understand your interest in gaining full control of the software platform.

There hasn't been any announcements for a publicly available SDK, so I can't tell you when, or if, it will be available.

What I can assure is that I will share your request with the corresponding team.

Have a nice day.

Regards,

Andres V.

Re: Out of box Euclid build of librealsense fails

MCart5 — Fri, 08 Sep 2017 16:06:47 GMT

Andres,

Thanks -- I hope the developers find a way. Meantime I will try and work around this as I have time.

Cheers,

MarkC

Re: Out of box Euclid build of librealsense fails

Meitav_K_Intel — Tue, 19 Sep 2017 14:20:20 GMT

Hi Weaponeer,

Fortunately I have a workaround for you.

If you go to the CMakeLists.txt and turn off "BUILD_UNIT_TESTS", it should compile fine.

Unless you plan on using those (I know that I haven't ever had the need to use them myself), it shouldn't be a problem.

If you want to build the examples (which aren't exactly as relevant to the Euclid, but can help you better understand librealsense), you can check that on, but make sure to build GLFW first, since it's a dependency.

Regards,

Meitav

Intel Euclid Development Team

Re: Out of box Euclid build of librealsense fails

MCart5 — Tue, 19 Sep 2017 19:43:07 GMT

Meitav,

Thanks ! That worked -- and led me to this:

cmake .. -DBUILD_EXAMPLES:BOOL=true -DBUILD_UNIT_TESTS:BOOL=false
Which gave me a clean build with example binaries

euclid@EUCLID_7189:~/librealsense/build$ ls -l devel/lib/librealsense

total 5280

-rwxrwxr-x 1 euclid euclid 340496 Sep 19 11:51 cpp-alignimages

-rwxrwxr-x 1 euclid euclid 192976 Sep 19 11:51 cpp-callback

-rwxrwxr-x 1 euclid euclid 396352 Sep 19 11:52 cpp-callback-2

-rwxrwxr-x 1 euclid euclid 442232 Sep 19 11:52 cpp-capture

-rwxrwxr-x 1 euclid euclid 1051184 Sep 19 11:52 cpp-config-ui

-rwxrwxr-x 1 euclid euclid 187808 Sep 19 11:52 cpp-enumerate-devices

And they ran ok (so far) !

euclid@EUCLID_7189:~/librealsense/build$ devel/lib/librealsense/cpp-enumerate-devices

Device 0 - Intel RealSense LR200:

Serial number: 3511805472

Firmware version: 2.0.71.09

USB Port ID: 2-4

Camera info:

DEVICE_NAME : Intel RealSense LR200

DEVICE_SERIAL_NUMBER: 3511805472

CAMERA_FIRMWARE_VERSION: 2.0.71.09

CAMERA_TYPE : PRQ-Ready

OEM_ID : OEM None

ISP_FW_VERSION : 0xd940

CONTENT_VERSION : 12

MODULE_VERSION : 4.4.0.111

IMAGER_MODEL_NUMBER : 33

CALIBRATION_DATE : 2014-07-04 08:18:35 UTC

EMITTER_TYPE : Laser Driver 4.1

FOCUS_VALUE : 0

LENS_TYPE : Newmax 58.9 x 45.9 degs in VGA

3RD_LENS_TYPE : AEOT

LENS_COATING__TYPE : Visible-light block / IR pass 43 nm width

3RD_LENS_COATING_TYPE: IR coating

NOMINAL_BASELINE : 70 mm

3RD_NOMINAL_BASELINE: 58 mm

Supported options: min max step default

COLOR_BACKLIGHT_COMPENSATION : 0 ... 1 1 0<span class="...

Re: Out of box Euclid build of librealsense fails

Meitav_K_Intel — Sun, 24 Sep 2017 08:35:44 GMT

Fantastic!

I'm seeing that other people do have so issues with the examples as well, so this will require some digging into the code, but I'm glad it works.

Let us know if you need any further help!

Meitav

Intel Euclid Development Team