New submission from Valentin Zhao <jmsq...@gmail.com>: I am going to build a Python.exe to migrate it to another PC, in order to build a seemingly virtual *environment* of Python which could run python files. What I do to implement this is to *COPY* \win32 folder to another pc then execute python.exe with specific python file path tagged along.
For now, it works well, however, I met with a strange problem that I cannot find *tcl* under current file hierarchy and this library is generated very deeply so I have to extract it to the root directory manually. Surprisingly, I found that I can directly *COPY* all the folders generated by *msi installer* to another pc then use it. Nevertheless, I fret about there could be some registration thing during installation. So how could I compile the source and make it generate folder hierarchy like the release version(like the snapshot I attached below)? I have read README.md in the \PCBuild yet it helps little. ---------- components: Windows files: build后结构.png messages: 325116 nosy: Valentin Zhao, paul.moore, steve.dower, tim.golden, zach.ware priority: normal severity: normal status: open title: How to build Release Version of Python in Windows? type: compile error versions: Python 3.6 Added file: https://bugs.python.org/file47797/build后结构.png _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue34643> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
