Add Qt4 and GLEW dependencies to Jetson environment

[jwatte]

A freshly flashed Jetpack 3 Jetson TX2 does not have QT4 or GLEW, which are needed for jetson-inference to actually build.
(Well, at least mine didn't :-)

[jwatte]

I now see that the CMakePreBuild.sh script would install those dependencies.
The script says it's run automatically by cmake, but on my machine it wasn't.
An alternative to merging this commit would be to update the README to say to run the script manually.

[dusty-nv]

These are installed by CMakePreBuild script, https://github.com/dusty-nv/jetson-inference/blob/master/CMakePreBuild.sh It should have been automatically run by cmake.  You could rm build and try again, or try running the steps in the script manually. In particular qt4-dev and glew packages are installed near the beginning.

On May 20, 2017 12:38 PM, Jon Watte ***@***.***> wrote: A freshly flashed Jetpack 3 Jetson TX2 does not have QT4 or GLEW, which are needed for jetson-inference to actually build. (Well, at least mine didn't :-) ________________________________ You can view, comment on, or merge this pull request online at:   #80 Commit Summary Add Qt4 and GLEW dependencies to Jetson environment File Changes M README.md (4) Patch Links: https://github.com/dusty-nv/jetson-inference/pull/80.patch https://github.com/dusty-nv/jetson-inference/pull/80.diff — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------

[jwatte]

And the REAL problem turned out to be that the CMakePreBuild.sh script hard-codes the relative path for output directories to "../data/networks"
My build artifacts do not live in jetson-inference/build, but instead live outside the source directory, and thus the hard-coded path did not work.
The script should probably "set -e" to fail early when things don't work, rather than just blithely go on and not cause setup errors in this case.

[dusty-nv]

Aha thank you, I will have to consider this issue with the paths. Additionally you could use 'make install' for the aarch64 package and set the install paths in CMakeLists. On May 20, 2017 1:11 PM, Jon Watte <notifications@github.com> wrote: And the REAL problem turned out to be that the CMakePreBuild.sh script hard-codes the relative path for output directories to "../data/networks" My build artifacts do not live in jetson-inference/build, but instead live outside the source directory, and thus the hard-coded path did not work. The script should probably "set -e" to fail early when things don't work, rather than just blithely go on and not cause setup errors in this case. — You are receiving this because you commented. Reply to this email directly, view it on GitHub<#80 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AOpDK6GHgKXFQJDA6Sy-IiSR1Y0BIUmqks5r7x67gaJpZM4NhWQ6>.

…

----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. -----------------------------------------------------------------------------------