[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: Still relevant, but the current patch is overkill (Brian was right, it's just way more batch than is healthy to check in). Things are changing rapidly, though; I'll close it as "postponed" for now, with the expectation of reopening someday. -- assignee

[issue16895] Batch file to mimic 'make' on Windows

Changes by Brian Curtin : -- nosy: -brian.curtin ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue16895] Batch file to mimic 'make' on Windows

Mark Lawrence added the comment: Is this still relevant or has it been overtaken by other work from Zach or Steve? -- nosy: +BreamoreBoy, steve.dower versions: +Python 3.5 -Python 3.4 ___ Python tracker __

[issue16895] Batch file to mimic 'make' on Windows

Changes by Jeremy Kloth : -- nosy: +jkloth ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.python.

[issue16895] Batch file to mimic 'make' on Windows

Changes by Mark Lawrence : -- nosy: -BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail.

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: > Brian Curtin added the comment: > > Don't we already require an existing Python to build some of the third-party > stuff, e.g., OpenSSL? Only for building a 64-bit Python on 32-bit Windows. Otherwise, OpenSSL is built using the just-built interpreter. > I don

[issue16895] Batch file to mimic 'make' on Windows

Brian Curtin added the comment: Don't we already require an existing Python to build some of the third-party stuff, e.g., OpenSSL? I don't think the bootstrapping issue holds that much weight. Adding some huge batch script that maybe one or two people even know how to modify is a much higher

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: > Richard Oudkerk added the comment: > > I can't say I know enough about batch files to understand much of the code, > but a few notes: > > Windows XP does not have the command "where" which you use -- Python 3.4 will > still support XP. Oh, that is an issue. I

[issue16895] Batch file to mimic 'make' on Windows

Richard Oudkerk added the comment: > Can't this just be a Python script? That would cause bootstrap issues for people who do not already have python installed. -- ___ Python tracker __

[issue16895] Batch file to mimic 'make' on Windows

Brian Curtin added the comment: Can't this just be a Python script? -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubs

[issue16895] Batch file to mimic 'make' on Windows

Richard Oudkerk added the comment: I can't say I know enough about batch files to understand much of the code, but a few notes: Windows XP does not have the command "where" which you use -- Python 3.4 will still support XP. Except perhaps for looping I would prefer to get rid of the use of go

[issue16895] Batch file to mimic 'make' on Windows

Changes by Mark Lawrence : -- nosy: +BreamoreBoy ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: http://mail.py

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: Here's a new version of the patch, which is a major rewrite. Among the changes: - Switch from using 'goto' to execute the right subroutine to 'call' and end every subroutine with 'exit /B' (thank you Richard for making me aware of that possibility). This makes

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: > You seem to end your subroutines (or whatever they are called) using "goto > end" rather than "exit /b". Since popd follows the "end" label, does this > mean that you get a popd after calling each subroutine? Yes. > Is this intended and can it cause unmatche

[issue16895] Batch file to mimic 'make' on Windows

Richard Oudkerk added the comment: You seem to end your subroutines (or whatever they are called) using "goto end" rather than "exit /b". Since popd follows the "end" label, does this mean that you get a popd after calling each subroutine? Is this intended and can it cause unmatched pushd/po

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: I was rather off about kill_python, wasn't I? Anyway, I've finally gotten another version put together that I'd like to get comments on. Major differences between this patch and the previous one, in no particular order: - Add a 'configure.bat' script to increa

[issue16895] Batch file to mimic 'make' on Windows

Terry J. Reedy added the comment: Thanks, clean and kill make sense for unattended build-bots. For interactive use, when 2 minutes rebuilding is a big deal, clean is a last resort. Let's just make sure we do not somehow suggest that it needs to be done routinely. Or to put it another way, do d

[issue16895] Batch file to mimic 'make' on Windows

Richard Oudkerk added the comment: > What does running 'kill-python before re-building python do? I have not > seen it mentioned in the in the devguide or pcbuild/readme. It kills any currently running python(_d).exe processes. This is because Windows does not allow program or library files t

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: >Terry J. Reedy added the comment: > >One must run external.bat if one is to subsequently build from the vs >gui with *most* of the external dependencies. I think the command to >run it should be 'external', not 'ready'. 'External' means get the >external dependenc

[issue16895] Batch file to mimic 'make' on Windows

Terry J. Reedy added the comment: One must run external.bat if one is to subsequently build from the vs gui with *most* of the external dependencies. I think the command to run it should be 'external', not 'ready'. 'External' means get the external dependencies and anyone who has run external.

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: > Richard Oudkerk added the comment: > > +1 Thank you :) > To use Tools/builbot/*.bat doesn't the current directory have to be the main > directory of the repository? Then I see no point in the "-C" argument: just > set the correct directory automatically. Tha

[issue16895] Batch file to mimic 'make' on Windows

Richard Oudkerk added the comment: +1 To use Tools/builbot/*.bat doesn't the current directory have to be the main directory of the repository? Then I see no point in the "-C" argument: just set the correct directory automatically. I think make.bat should also support creation of non-debug b

[issue16895] Batch file to mimic 'make' on Windows

Zachary Ware added the comment: Here's an updated version in the form of a patch. Features include: - Ensure things are done in the right directory with pushd/popd - Allow setting environment variables (for the life of the script) with: make test "PYTHON=..\PCbuild\python.exe" - Emulate

[issue16895] Batch file to mimic 'make' on Windows

Terry J. Reedy added the comment: +1 Add make external[-64] to runs Tools/buildbot/external[-amd64].bat and explain this in the devguide (if not already) rather than buried in the opaque PCBuild/readme. Even after reading build.bat, I do not understand what is the different net effect of that

[issue16895] Batch file to mimic 'make' on Windows

New submission from Zachary Ware: I find myself frustrated with some of the hoops I have to jump through and extra things I have to remember when I want to play around with Python on Windows. To make things a little easier, I've created a 'make.bat' file that can sit in the root of the reposi