Skip to main content

Building windows installers in a Linux CI environment using wine and innosetup

Quelea is by far the "side project" that takes up the majority of my time. To aid with testing, I built in CI relatively early with a Jenkins server running on a custom VM. This was great - I could just push a change to the repo from anywhere, and then point the user to the CI release. They'd download it and be able to confirm whether the fix had worked (or not!)

I've since switched to Travis and retired said VM (it's one less thing to maintain, and now everything is on Github.) But both these setups had one main issue - the windows installer wouldn't get built as part of this process, since they were Linux boxes and innosetup doesn't have a linux distribution. Travis has added windows support, but it's in early release, and in any case I'd like the entire build process to be able to run on any Linux box - it makes it both quicker and more transferrable if we ever need to move elsewhere.

I therefore looked into using wine in the CI release to build the windows installer - and it's not too bad at all. There's a few non-obvious things to figure out though, so I'm describing the process here in case anyone else has the same requirement.

I'm making some assumptions here - I'm not walking through creating the innosetup script (the iss file), nor am I walking through integrating innosetup with your build environment of choice. Before following this guide, you should have a build process that produces a working installer exe, from your build script, in a windows environment. We'll focus on translating this to a Linux environment so it can be built by any common CI tool (Travis, CircleCI, etc.)

I'm using Travis and Gradle for the purposes of this walkthrough, but the concepts can be applied anywhere. So without further ado, you'll need to add the following to your .travis.yml:

 sudo: required

(You'll need that.)

addons:
  apt:
    packages:
    - wine
    - xvfb

You'll need to specify both wine and xvfb as packages for your CI environment to install. Wine is needed for obvious reasons. XVFB is the X virtual framebuffer, and is needed to emulate a graphical environment in a headless setting. (It can do all sorts of fancy things such as taking screenshots of the emulated framebuffer and simulating input events, but we don't need to worry about any of that.)

before_install:
  - wget http://files.jrsoftware.org/is/5/innosetup-5.6.1.exe
  - wineboot --update
  - Xvfb :0 -screen 0 1024x768x16 &
  - DISPLAY=:0.0 wine innosetup-5.6.1.exe /VERYSILENT /SUPPRESSMSGBOXES

Without "wineboot --update" you'll get some strange errors and very long hangs when the installer runs - that's the key to making the process go smoothly. The next line spins up the virtual framebuffer, and the line after executes the innosetup installer that wget downloaded in the first step. The final line installs innosetup into the wine environment, and from that point onwards it's available to your build environment!

The next thing I'll create is a simple shell script to build the installer:

#!/bin/bash
wine "/home/travis/.wine/drive_c/Program Files (x86)/Inno Setup 5/iscc.exe" /dMyAppVersion=$1 quelea64.iss /O /F /q"Quelea"

...and then a Gradle task to call said shell script, and rename / move the output files when done:

task innosetup (type:Exec) {
    doFirst {
        workingDir = project.file('.')
        if (System.getProperty('os.name').toLowerCase(Locale.ROOT).contains('windows')) {
            commandLine = ['cmd', '/C', 'build-install.bat', project.queleaversion]
        } else {
            commandLine = ['sh', './build-install.sh', project.queleaversion]
        }
    }
    
    doLast {
        copy {from file("Output/setup.exe") into file(project.distdir + "/standalone") rename { String filename -> return WindowsInstallerName}}
        copy {from file("Output/setup64.exe") into file(project.distdir + "/standalone") rename { String filename -> return WindowsInstaller64Name}}
        delete (file("Output"))
    }
}

Note here that I've still kept the windows batch file in place which enables me to build on either platform. Gradle will selectively call the correct script based on the platform.

And that's pretty much it!

If you'd like to see how we've integrated this process into Quelea, you can poke around in the repo. There's additional logic there to upload the CI artifacts to a Github release as well, which means I can always point people at a single Github release to grab the latest version (and don't have to maintain any off-platform infrastructure.)

Comments

Post a Comment

Popular posts from this blog

The comprehensive (and free) DVD / Blu-ray ripping Guide!

Note: If you've read this guide already (or when you've read it) then going through all of it each time you want to rip something can be a bit of a pain, especially when you just need your memory jogging on one particular section. Because of that, I've put together a quick "cheat sheet" here  which acts as a handy reference just to jog your memory on each key step. I've seen a few guides around on ripping DVDs, but fewer for Blu-rays, and many miss what I believe are important steps (such as ensuring the correct foreign language subtitles are preserved!) While ripping your entire DVD collection would have seemed insane due to storage requirements even a few years ago, these days it can make perfect sense. This guide doesn't show you a one click approach that does all the work for you, it's much more of a manual process. But the benefits of putting a bit more effort in really do pay off - you get to use entirely free tools with no demo versions, it...
36 comments
Read more

Dropbox Java API

This code will no longer work! It uses the old v1 API, which has been turned off. See here for working code with the latest v2 API. As well as being useful as general cloud storage, dropbox also has an API that lets you access its contents programmatically. It's a straightforward REST API with a number of language specific libraries to make the going a bit easier. Java is included on the list of SDKs, but at present only Android is included on the list of tutorials. This can be somewhat frustrating because simple examples using Java are lacking. Fortunately, the process was described by Josh here . So I've taken it and implemented it in Java, and it seems to work. It's a very basic example that authenticates with dropbox then uploads a file called "testing.txt" containing "hello world." Of course, more functionality is available than this, but this is the hard part (at least I found working this bit out the hard part.) Once you've got your Dro...
113 comments
Read more

Using VLCJ for video reliably with out of process players

This post is really a follow on to the last, so if you want a bit of background give that a read through. In it I basically talk about the various options I came to when trying to implement video support in Java, and how I felt the best way to go was using out of process players and VLCJ. Before I get to the code, a warning - while this isn't stupidly hard, it's definitely not for beginners. If you're competent with Java in general you shouldn't have any trouble following - but this is not a cut / paste / forget the advanced stuff job! Eventually and depending on interest I may look into packaging it up into an easy to use library and distributing, but that day is not today! Secondly, this code is literally cut straight out of Quelea and at the moment is: Largely uncommented From an unreleased version Not the best quality May contain Quelea specific bits that don't apply Eventually, it'll all be refactored into beautiful OO-like niceness. But in terms of the con...
5 comments
Read more