-
Notifications
You must be signed in to change notification settings - Fork 644
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
[Fix] fix ncnn #187
[Fix] fix ncnn #187
Conversation
Codecov Report
@@ Coverage Diff @@
## master #187 +/- ##
=======================================
Coverage 66.98% 66.98%
=======================================
Files 189 189
Lines 6176 6176
Branches 955 955
=======================================
Hits 4137 4137
Misses 1746 1746
Partials 293 293
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
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.
LGTM.
set(_NCNN_EXT_DIR ${CMAKE_SOURCE_DIR}/mmdeploy/backend/ncnn) | ||
set_target_properties(ncnn_ext PROPERTIES | ||
LIBRARY_OUTPUT_DIRECTORY ${_NCNN_EXT_DIR} | ||
LIBRARY_OUTPUT_DIRECTORY_DEBUG ${_NCNN_EXT_DIR} |
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.
Are both LIBRARY_OUTPUT_DIRECTORY_DEBUG
and LIBRARY_OUTPUT_DIRECTORY_RELEASE
properties necessary?
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.
On MSVC, the path to the target will contain "Debug" or "Release" otherwise.
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.
LGTM
* remove albu version limit * fix lint
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily receiving feedbacks. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
ncnn was not taken into consideration in #106, this PR tries to bring it back.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward-compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist