Testing:Windows Testing Environment

From OpenLP
Jump to: navigation, search

Windows Nightly Build

The easiest way of testing OpenLP is to use the Nightly Build. Note however that this may sometimes be a day or two out of date, and you can check when it was created on the OpenLP Twitter account.

If you want to run the most up to date version, the following steps will guide you through the process.

Installing Required Software

In order to run the very latest code, or developers personal branches, several pieces of software first need to be installed.

The steps required are detailed on the Windows Environment page.

Getting source code

You can get a very recent revision of OpenLP via the "nightly build" tarball, or you can get the latest version directly via Bazaar.

Nightly Build

The nightly build is a source tarball (.tar.gz file) of a recent revision. The tarball is generated each night. To see when the tarball was last created, check the OpenLP Twitter account. Simply download this file to your computer, and then extract it. If you don't have an application which can open .tar.gz files, the recommended program is 7-zip

Bazaar Version Control

To access the source code, you will need a Bazaar client. Download the Windows client from the Bazaar site. The recommended download is the latest Stable Release.

Once installed, create a Project directory for OpenLP, e.g. "My Documents\My Projects\OpenLP". Then right-click in the directory, go to TortoiseBzr, Checkout/Branch and type in lp:openlp in the "branch from" edit box.

Further information is on the Bazaar page.

Running OpenLP

Once you have run these steps, bring up the Windows command prompt (Start -> Run -> "cmd.exe"), CD into the folder you downloaded OpenLP into and then run the program using python. We recommend using the debug command line option which produces the log file that will assist developers if you find a problem.

C:\Users\jonathan> cd Documents\My Projects\OpenLP
C:\Users\jonathan\Documents\My Projects\OpenLP> c:\python26\python openlp.pyw -l debug

Further Information