Skip to content

Fix Windows build by renaming Python init functions #1779

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

Merged
merged 1 commit into from
Jan 22, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions torchvision/csrc/vision.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -14,18 +14,18 @@
#include "nms.h"

// If we are in a Windows environment, we need to define
// initialization functions for the _custom_ops extension
// initialization functions for the _C extension
#ifdef _WIN32
#if PY_MAJOR_VERSION < 3
PyMODINIT_FUNC init_custom_ops(void) {
PyMODINIT_FUNC init_C(void) {
// No need to do anything.
// _custom_ops.py will run on load
// extension.py will run on load
return NULL;
}
#else
PyMODINIT_FUNC PyInit__custom_ops(void) {
PyMODINIT_FUNC PyInit__C(void) {
// No need to do anything.
// _custom_ops.py will run on load
// extension.py will run on load
return NULL;
}
#endif
Expand Down