Rev 52: Build in-place before we build for installing. in http://bazaar.launchpad.net/~bzr/bzr-windows-installers/trunk

[John Arbash Meinel]

At http://bazaar.launchpad.net/~bzr/bzr-windows-installers/trunk

------------------------------------------------------------
revno: 52
revision-id: john at arbash-meinel.com-20091105182129-rjsvfmvqjeorv030
parent: john at arbash-meinel.com-20091103161055-qsd43wzixo03gw25
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: trunk
timestamp: Thu 2009-11-05 12:21:29 -0600
message:
  Build in-place before we build for installing.
  
  We need a better fix for this, but for now we need the generated .h file
  in order to build _static_tuple.c, but setuptools doesn't add the
  build directory to the include path. And it is non-trivial to dig
  that out.
-------------- next part --------------
=== modified file 'tools/win32/buildout-templates/bin/build-installer.bat.in'
--- a/tools/win32/buildout-templates/bin/build-installer.bat.in	2009-10-20 14:53:27 +0000
+++ b/tools/win32/buildout-templates/bin/build-installer.bat.in	2009-11-05 18:21:29 +0000
@@ -59,6 +59,14 @@
 %COMSPEC% /c bzr co %ROOT%/bzr/%BZR_TARGET% %TARGET%
 @if %ERRORLEVEL% NEQ 0 (set BUILD_ERROR=%ERRORLEVEL%) & goto End
 
+rem TODO: remove this step
+rem First we stage a 'build_ext -i'. We have to do this because _static_tuple.h
+rem requires the headers for _simple_set_pyx_api.h but those are autogenerated
+rem It seems that the build process does *not* add the build directory to the
+rem include path, so we have to build in-place to find the headers.
+cd %TARGET%
+%PYTHON% setup.py build_ext -i
+
 rem Build the Python installers first, because we don't want to
 rem include any of the 3rd-party plugins, because we don't bundle
 rem their dependencies. If you don't have all of these Python versions