Wine Mono vagrant build environment

Austin English austinenglish at gmail.com
Thu Mar 9 22:16:10 CST 2017


On Fri, Mar 3, 2017 at 2:02 PM, Vincent Povirk <madewokherd at gmail.com> wrote:
> I'm not sure if anyone will care about this, but I figured I should
> mention it somewhere.
>
> With the release of Wine Mono 4.7.0 today, the source tree now ships
> with a Vagrantfile, which can be used with Vagrant to create a virtual
> machine that can build the project. This was the environment used to
> create the msi package, and I plan to continue using it this way for
> future releases.
>
> Previously, the official build environment was my work PC, which means
> there was always the possibility that upgrading or changing it would
> have some effect on the official packages.
>
> I don't know if this is useful for anyone else, but I figure that an
> easy way to create a build environment, along with the complete
> documentation of that environment which we get as a side-effect, can
> only be a good thing.
>
> This is not a replacement for building on real hardware. I only plan
> to use it to make official builds, not for development, and I still
> want to hear about any issues people encounter while trying to do the
> build on their own systems.

Great! I've built wine-mono a few times for various reasons. While it
wasn't terribly difficult to set up (wine-gecko is definitely more
involved), I'm a huge fan of having a reproducible build setup.

Thanks Vincent!

-- 
-Austin
GPG: 14FB D7EA A041 937B



More information about the wine-devel mailing list