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

Update CMakeLists to allow Jetson container build #89

Closed
wants to merge 6 commits into from

Conversation

dyastremsky
Copy link
Contributor

The l4t Jetson containers store TensorFlow files in a different location. This pull request allows the user to pass a Jetson build flag to allow the build to look for files in the TensorFlow location on l4t.

CMakeLists.txt Outdated Show resolved Hide resolved
CMakeLists.txt Outdated Show resolved Hide resolved
tanmayv25
tanmayv25 previously approved these changes Apr 12, 2023
@dyastremsky
Copy link
Contributor Author

Requesting reapproval due to rebasing.

@@ -33,6 +33,8 @@ project(tritontensorflowbackend LANGUAGES C CXX)
#
option(TRITON_ENABLE_GPU "Enable GPU support in backend." ON)
option(TRITON_ENABLE_STATS "Include statistics collections in backend." ON)
option(TRITON_JETSON_BUILD "Build for Jetson. " OFF)
option(TRITON_TENSORFLOW_LICENSE_AVAILABLE "Whether the TensorFlow license is available in this build. " ON)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be an option. We should always include the license to comply with Apache 2.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please see the conversations here for the context of why this is here: #89 (comment) and #89 (comment).

I'm not sure what a good alternative would be. Since it's not included in the l4t containers as far as I know, we could probably clone it from elsewhere like GitHub if that's acceptable.

@dyastremsky
Copy link
Contributor Author

Closing this PR. It looks like we no longer need it. Right now, we use the --no-container-build inside a Jetson container to produce the Jetson Docker containers. If we shift to using a container-build directly, we can reference this PR, as these changes will be needed for that build.

@dyastremsky dyastremsky closed this May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants