Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
How to first build and then install into a stage directory?
See original GitHub issueBy default build seems to build the source tarball and wheel.
I work in the context of the FreeBSD port. I need to (1) configure (2) build (3) install into a stage directory.
Using setup tools this is done like this: (1) python setup.py config (2) python setup.py build (3) python setup.py install -record /usr/ports/science/py-xx/work-py39/.PLIST.pymodtmp -c -O1 --prefix=/usr/local --single-version-externally-managed --root=/usr/ports/science/py-xx/work-py39/stage
What are the equivalent commands using build?
We don’t need source tarball and wheel. It should just build and then install into a stage directory.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Pip is a package manager as well as a wheel builder and installer. Build is just a wheel builder. Pip’s package management features are at best redundant and at worst actively get in the way when used by a package manager (or ports system).
I’ve suggested this patch for the FreeBSD ports framework to fully support PEP-517 at the level of individual ports. It is based on build/installer packages.