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

Python CMakeExtension #14

Merged
merged 8 commits into from
Apr 23, 2022
Merged

Python CMakeExtension #14

merged 8 commits into from
Apr 23, 2022

Conversation

rusty1s
Copy link
Member

@rusty1s rusty1s commented Apr 22, 2022

Allows cmake build via pip install .

setup.py Show resolved Hide resolved
setup.py Show resolved Hide resolved
@@ -36,5 +87,7 @@
'dev': dev_requires,
},
packages=find_packages(),
ext_modules=[CMakeExtension('libpyg')],
Copy link
Member

@ZenoTan ZenoTan Apr 22, 2022

Choose a reason for hiding this comment

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

A little confused about naming it libpyg ('lib' as library prefix) but in python having torch.ops.pyg, and folder name pyg_lib. Is there a way to make them look consistent or specify them in doc?

Copy link
Member Author

Choose a reason for hiding this comment

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

I currently do not see an easy way to do this.

  • lib*.so is the standard naming of libraries
  • pyg is the namespace
  • pyg_lib is the Python package name.

I added a TODO here which we can look into later. Hope that works for you :)

@rusty1s rusty1s merged commit e354bbe into master Apr 23, 2022
@rusty1s rusty1s deleted the python_build branch April 23, 2022 05:16
@rusty1s rusty1s mentioned this pull request Apr 25, 2022
12 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants