Skip to content

libvips/build-win32

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

VIPS WIN32

This package makes a 32-bit Windows binary of libvips and nip2. If you want a 64-bit Windows binary, see build-win64. The 64-bit version is also much simpler to use.

We use jhbuilder to git, mingw to compile, and good old zip to package the vips source code for WIN32.

JHBuild is a tool designed to ease building collections of source packages, called “modules”. JHBuild uses “module set” files to describe the modules available to build. The “module set” files include dependency information that allows JHBuild to discover what modules need to be built and in what order.

MinGW, a contraction of "Minimalist GNU for Windows", is a minimalist development environment for native Microsoft Windows applications.

MinGW provides a complete Open Source programming tool set which is suitable for the development of native MS-Windows applications, and which do not depend on any 3rd-party C-Runtime DLLs. (It does depend on a number of DLLs provided by Microsoft themselves, as components of the operating system; most notable among these is MSVCRT.DLL, the Microsoft C runtime library. Additionally, threaded applications must ship with a freely distributable thread support DLL, provided as part of MinGW itself).

PREREQUISITES

[Ubuntu Desktop] (http://www.ubuntu.com/download/desktop)

  • This doesn't mean you can't get the process to work on anything else. This is simply what we are using and know to work. Tested on 10.10 and 11.04, 32- and 64-bit. Though you can only make a 32-bit Windows binary for now.

OPTIONAL

[VMware Player] (http://www.vmware.com/products/player/) - Bubba runs his Ubuntu Desktop in a VMWare Player on a Windows 7 Ultimate x64 Desktop host.

[DEPENDENCIES] (http://xkcd.com/754/)

It is possible that you already have some of these installed on your Ubuntu Desktop; however, it is not likely that you have all of them. Better safe than sorry, install them all. You might even want to update the whole kit, just for the heck of it.

Build/Tool Related Dependencies

sudo apt-get install build-essential \
wine \
mingw-w64 mingw-w64-tools \
cmake \
jhbuild \
autoconf \
automake1.4 \
automake1.7 \
automake1.9 \
autotools-dev \
docbook-utils \
docbook2x \
gtk-doc-tools \
nasm \
bison \
flex

Library Dependencies

sudo apt-get install libatk1.0-0 \
libatk1.0-dev \
libglib2.0-0 \
libglib2.0-dev \
libgtk2.0-0 \
libgtk2.0-dev \
libglade2-0 \
libglade2-dev \
libgsf-1-114 \
libgsf-gnome-1-dev \
libpango1.0-0 \
libpango1.0-dev \
libcairo2 \
libcairo2-dev \
libexpat1 \
libexpat1-dev \
libfontconfig1 \
libfontconfig1-dev \
libfreetype6 \
libfreetype6-dev \
gettext \
libpng12-0 \
libpng12-dev \
libxml2 \
libxml2-dev \
tango-icon-theme \
libcxxtools6 \
libcxxtools-dev \
zlib1g \
zlib1g-dev \
zlibc 

These are Ubuntu binaries and of course we will be building a Windows binary. However, some of the packages we build are not very good at cross-compiling and builds can fail unless they can find a native library as well.

SUMMARY

Check specific build folders for further instructions.