Building XULRunner with Python

  • Revision slug: Building_XULRunner_with_Python
  • Revision title: Building XULRunner with Python
  • Revision id: 168285
  • Created:
  • Creator: SteveLee
  • Is current revision? No
  • Comment removed in progress

Revision Content

Building XULRunner with Python

This page describes how to build XULRunner with Python extension on Windows and while generally useful it is written based on experiences with accessibility projects.

With the Python extensions enabled XULRunner provides python script access to the DOM and XPCOM in addition to the usual Java Script. This gives access to Python features and modules and builds on Mark Hammond's pyXPCOM work from Active State.

Currently (Mar 07) Python is not enabled by default so a custom build of Mozilla is needed. This page provides instructions in the hope of eliminating much trial and error. You should also read the the developer documentation on source code and building as wells as PyXPCOM

XULRunner with Python promises to be a good platform for accessibility projects and both Jambu Alternative Input and the IAccessible2 test tool are using it. Of particular interested is access to MSAA and IAccessible2 via the Python comtypes package.


Development Machine Setup

First a word of warning that ZoneAlarm has exhibited memory leaks that cause build machines to crash with rather spurious errors. You may want to uninstall it you suspect this to be a problem. You will also want to disable any virus scanner resident monitoring as that will slow builds.

Ensure your PC is running XP with all the latest Service Packs and patches applied.

Microsoft C++ compiler is required and whilst the current free version is Visual Studio 8 Express (MSVC8) you will almost certainly want to use Visual Studio .NET 2003 (MSVC71) which is not longer officially available. The issue is that XULRunner must be built with the same version of C as Python and with Python 2.5 that is MSVC71. Both must use the same version of the C runtime library MSVCRT?.DLL or crashes will ensue. The alternative is to build Python with MSVC8 as well asMozilla, but that may be problematic. It might also be possible to use the Open Source MinGW compiler with the correct MSVC run time but that is apparently not recommended. Apply any Service Packs and for MSVC71 SP 1 is available. The matching platform SDK is also needed and for MSVC71 that is .NET Framework SDK 1.1.

Next you need the latest Mozilla Build system and the latest incarnation is very easy to use. Also install the included Python using python25\python-2.5.msi. It doesn't need to be installed for the build but will be useful later when installing Python packages which look for entires in the Windows' registry.


Building

The batch file start-msvc71.bat is used to launch the build console (MSys from the MinGw project ). You could modify it to set the CVSROOT environment variable if you are mainly working with Mozilla.

set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot

Having created a mozilla project directory (e.g. C:\projects\mozilla) save the following .mozconfig file in the mozilla directory. Note this is complete and does not require the checkout of any other project specific .mozconfig files as sometimes shown. It effectively specifies a release build that is not particularly suitable for debugging XULRunner itself. It uses the trunk (or latest) code in CVS so may be unstable.

mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../obj-xulrunner
mk_add_options MOZ_CO_PROJECT=xulrunner
ac_add_options --enable-application=xulrunner
ac_add_options --enable-extensions=python,default
ac_add_options --disable-javaxpcom
ac_add_options --disable-activex
ac_add_options --disable-activex-scripting
ac_add_options --disable-tests
ac_add_options --enable-optimize 

To check out all the required source code and build it execute

cd /c/projects
cvs co mozilla/client.mk
cd mozilla
make -f client.mk

This is also used for subsequent updates from CVS or to build without a check out use

cd mozilla
make -f client.mk build

The built XULRunner can then be found as c:\projects\obj-xulrunner\dist\bin\xulrunner.exe.


Using Python in XUL applications

HTML <script> tags specify that Python is used with type="application/x-python" attribute. DOM scripting is pretty much as with Java Script. For example

def onLoad():
    btnTest = document.getElementById("btnTest")
    btnTest.addEventListener('command', onTest, False)

def onTest():
    window.alert('Button activated')
        
window.addEventListener('load', onLoad, False)


One possible gotcha is that the default python path used to find modules that are imported explicitly includes the xulrunner executable directory and the directory that is current when XULRunner launches. However it does not include any path related to the XUL application being run. Some work around will need to be found.

Unhandled exceptions are displayed in the JavaScript Error Console which can be opened using xulrunner -jsconsole. One solution is to put try .... except: print_exc() round any event handler to print tracebacks to stdout and use a python console to catch that output.

Use task manager to check for a zombie xulrunner process after a crash. A zombie will keep old code open and cause confusion when you make changes and run xulrunner again.

Deploying

Perhaps there is a XULRunner installer, otherwise the dist folder should be copied. Don't copy any .pyo files or errors will occur on the target machine.

Python must be installed on the target machine. Eventually perhaps a minimal Python installation could be created using setup.py or pyInstaller. It is possible to test for python in a batch file using something like

rem Check Python 2.5 installed
reg query "HKLM\SOFTWARE\Python\PythonCore\2.5" > nul 2>&1 || reg query "HKCU\SOFTWARE\Python\PythonCore\2.5" > nul 2>&1
if errorlevel 1 (
    echo Python 2.5 was not found. Please install it.
    echo Exiting...
    pause
    exit /b 1
    )

start "XULRunner with Python" "%moz_bin%\xulrunner.exe" -app application.ini %opts%
exit /b 0

Revision Source

<p>
</p>
<h2 name="Building_XULRunner_with_Python"> Building XULRunner with Python </h2>
<p>This page describes how to build XULRunner with Python extension on Windows and while generally useful it is written based on experiences with accessibility projects. 
</p><p>With the Python extensions enabled XULRunner provides python script access to the DOM and XPCOM in addition to the usual Java Script. This gives access to Python features and modules and builds on Mark Hammond's pyXPCOM work from Active State. 
</p><p>Currently (Mar 07) Python is not enabled by default so a custom build of Mozilla is needed. This page provides instructions in the hope of eliminating much trial and error. You should also read the the developer documentation on <a href="en/Download_Mozilla_Source_Code">source code</a> and <a href="en/Build_Documentation">building</a> as wells as <a href="en/PyXPCOM">PyXPCOM</a>
</p><p>XULRunner with Python promises to be a good platform for accessibility projects and both <a class="external" href="http://www.oatsoft.org/trac/jambu/wiki">Jambu Alternative Input</a> and the IAccessible2 test tool are using it. Of particular interested is access to MSAA and IAccessible2 via the Python comtypes package.
</p><p><br>
</p>
<h3 name="Development_Machine_Setup"> Development Machine Setup </h3>
<p>First a word of warning that ZoneAlarm has exhibited memory leaks that cause build machines to crash with rather spurious errors. You may want to uninstall it you suspect this to be a problem. You will also want to disable any virus scanner resident monitoring as that will slow builds.
</p><p>Ensure your PC is running XP with all the latest Service Packs and patches applied.
</p><p>Microsoft C++ compiler is required and whilst the current free version is Visual Studio 8 Express (MSVC8) you will almost certainly want to use Visual Studio .NET 2003 (MSVC71) which is not longer officially available. The issue is that XULRunner must be built with the same version of C as Python and with Python 2.5 that is MSVC71. Both must use the same version of the C runtime library MSVCRT?.DLL or crashes will ensue. The alternative is to build Python with MSVC8 as well asMozilla, but that may be problematic. It might also be possible to use the Open Source MinGW compiler with the correct MSVC run time but that is apparently not recommended. Apply any Service Packs and for MSVC71 <a class="external" href="http://www.microsoft.com/downloads/details.aspx?familyid=69d2219f-ce82-46a5-8aec-072bd4bb955e&amp;displaylang=en">SP 1</a> is available. The matching platform SDK is also needed and for MSVC71 that is <a class="external" href="http://www.microsoft.com/downloads/details.aspx?FamilyID=9b3a2ca6-3647-4070-9f41-a333c6b9181d&amp;DisplayLang=en">.NET Framework SDK 1.1</a>.
</p><p>Next you need the latest <a href="en/Windows_Build_Prerequisites"> Mozilla Build system</a> and the latest incarnation is very easy to use. Also install the included Python using <i>python25\python-2.5.msi</i>. It doesn't need to be installed for the build but will be useful later when installing Python packages which look for entires in the Windows' registry.
</p><p><br>
</p>
<h3 name="Building"> Building </h3>
<p>The batch file <i>start-msvc71.bat</i> is used to launch the build console (MSys from the MinGw project ). You could modify it to set the CVSROOT environment variable if you are mainly working with Mozilla.
</p>
<pre>set CVSROOT=:pserver:anonymous@cvs-mirror.mozilla.org:/cvsroot
</pre>
<p>Having created a <i>mozilla</i> project directory (e.g. <i>C:\projects\mozilla</i>) save the following .mozconfig file in the mozilla directory. Note this is complete and does not require the checkout of any other project specific .mozconfig files as sometimes shown. It effectively specifies a release build that is not particularly suitable for debugging XULRunner itself. It uses the trunk (or latest) code in CVS so may be unstable.
</p>
<pre>mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../obj-xulrunner
mk_add_options MOZ_CO_PROJECT=xulrunner
ac_add_options --enable-application=xulrunner
ac_add_options --enable-extensions=python,default
ac_add_options --disable-javaxpcom
ac_add_options --disable-activex
ac_add_options --disable-activex-scripting
ac_add_options --disable-tests
ac_add_options --enable-optimize 
</pre> 
<p>To check out all the required source code and build it execute
</p>
<pre>cd /c/projects
cvs co mozilla/client.mk
cd mozilla
make -f client.mk
</pre>
<p>This is also used for subsequent updates from CVS or to build without a check out use
</p>
<pre>cd mozilla
make -f client.mk build
</pre>
<p>The built XULRunner can then be found as <i>c:\projects\obj-xulrunner\dist\bin\xulrunner.exe</i>.
</p><p><br>
</p>
<h3 name="Using_Python_in_XUL_applications"> Using Python in XUL applications </h3>
<p>HTML &lt;script&gt; tags specify that Python is used with <i>type="application/x-python"</i> attribute. DOM scripting is pretty much as with Java Script. For example
</p>
<pre>def onLoad():
    btnTest = document.getElementById("btnTest")
    btnTest.addEventListener('command', onTest, False)

def onTest():
    window.alert('Button activated')
        
window.addEventListener('load', onLoad, False)
</pre>
<p><br>
One possible gotcha is that the default python path used to find modules that are <i>import</i>ed explicitly includes the xulrunner executable directory and the directory that is current when XULRunner launches. However it does not include any path related to the XUL application being run. Some work around will need to be found.
</p><p>Unhandled exceptions are displayed in the JavaScript Error Console which can be opened using <i>xulrunner -jsconsole</i>. One solution is to put <i>try .... except: print_exc()</i> round any event handler to print tracebacks to stdout and use a python console to catch that output.
</p><p>Use task manager to check for a zombie xulrunner process after a crash. A zombie will keep old code open and cause confusion when you make changes and run xulrunner again.
</p>
<h3 name="Deploying"> Deploying </h3>
<p>Perhaps there is a XULRunner installer, otherwise the <i>dist</i> folder should be copied. Don't copy any <i>.pyo</i> files or errors will occur on the target machine.
</p><p>Python must be installed on the target machine. Eventually perhaps a minimal Python installation could be created using setup.py or pyInstaller. It is possible to test for python in a batch file using something like
</p>
<pre>rem Check Python 2.5 installed
reg query "HKLM\SOFTWARE\Python\PythonCore\2.5" &gt; nul 2&gt;&amp;1 || reg query "HKCU\SOFTWARE\Python\PythonCore\2.5" &gt; nul 2&gt;&amp;1
if errorlevel 1 (
    echo Python 2.5 was not found. Please install it.
    echo Exiting...
    pause
    exit /b 1
    )

start "XULRunner with Python" "%moz_bin%\xulrunner.exe" -app application.ini %opts%
exit /b 0
</pre>
Revert to this revision