windows maskrcnn error: unresolved external symbol "class at::Tensor __cdecl nms_cpu(class at::Tensor const &,class at::Tensor const &,float)" (?nms_cpu@@YA?AVTensor@at@@AEBV12@0M@Z)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 17.9k
- Forks
- 7.3k
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 13
Description
I built torchvision pulled from master using :
cmake -DCMAKE_PREFIX_PATH=D:/Garage/onnx-deploy/libtorchd -DCMAKE_INSTALL_PREFIX=D:/vision/Debug -DCMAKE_BUILD_TYPE=Debug ..
cmake --build . --config Debug
cmake --install .
Then torch.jit.script(model) and saved mask-rcnn model from torchvision.
Errors occured in my C++ project, firstly Unknown builtin op: torchvision::_new_empty_tensor_op, then I modified my code according to #1407, added lines like #include "torchvision/nms.h" and torch::RegisterOperators().op("torchvision::nms", &nms) , but it won't work.
The error became unresolved external symbol "class at::Tensor __cdecl nms_cpu(class at::Tensor const &,class at::Tensor const &,float)" (?nms_cpu@@YA?AVTensor@at@@AEBV12@0M@Z).
The libtorch version is 1.5.0 and torchvision is pulled from master yesterday.
Any clue how I can get mask rcnn running? Similar issues are many but little to help, I really get confused about how to modify CMakeList.txt of TorchVision.
cc @peterjc123 @nbcsm @guyang3532 @maxluk @gunandrose4u @smartcat2010 @mszhanyi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the reported Windows CMake configure/build commands and inspect the TorchVision CMakeLists.txt and torchvision/nms.h registration path. Reproduce the unresolved nms_cpu linker error in the C++ project using the stated libtorch 1.5.0 and TorchVision master versions. Done means the scripted Mask R-CNN model can run without the missing operator or linker error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cmake, cpp, python
- Domain
- build-system, computer-vision
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100