Unrelated to pep 517, remind me whether when invoking setup.py build -b dir bdist, if the -b argument passed to the build command is supposed to affect the build command run as a subcommand of bdist? Asking for a friend 😸 On Sat, Jul 8, 2017, 11:17 Jeremy Kloth <jeremy.kloth@gmail.com> wrote:
On Fri, Jul 7, 2017 at 9:45 PM, Nick Coghlan <ncoghlan@gmail.com> wrote:
On 7 July 2017 at 23:23, Daniel Holth <dholth@gmail.com> wrote:
FYI distutils supports out of tree builds too. It is the -b argument to 'setup.py build'.
Sort of. That's short for "--bdist-dir" and tells distutils/setuptools not to use the "dist/" subdirectory for either build trees or the build artifacts. It doesn't say anything about where intermediate artifacts generated by compilers etc should end up.
No, Daniel is correct. "setup.py *build* -b" is short for --build-base which is where all build artifacts go, even those from compilers. It seems you are confusing it with "setup.py *bdist* -b" which is indeed short for "--bdist-dir".
-- Jeremy Kloth