Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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:
tritonfrontend
support for no/partial endpoint builds #7605build:
tritonfrontend
support for no/partial endpoint builds #7605Changes from 14 commits
59d9aa8
0b66a27
173216e
c9fa783
384da14
40da2be
f08de59
f3fc425
a657cae
be36c42
80ee6e5
723df84
48acc3e
c6efa9e
2932600
85d7676
8f0b4e1
07ccbc6
2ac6874
ace4528
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't understand this part, if not supported, then why introducing the dependency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently, when building through
build.py
orcmake
, tracing can be enabled in the build. From my understanding, this means thattracing-library
(tracer.h
) will get built with the#ifdef TRITON_ENABLE_TRACING
sections included. Hence, whenhttp-endpoint-library
orgrpc-endpoint-library
includetracer.h
(here and here) it will look for the tracing dependencies thattracer.h
requires.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then shouldn't
tracing-library
be added ashttp-endpoint-library
/grpc-endpoint-library
's dependencies?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this would be a good change. Currently instead of linking the
tracing-library
, we do something along the lines of:http_server.h
and in CMakeList.txt to handle the dependencies we do:
But now that we are changing the
tracing-library
links/includes to be public, I replaced:with this:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With assistance from @fpetrini15, I was able to verify that these changes work with the windows build as well.
CI Pipeline ID: 19374177
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that these libs are exposed publicly by the
tracing-library
that is already linked to thepy-bindings
target, do we need to do it again here?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without linking and including these libraries/directories to
py-bindings
, the build fail which points to thesrc/CMakeLists.txt
linking change fromPRIVATE
toPUBLIC
not having the intended consequence. Hence, will revert thesrc/CMakeLists.txt
level changes and keep these link/include operations.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But how can
main
target don't need handling like this? Isn'tmain
andpy-bindings
conceptually the same in terms of compilation and linking?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the suggestion. The new handling of
tracing-library
requires only linkingpy-bindings
totracing-library
without including/linking anyopentelemetry
directories or libraries directly topy-bindings
.The fix was to link tracing-library "as is" and not link
$<TARGET_OBJECTS:tracing-library>
because linking the latter will not propagate the link interface of tracing-library when linked with the final library.