That does help, thanks so much for the fast response! I now see how it's executed on Azure pipelines also, so that should be enough for me to reverse engineer the rest.
Followup questions if you have time: 1. It seems that directory doesn't exist in the 3.6 branches/tags, so it must have been done a different way back then. Do you think it's back-portable to 3.6? 2. One of our objectives is to effectively create a nearly identical embeddable package for linux. Do you think the layout code is generic enough to be modified to create a linux equivalent? Obviously, there are many alternative methods and documents for creating "embeddable" pythons on linux, but the windows package has all the characteristics we want, and of course we'd like our Windows and Linux process build and packaging processes to be as similar as possible, so it seems attractive to try to port this layout script to linux. Gerald R. Wiltse jerrywil...@gmail.com On Wed, May 1, 2019 at 12:22 PM Steve Dower <steve.do...@python.org> wrote: > On 01May2019 1109, Gerald Wiltse wrote: > > I looked through all the windows builders here and could not find any > > which generate this package, can anyone tell me where the work happens? > > I also tried searching looking for scripts and CI files which create the > > package in all the relevant repos and could not find those either. > > > > Is this information not public? > > It's just not obviously documented (yet). We use the "PC/layout" script > (run as "python PC/layout -h" to get arguments). You'll want at least > --preset-embed and either --copy or --zip to specify where the layout is > created. > > > Is it a manual build? > > It's semi-automated, but it's only triggered for releases and so it's > not part of the normal CI configuration. > > Hope that helps, > Steve >
_______________________________________________ Python-Dev mailing list Python-Dev@python.org https://mail.python.org/mailman/listinfo/python-dev Unsubscribe: https://mail.python.org/mailman/options/python-dev/archive%40mail-archive.com
