-
Notifications
You must be signed in to change notification settings - Fork 70
Building fuser project
jjsjann123 edited this page Mar 31, 2023
·
17 revisions
Build issue is tracked here: https://github.com/NVIDIA/Fuser/issues/101. If you run into problems, open an issue and link it against that.
- clone pytorch code base to your local machine. https://github.com/pytorch/pytorch (we do nightly build against pytorch upstream.
viable/strictbranch is recommended for stable CI.) - clone fuser code base to your local machine. https://github.com/NVIDIA/Fuser (default to
main, which is our development branch) - Build pytorch from the
[PATH_TO_PYTORCH], with one environment variableexport NVFUSER_SOURCE_DIR=[PATH_TO_FUSER]to use the latest fuser code base, replacing the submodule fuser code that's shipped with pytorch under[PATH_TO_PYTORCH]/third_party/nvfuser.
- Install pytorch (either from source or via pip wheel);
- clone fuser code to your local machine
https://github.com/NVIDIA/Fuser; - Update nvfuser submodule:
git submodule sync --recursive; git submodule update --init --recursive; - Install required pip modules:
pip install -r requirements.txt; - Build nvfuser with
python setup.py develop;
A few note on pytorch standalone build:
- nightly pip from pytorch currently doesn't work for our cpp tests: https://github.com/pytorch/pytorch/issues/98093
- there was some packaging issue with pytorch that has been patched (https://github.com/pytorch/pytorch/pull/97404), So as of today 3/31/2023, nightly pip wheel should work, but pytorch 2.0 pip wheel doesn't.
For PRs changing build system. We kindly ask you to verify it in all three uses:
- submodule build;
- standalone build against your locally build
pytorch; - [somewhat optional] standalone build against a pip installed
pytorch; (note that since upstream pip package has issues, you might want to build a pip wheel locally and use that instead)