How to set up the build environment

[marbx]

I try to set up and document the build environment (for Python 3)

Related: #1487

This is a rewrite of https://wiki.python.org/moin/WindowsCompilers

Install Microsoft Visual C++ compiler for Python 3.5, 3.6, 3.7, 3.8

Microsoft Visual C++ 14.2 is in Visual Studio 2019

• Download the Installer for Visual Studio 2019 (~ 1 MB)

• In the installer:

  • Check C++ build tools
    • In the menue to the right, check:
      • MSVCv142 - VS 2019 C++ x64/x86 build tools
      • Windows 10 SDK
      • C++ MFC for latest v142 build tools (automatically ticks C++ ATL)
        • Note: The installer does not contain MFC for v140
    • Press Install (~ 5 GB)

• Restart

• Include the "Microsoft (R) Message Compiler" into the path

  • Search

    dir /b /s mc.exe

  • and set (example)

    set "path=%path%;c:\Program Files (x86)\Windows Kits\10\bin\10.0.18362.0\x64"

• Run

  python setup.py -q build

Error

RuntimeError: No MFC files found!

What am I missing/doing wrong?

Thank you

[marbx]

Error solved

MFC v140 is in Build Tools for Visual Studio 2017 (version 15.9), available at https://my.visualstudio.com.

The devblog explains (see Screenshot!)

The Visual C++ build tools workload in the Visual Studio Build Tools will install the latest v141 toolset from VS2017 by default. The v140 toolset from VS2015 will install side-by-side with the v141 toolset. To install them just select the “VC++ 2015.3 v140 toolset for desktop (x86,x64)” at the bottom of the “Optional” section.

[marbx]

Question:

• Why do I need to include mc in the path?

[mhammond]

* Why do I need to include mc in the path?

mc is used in the build to embed message resources in a few of the built files. Is that what you are asking?

[marbx]

No, I don't question the reason for mc. Looks like an interesting technology.

I wanted confirmation that amending the path environment variable on its own completes the pywin32 build environment, and that I don't miss steps which include amending the path.

Thank you, I will create a pull request for a markdown document.

[vernondcole]

Markus: Thank you! Good work on the document. Dear Group: I have been attempting on-and-off for several years to build a working pywin32 build machine. I have never (yet) succeeded, but the project has floated back to the top of my personal to-do list. This time, I am writing a script to create an entire build-and-test assembly, so that I will never again have to submit an untested pull request. When complete, this script is intended to be able to set up a build machine suitable for our CI/CD, or for anyone who wants to be able to set up a build system with a few typed (or cut-and paste) lines of command. None of the pull-down-this-and-click-that kind of thing, so it will work on virtual machines in a headless environment. The deployment tool I have selected is Salt, <https://docs.saltstack.com> which operates well on Windows, partly because it is written in Python using pywin32. I am adding the necessary scripts to a Salt demonstration system (salt-bevy <https://github.com/salt-bevy/salt-bevy>) which I maintain, which already has most of the tools needed. The first baby steps are in the pywin32_test_environment <https://github.com/salt-bevy/salt-bevy/tree/pywin32_test_environment> branch. Consider this to be an announcement, and a request for frequent help. When I hit each road block (the first of which I expect a few hours hence) I will post a new thread on this forum. With help from all of you, each road block will be solved in turn. -- Vernon Cole

…

On Sun, Mar 22, 2020 at 4:09 AM Markus ***@***.***> wrote: No, I don't question the reason for mc. Looks like an interesting technology. I wanted confirmation that amending the path environment variable on its own completes the pywin32 build environment, and that I don't miss steps which include amending the path. Thank you, I will create a pull request for a markdown document. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1489 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEZOBOEMR2KKUOCECA3TELRIXPUZANCNFSM4LQ5M7CA> .

[marbx]

Hi @vernondcole, isn't that funny: I come to pywin32 because Salt uses it.

In particular, I would like to propose a headless distribution variant of pywin32, which fits even better into Salt.

I was also wondering how to test pywin32, so I can use the bevy, very handy.

[marbx]

@vernondcole, I have repeated the install on a second PC, so I have confidence in the "pull-down-this-and-click-that" description of the setup.

As you are aware, Salt uses pywin32.

I would like to build a pywin32 variant without MFC. This would exclude Pythonwin and Scintilla, and all other GUI elements, because Salt does not require, and therefore should not contain MFC.

I can ran python setup.py -q build.

Could you give me an advise how to proceed?