Packaging OpenCV with CUDA - Install on Jetson

After spending hours building OpenCV as in the video • OpenCV with CUDA in Py... , wouldn't it be nice to package it as an installer for your NVIDIA Jetson? Full article on JetsonHacks: wp.me/p7ZgI9-3Nm
Here's how to do it! Items in the video:
Jetson Nano Developer Kit: amzn.to/468IM8x
64 GB SD Card: amzn.to/3ujZTY3
Samsung SSD: amzn.to/3QZVqT3
NOTE: If you use the cp command to save or copy your build products, make sure to keep the same time stamps. For example:
$ cp -r --preserve=timestamps build_opencv /path/to/destination
This is for all Jetsons, including the Jetson Nano, Jetson Xavier, and Jetson Orin series.
00:00 Introduction
00:13 Saving Build Artifacts
01:21 Restoring Build Artifacts
01:44 Simple make install
03:15 Build Package - First method
04:30 Build Package - Command Line Copy Method
07:03 Install Package
08:49 Resolving Runtime Dependencies
As an Amazon Associate I earn from qualifying purchases.
Visit the JetsonHacks storefront on Amazon: www.amazon.com/shop/jetsonhacks
Visit the website at jetsonhacks.com
Sign up for the newsletter! newsletter.jetsonhacks.com
Github accounts: github.com/jetsonhacks
github.com/jetsonhacksnano
Twitter: / jetsonhacks
Some of these links here are affiliate links. As an Amazon Associate I earn from qualifying purchases at no extra cost to you.

[@vuxuanhai7311]

Thanks a bunch! I'm curious about the distinctions among the OpenCV packaging types with CUDA. You shared three, each employing different approaches. Can you elaborate on the differences?

[@JetsonHacks]

You are welcome. The first is the shell script, the package install shown in the video. The shell script is a convenience wrapper with code to install the included library and support files. The user doesn't need to know much about the contents, and it makes it easier to install to places such as /usr/local or .local . People install into .local if they only want the current user to have access to it.
The second is a .tar.gz file. This is simply the library and support files organized into the typical installation directories. It's compressed (the .gz part). The idea there is you can simply decompress and untar it into the location you prefer directly from the command line or your own script.
The .tar.Z file is similar to the .tar.gz file but uses a different compression method. This uses the 'compress' utility for compression. It's a little bit older.
Hope this helps, and thanks for watching!

[@surflaweb]

Can I do the same for jetson orin nano?

[@JetsonHacks]

Yes. Thanks for watching!

[@surflaweb]

@@JetsonHacks thanks

[@jeffg4686]

We need Jetson VR/AR

[@JetsonHacks]

That's a good point! Thanks for watching!