| msg57690 - (view) |
Author: Christian Heimes (christian.heimes) *  |
Date: 2007-11-20 03:28 |
| I've created a small bat files that mimics the Makefile in Docs/. It may be useful for some Windows users. |
|
|
| msg57692 - (view) |
Author: Martin v. Löwis (loewis) * |
Date: 2007-11-20 03:59 |
| See also Tools/buildbot/buildmsi.bat. With cygwin installed, building the documentation is as simple as bash.exe -c 'cd Doc;make PYTHON=python2.5 update htmlhelp' "%ProgramFiles%\HTML Help Workshop\hhc.exe" Doc\build\htmlhelp\pydoc.hhp |
|
|
| msg59264 - (view) |
Author: Joseph Armbruster (JosephArmbruster) |
Date: 2008-01-04 22:31 |
| I tested this out out in the trunk (59706). Placed builddoc.bat in /Doc and ran the following commands: builddoc checkout builddoc html builddoc htmlhelp builddoc web All appeared to work fine on my system. |
|
|
| msg59682 - (view) |
Author: Amaury Forgeot d'Arc (amaury.forgeotdarc) * |
Date: 2008-01-10 22:05 |
| This batch file is a good idea. I have two remarks: - it assumes that the python program is spelled "python25". This could be configurable. Something along: IF "%PYTHON%"=="" SET PYTHON=python25 Or is there a better way? - Also, I suggest to insert a SETLOCAL command on the second line of the script, so that the variables set in the script are restored at the end. |
|
|
| msg59714 - (view) |
Author: Joseph Armbruster (JosephArmbruster) |
Date: 2008-01-11 15:07 |
| Is referencing the built python binary in the build tree a good idea? Just in case they do not have python installed on the system already? |
|
|
| msg59717 - (view) |
Author: Christian Heimes (christian.heimes) * |
Date: 2008-01-11 15:17 |
| Joseph Armbruster wrote: > Is referencing the built python binary in the build tree a good idea? > Just in case they do not have python installed on the system already? The doc builder requires Python 2.5 and *may* work with 2.6 but definitely not with 3.x. |
|
|
| msg59718 - (view) |
Author: Joseph Armbruster (JosephArmbruster) |
Date: 2008-01-11 15:20 |
| Ah, good to know :-) |
|
|
| msg59721 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2008-01-11 17:09 |
| Christian Heimes schrieb: > Christian Heimes added the comment: > > Joseph Armbruster wrote: >> Is referencing the built python binary in the build tree a good idea? >> Just in case they do not have python installed on the system already? > > The doc builder requires Python 2.5 and *may* work with 2.6 but > definitely not with 3.x. It should work with 2.6 without problems. 3k compatibility is another story, of course :) |
|
|
| msg59733 - (view) |
Author: Joseph Armbruster (JosephArmbruster) |
Date: 2008-01-11 18:27 |
| Which brings up a question. Would all things in the tree ideally work with the version that was built from checkout? Just in case something like this comes up in the future, i'd want to know if it is better to have it configured as this or to auto-magically point to the "right place" in the build tree for the python binary. Curiosity more than anything. |
|
|
| msg59820 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2008-01-12 13:59 |
| Ideally, yes. The case of the doc build is a bit more complicated because it relies on external libraries which may or may not work with the tree version. |
|
|
| msg59826 - (view) |
Author: Martin v. Löwis (loewis) * |
Date: 2008-01-12 17:06 |
| > Would all things in the tree ideally work > with the version that was built from checkout? It's more important that it works with many old versions, than with its own version. "python" should be on the path, and ideally, whatever you get there should work. The documentation, unfortunately, requires 2.5 as a minimum. It should stay that way for a long time, so that at some point, it works with whatever people typically have on their machines. |
|
|
| msg59856 - (view) |
Author: Georg Brandl (georg.brandl) * |
Date: 2008-01-13 16:32 |
| FTR, I'm currently removing all 2.5isms from Sphinx. |
|
|
| msg60088 - (view) |
Author: Christian Heimes (christian.heimes) * |
Date: 2008-01-18 12:00 |
| I've implemented Amaury's suggestions and also added a call to hhc.exe if the target is htmlhelp. The files was added in r60048 |
|
|