Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build configuration options used in official PPA builds #5618

Closed
WasabiFan opened this issue Jan 10, 2020 · 12 comments
Closed

Build configuration options used in official PPA builds #5618

WasabiFan opened this issue Jan 10, 2020 · 12 comments

Comments

@WasabiFan
Copy link
Contributor

Required Info
Camera Model N/A
Firmware Version N/A
Operating System & Version Ubuntu 18.04 arm64
Kernel Version (Linux Only) N/A
Platform Nvidia Jetson Xavier
SDK Version All
Language All
Segment N/A

Issue Description

What CMake flags are used when building each of the .deb packages at http://realsense-hw-public.s3.amazonaws.com/Debian/apt-repo? Where can I find them?

In particular, this page (https://github.com/IntelRealSense/librealsense/blob/master/doc/installation_jetson.md) suggests at the bottom building with FORCE_LIBUVC=true and BUILD_WITH_CUDA=true if building from source. But up above it recommends using the prebuilt packages. So are builds for this architecture built with those flags? Or is the page not internally consistent?

@ev-mp
Copy link
Collaborator

ev-mp commented Jan 12, 2020

@WasabiFan hello, the Debian packages for Arm64 are Jetson-optimized, i.e. built with FORCE_LIBUVC=true and BUILD_WITH_CUDA=true as recommended.

@WasabiFan
Copy link
Contributor Author

Thanks!

@WasabiFan WasabiFan reopened this Jan 15, 2020
@WasabiFan
Copy link
Contributor Author

@ev-mp It looks like that build configuration doesn't include the Python wrapper. The wheels published on PyPi don't include arm64 builds. How am I supposed to install the Python wrapper?

@ev-mp
Copy link
Collaborator

ev-mp commented Jan 15, 2020

That's correct, currently the pip install packages are generated for X86/X64 architecture only.
For Arm64 you need to build the python wrapper using the installation guide

@WasabiFan
Copy link
Contributor Author

The issue is that you can't build the Python wrapper without building all of librealsense, as far as I can tell. So the pre-built packages are only useful if you're writing in C++ — if you want to write in Python or another language, you have to compile from source anyway, right?

Can you provide or point me to the exact script and build options that are used for official builds so I can replicate it as closely as possible?

@ev-mp
Copy link
Collaborator

ev-mp commented Jan 16, 2020

The rule used to configure the SDK for Jetson debians is :

override_dh_auto_configure: dh_auto_configure -- -DBUILD_EXAMPLES=true -DCMAKE_BUILD_TYPE=release -DBUILD_WITH_CUDA:BOOL=ON -DFORCE_RSUSB_BACKEND:BOOL=ON

@RealSenseCustomerSupport
Copy link
Collaborator


Hi @WasabiFan,

Has the comment provided by @ev-mp helped to find an answer to your question? Please let us know if you need any further assistance with this matter.

Thank you!

@WasabiFan
Copy link
Contributor Author

It was helpful. @ev-mp where can this information be found publicly? Can you publish the official build scripts?

@ev-mp
Copy link
Collaborator

ev-mp commented Feb 4, 2020

@WasabiFan, as for the inquiry -
while currently it is not in the public domain upstreaming the SDK debian distribution is one of the established team's goals, which in turn will automatically open-source the repositories.
Unfortunately I cannot elaborate on scheduling.

@RealSenseCustomerSupport
Copy link
Collaborator


@WasabiFan,

Do you need any additional clarifications regarding this topic?

@WasabiFan
Copy link
Contributor Author

I don't need clarification, but this issue should presumably stay open until the build script configurations are publicly available.

@RealSenseSupport
Copy link
Collaborator

@WasabiFan

If no further clarifications are needed, this thread will be closed since we already have an open issue where updates about the progress on "making build script configurations publicly available" will be published: #4431

Please don't hesitate to open a new thread if you have additional questions!
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants