This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author Valentin Zhao
Recipients Valentin Zhao, paul.moore, steve.dower, tim.golden, zach.ware
Date 2018-09-12.03:42:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1536723765.14.0.956365154283.issue34643@psf.upfronthosting.co.za>
In-reply-to
Content
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.
History
Date User Action Args
2018-09-12 03:42:45Valentin Zhaosetrecipients: + Valentin Zhao, paul.moore, tim.golden, zach.ware, steve.dower
2018-09-12 03:42:45Valentin Zhaosetmessageid: <1536723765.14.0.956365154283.issue34643@psf.upfronthosting.co.za>
2018-09-12 03:42:44Valentin Zhaolinkissue34643 messages
2018-09-12 03:42:44Valentin Zhaocreate