Equivalent of "make install" for Python on windows?
Oh right, and another example:
The binary names for debug builds have a _d suffix, but modules like pip (which I assume can only be installed with get-pip.py) expect them not to have this suffix. Once I started copying lots of .exe and .lib files around just to make the distribution work I started to think I was missing something.
> On Jul 10, 2020, at 8:01 AM, Patrick Stinson <patrickkidd at gmail.com> wrote:
> Building python from source on windows is straightforward enough with PCBuild/build.bat. But it seems as though the resulting distribution that runs from these standard build dirs ends up sort of incomplete and/or fragmented - at least for what I am used to on *NIX.
> Binaries are in ./PCBuild/platform instead of ./bin, there is no pip, then get-pip.py installs the pip module but puts the pip script in ./Scripts. And other things?
> Is there some kind of install step that I am missing? It?s fine if this is just a matter of adjusting to a non-standard distribution config, but I have always had the feeling that the distribution doesn?t really work correctly.