You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The make install target currently executes pip install -e . (editable install). This makes sense for development purposes, but it differs from the normal expectations of a make install. Typically, make install copies the executable to /usr/local, thus making it available across the system for the user.
In our case, we are creating a Python package. Therefore, it doesn't make sense to copy anything to /usr/local but the analogous situation would be installing the library across the Python environment. Both editable and static installs accomplish this goal but have slightly different use cases.
To maintain some level of conventional behavior for make install, I suggest modifying make install to install the static wheel output from make build. Then, add make dev to execute pip install -e ..
The text was updated successfully, but these errors were encountered:
...continuation of #60
The
make install
target currently executespip install -e .
(editable install). This makes sense for development purposes, but it differs from the normal expectations of amake install
. Typically,make install
copies the executable to/usr/local
, thus making it available across the system for the user.In our case, we are creating a Python package. Therefore, it doesn't make sense to copy anything to
/usr/local
but the analogous situation would be installing the library across the Python environment. Both editable and static installs accomplish this goal but have slightly different use cases.To maintain some level of conventional behavior for
make install
, I suggest modifyingmake install
to install the static wheel output frommake build
. Then, addmake dev
to executepip install -e .
.The text was updated successfully, but these errors were encountered: