Skip to content

Commit

Permalink
Recommendations for workflow when modifying C files. (pytorch#1443)
Browse files Browse the repository at this point in the history
Signed-off-by: Edward Z. Yang <[email protected]>
  • Loading branch information
ezyang authored and soumith committed May 2, 2017
1 parent aa2ee86 commit fb07914
Showing 1 changed file with 10 additions and 0 deletions.
10 changes: 10 additions & 0 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,6 +70,16 @@ For example:

You do not need to repeatedly install after modifying python files.

If you are working on C files, you will need to build your changes:

```
(rm -rf build; python setup.py develop)
```

We recommend removing the `build` directory before rebuilding because
setup.py's recompilation checking is not great, and it will often fail
to rebuild C code after you modify code in a `generic` directory.

#### C++ Development tips

When you are developing on the C++ side of things, the environment variables `DEBUG` and `NO_CUDA` are helpful.
Expand Down

0 comments on commit fb07914

Please sign in to comment.