Re: [Mingw-cross-env-list] no mysql plugin with qt5 (qtbase)

Introduction

MXE (M cross environment) is a Makefile that compiles a cross compiler and cross compiles many free libraries such as SDL and Qt. Thus, it provides a nice cross compiling environment for various target platforms, which

is designed to run on any Unix system
is easy to adapt and to extend
builds many free libraries in addition to the cross compiler
can also build just a subset of the packages, and automatically builds their dependencies
downloads all needed packages and verifies them by their checksums
is able to update the version numbers of all packages automatically
directly uses source packages, thus ensuring the whole build mechanism is transparent
allows inter-package and intra-package parallel builds whenever possible
is already used by several projects

Screenshots

Cross compiling 4tH:

and running it:

Tutorial

Step 1: Requirements and Download

First, you should ensure that your system meets MXE's requirements. You will almost certainly have to install some stuff.

When everything is fine, download the current stable version:

git clone -b stable https://github.com/mxe/mxe.git

If you don't mind installing it in your home directory, just skip the following step and go straight to step 3.

Step 2: System-wide Installation (optional)

Now you should save any previous installation of the MXE. Assuming you've installed it under /opt/mxe (any other directory will do as well), you should execute the following commands:

su
mv /opt/mxe /opt/mxe.old
exit

Then you need to transfer the entire directory to its definitive location. We will assume again you use /opt/mxe, but feel free to use any other directory if you like.

su
mv mxe /opt/mxe
exit

We're almost done. Just change to your newly created directory and get going:

cd /opt/mxe

Step 3: Build MXE

Enter the directory where you've downloaded the MXE. Now it depends on what you actually want – or need.

If you choose to enter:

make

you're in for a long wait, because it compiles a lot of packages. On the other hand it doesn't require any intervention, so you're free to do whatever you like – like watch a movie or go for a night on the town. When it's done you'll find that you've installed a very capable Win32 cross compiler onto your system.

If you only need the most basic tools you can also use:

make gcc

and add any additional packages you need later on. You can also supply a host of packages on the command line, e.g.:

make gtk lua libidn

You'll always end up with a consistent cross compiling environment.

If you have trouble here, you can try different versions from the download section. Also, please feel free to contact the mxe team through the project mailing list.

After you're done it just needs a little post-installation.

Step 4: Environment Variables

Edit your .bashrc script in order to change $PATH:

export PATH=/where MXE is installed/usr/bin:$PATH

In case you are using custom $PKG_CONFIG_PATH entries, you can add separate entries for cross builds:

export PKG_CONFIG_PATH="entries for native builds"

export PKG_CONFIG_PATH_i686_pc_mingw32="entries for MXE builds"

Remember to use i686-pc-mingw32-pkg-config instead of pkg-config for cross builds. The Autotools do that automatically for you.

Note that any other compiler related environment variables (like $CC, $LDFLAGS, etc.) may spoil your compiling pleasure, so be sure to delete or disable those.

Congratulations! You're ready to cross compile anything you like.

Step 5a: Cross compile your Project (Autotools)

If you use the Autotools, all you have to do is:

./configure --host=i686-pc-mingw32
make

If you build a library, you might also want to enforce a static build:

./configure --host=i686-pc-mingw32 --enable-static --disable-shared
make

Don't worry about a warning like this:

configure: WARNING: If you wanted to set the --build type, don't use --host.
If a cross compiler is detected then cross compile mode will be used.

Everything will be just fine.

Step 5b: Cross compile your Project (CMake)

If you have a CMake project, you can use the provided toolchain file:

cmake ... -DCMAKE_TOOLCHAIN_FILE=/where MXE is installed/usr/i686-pc-mingw32/share/cmake/mxe-conf.cmake

Step 5c: Cross compile your Project (Qt)

If you have a Qt application, all you have to do is:

/where MXE is installed/usr/i686-pc-mingw32/qt/bin/qmake
make

Note that Qt 4 is in the "qt" subdirectory. Qt 5 is in the "qt5" subdirectory and its qmake can be invoked similarly.

If you are using Qt plugins such as the svg or ico image handlers, you should also have a look at the Qt documentation about static plugins.

Note the sql drivers (-qt-sql-*) and the image handlers for jpeg, tiff, gif and mng are built-in, not plugins.

Step 5d: Cross compile your Project (Makefile)

If you have a handwritten Makefile, you probably will have to make a few adjustments to it:

CC=$(CROSS)gcc
LD=$(CROSS)ld
AR=$(CROSS)ar
PKG_CONFIG=$(CROSS)pkg-config

You may have to add a few others, depending on your project.

Then, all you have to do is:

make CROSS=i686-pc-mingw32-

That's it!

Step 5e: Cross compile your Project (OSG)

Using static OpenSceneGraph libraries requires a few changes to your source. The graphics subsystem and all plugins required by your application must be referenced explicitly. Use a code block like the following:

#ifdef OSG_LIBRARY_STATIC
USE_GRAPHICSWINDOW()
USE_OSGPLUGIN(<plugin1>)
USE_OSGPLUGIN(<plugin2>)
...
#endif

Look at examples/osgstaticviewer/osgstaticviewer.cpp in the OpenSceneGraph source distribution for an example. This example can be compiled with the following command:

i686-pc-mingw32-g++ \
    -o osgstaticviewer.exe examples/osgstaticviewer/osgstaticviewer.cpp \
    `i686-pc-mingw32-pkg-config --cflags openscenegraph-osgViewer openscenegraph-osgPlugins` \
    `i686-pc-mingw32-pkg-config --libs openscenegraph-osgViewer openscenegraph-osgPlugins`

The i686-pc-mingw32-pkg-config command from MXE will automatically add -DOSG_LIBRARY_STATIC to your compiler flags.

Further Steps

If you need further assistance, feel free to join the project mailing list where you'll get in touch with the MXE developers and other users.

Download

To obtain the current stable version, run:

git clone -b stable https://github.com/mxe/mxe.git

The development version can be obtained by:

git clone -b master https://github.com/mxe/mxe.git

N.B. when using the development version, ensure you use the local documentation (index.html) - the website reflects the stable branch.

To retrieve updates, run:

git pull

You can also browse the web repository.

In addition, feel free to join the project mailing list and to propose new packages.

For Committers

The following .git/config settings ensure that the stable branch will always be pushed to the gh-pages branch in addition to the stable branch, thus ensuring the website will always stay in sync:

[remote "origin"]
        url = ""
        fetch = +refs/heads/*:refs/remotes/origin/*
        push = refs/heads/master:refs/heads/master
        push = refs/heads/stable:refs/heads/stable
        push = refs/heads/stable:refs/heads/gh-pages
[branch "master"]
        remote = origin
        merge = refs/heads/master
[branch "stable"]
        remote = origin
        merge = refs/heads/stable

Branch Concept

For the sake of simplicity, there are just two branches, "master" and "stable". Although it might seem obvious, here's an overview of the types of changes that go into each branch:

Any change of a build script goes into "master".
Any package upgrade goes into "master".
Any documentation upgrade that refers to a feature not present in stable goes into "master".
Anything else that doesn't affect the build goes into "stable".
Any non-critical improvement to the main Makefile goes into "stable".
Any improvement in the package download URLs or package version recognition goes into "stable".
When in doubt, "master" is used rather than "stable".
After a successful testing phase, the whole "master" branch will be merged into "stable" (fast-forward).

Requirements

MXE requires a recent Unix system where all components as stated in the table below are installed. Detailed instructions are available for:

Debian
Fedora
FreeBSD
Frugalware
Gentoo
Mac OS X
openSUSE

Autoconf	≥ 2.67
Automake	≥ 1.10
Bash
Bison
Bzip2
CMake	≥ 2.8.0
Flex	≥ 2.5.31
GCC (gcc, g++)
Git	≥ 1.7
GNU Coreutils
GNU Gettext
GNU Make	≥ 3.81
GNU Sed
Intltool	≥ 0.40
LibC for 32-bit
libffi	≥ 3.0.0
Libtool	≥ 2.2
OpenSSL-dev
Patch
Perl
Perl XML::Parser
Pkg-config	≥ 0.16
SCons	≥ 0.98
UnZip
Wget
XZ Utils
Yasm

Debian and derivatives

apt-get install autoconf automake bash bison bzip2 \
                    cmake flex gettext git g++ intltool \
                    libffi-dev libtool libltdl-dev openssl libssl-dev \
                    libxml-parser-perl make patch perl \
                    pkg-config scons sed unzip wget \
                    xz-utils yasm

On 64-bit Debian, install also:

apt-get install g++-multilib libc6-dev-i386

On Debian Squeeze, you'll need some packages from backports. Add this line:

deb http://backports.debian.org/debian-backports squeeze-backports main

to your sources.list (or add a new file with the ".list" extension to /etc/apt/sources.list.d/)

apt-get update
aptitude -t squeeze-backports install cmake yasm

Fedora

yum install autoconf automake bash bison bzip2 cmake \
            flex gcc-c++ gettext git intltool make sed \
            libffi-devel libtool openssl-devel patch perl pkgconfig \
            scons yasm unzip wget xz

On 64-bit Fedora, there are issues without a 32-bit compiler.

FreeBSD

pkg_add -r automake autoconf bash bison cmake coreutils\
           flex gettext git glib20 gmake gsed intltool libffi \
           libtool openssl patch perl p5-XML-Parser pkgconf \
           scons unzip wget yasm

Ensure that /usr/local/bin precedes /usr/bin in your $PATH:

For C style shells, edit .cshrc

setenv PATH /usr/local/bin:$PATH

For Bourne shells, edit .profile

export PATH = /usr/local/bin:$PATH

On 64-bit FreeBSD, there are issues without a 32-bit compiler.

Frugalware

pacman-g2 -S autoconf automake bash bzip2 bison cmake \
             flex gcc gettext git intltool make sed libffi libtool \
             openssl patch perl perl-xml-parser pkgconfig \
             scons unzip wget xz xz-lzma yasm

On 64-bit Frugalware, there are issues without a 32-bit compiler.

Gentoo

emerge sys-devel/autoconf sys-devel/automake \
       app-shells/bash sys-devel/bison app-arch/bzip2 \
       dev-util/cmake sys-devel/flex sys-devel/gcc \
       sys-devel/gettext dev-vcs/git \
       dev-util/intltool sys-devel/make sys-apps/sed \
       dev-libs/libffi sys-devel/libtool dev-libs/openssl sys-devel/patch \
       dev-lang/perl dev-perl/XML-Parser \
       dev-util/pkgconfig dev-util/scons app-arch/unzip \
       net-misc/wget app-arch/xz-utils dev-lang/yasm

Mac OS X

Install Xcode 4 and MacPorts, then run:

sudo port install autoconf automake bison cmake coreutils \
                  flex gettext git-core glib2 gsed intltool libffi \
                  libtool openssl p5-xml-parser pkgconfig scons \
                  wget xz yasm

Mac OS X versions ≤ 10.7 are no longer supported.

openSUSE

zypper install -R autoconf automake bash bison bzip2 \
                  cmake flex gcc-c++ gettext-tools git \
                  intltool libffi-devel libtool make openssl \
                  libopenssl-devel patch perl \
                  perl-XML-Parser pkg-config scons \
                  sed unzip wget xz yasm

On 64-bit openSUSE, install also:

zypper install -R gcc-32bit glibc-devel-32bit \
                  libgcc46-32bit libgomp46-32bit \
                  libstdc++46-devel-32bit

Issues without a 32-bit compiler

Certain packages contain native tools that are currently 32-bit only. In order to build these on a 64-bit system, multi-lib support must be enabled in the compiler toolchain. However, not all operating systems support this.

To build the remainder of MXE, specify empty build rules for the affected packages:

make \
            ocaml-cairo_BUILD= \
            ocaml-findlib_BUILD= \
            ocaml-lablgtk2_BUILD= \
            ocaml-camlimages_BUILD= \
            ocaml-flexdll_BUILD= \
            ocaml-native_BUILD= \
            ocaml-core_BUILD= \
            ocaml-lablgl_BUILD= \
            ocaml-xml-light_BUILD=

Usage

All build commands also download the packages if necessary.

In a BSD userland, substitute "make" with "gmake".

make: build all packages, non-parallel
make gcc: build a minimal useful set of packages, i.e. the cross compilers and the most basic packages, non-parallel
make foo bar: build packages "foo", "bar" and their dependencies, non-parallel
make foo bar -j 4 JOBS=2: build packages "foo", "bar" and their dependencies, where up to 4 packages are build in parallel, each with up to 2 compiler processes running in parallel
make check-requirements: check most of the requirements if necessary – executed automatically before building packages
make download: download all packages, non-parallel, such that subsequent builds work without internet access
make download-foo download-bar: download packages "foo", "bar" and their dependencies, non-parallel
make download-foo download-bar -j 4: download packages "foo", "bar" and their dependencies, where up to 4 packages are downloaded in parallel
make clean: remove all package builds – use with caution!
make clean-pkg: remove all unused package files, handy after a successful update
make update: for internal use only! – update the version numbers of all packages, download the new versions and note their checksums
make cleanup-style: for internal use only! – cleanup coding style

List of Packages

See something missing? Feel free to create a new package.

agg	2.5	Anti-Grain Geometry
alure	1.2	alure
apr-util	1.4.1	APR-util
apr	1.4.2	APR
armadillo	3.820.0	Armadillo C++ linear algebra library
atk	2.8.0	ATK
atkmm	2.22.6	ATKmm
aubio	0.3.2	aubio
bfd	2.23.2	Binary File Descriptor library
binutils	2.23.2	GNU Binutils
blas	1	blas
boost	1.53.0	Boost C++ Library
bzip2	1.0.6	bzip2
cairo	1.12.14	cairo
cairomm	1.10.0	cairomm
cblas	1	cblas
cegui	0.7.9	Crazy Eddie’s GUI System (CEGUI)
cfitsio	3340	cfitsio
cgal	4.0.2	cgal
cminpack	1.3.0	cminpack
cppunit	1.12.1	CppUnit
cunit	2.1-2	cunit
curl	7.30.0	cURL
dbus	1.7.2	dbus
dcmtk	3.6.0	DCMTK
devil	1.7.8	DevIL
eigen	3.1.3	eigen
exiv2	0.23	Exiv2
expat	2.1.0	Expat XML Parser
faad2	2.7	faad2
ffmpeg	1.2.1	ffmpeg
fftw	3.3.3	fftw
file	5.14	file
flac	1.2.1	FLAC
flann	1.7.1	FLANN
fltk	1.3.2	FLTK
fontconfig	2.10.92	fontconfig
freeglut	2.8.1	freeglut
freeimage	3.15.4	FreeImage
freetds	0.91	FreeTDS
freetype	2.4.12	freetype
fribidi	0.19.5	FriBidi
ftgl	2.1.3~rc5	ftgl
gc	7.2d	gc
gcc	4.8.1	GCC
gcc-gmp	5.1.1	GMP for GCC
gcc-mpc	1.0.1	MPC for GCC
gcc-mpfr	3.1.2	MPFR for GCC
gd	2.0.35	GD (without support for xpm)
gdal	1.10.0	GDAL
gdb	7.6	gdb
gdk-pixbuf	2.28.1	GDK-pixbuf
geos	3.3.8	GEOS
gettext	0.18.2	gettext
giflib	5.0.4	giflib
glew	1.9.0	GLEW
glib	2.34.3	GLib
glibmm	2.32.1	GLibmm
gmp	5.1.1	GMP
gnutls	3.1.11	GnuTLS
graphicsmagick	1.3.18	GraphicsMagick
gsl	1.15	GSL
gsoap	2.8.15	gSOAP
gst-plugins-base	1.0.7	gst-plugins-base
gst-plugins-good	1.0.7	gst-plugins-good
gstreamer	1.0.7	gstreamer
gta	1.0.4	gta
gtk2	2.24.18	GTK+
gtkGLArea	2.0.1	GtkGLArea
gtkglext	1.2.0	GtkGLExt
gtkglextmm	1.2.0	GtkGLExtmm
gtkimageview	1.6.4	GtkImageView
gtkmm2	2.24.2	GTKMM
gtksourceview	2.10.5	GTKSourceView
gtksourceviewmm2	2.10.3	GtkSourceViewmm
guile	1.8.7	GNU Guile
harfbuzz	0.9.16	HarfBuzz
hdf4	4.2.9	HDF4
hdf5	1.8.10-patch1	HDF5
hunspell	1.3.2	Hunspell
id3lib	3.8.3	id3lib
ilmbase	2.0.0	IlmBase
imagemagick	6.8.5-6	ImageMagick
jasper	1.900.1	JasPer
jpeg	9	jpeg
json-c	0.11	json-c
lame	3.99	lame
lapack	3.4.2	lapack
lcms	2.4	lcms
lcms1	1.19	lcms1
lensfun	0.2.7	lensfun
levmar	2.6	levmar
libarchive	3.0.3	Libarchive
libass	0.10.1	libass
libcroco	0.6.2	Libcroco
libdnet	1.11	libdnet
libevent	2.0.21	libevent
libf2c	1	libf2c
libffi	3.0.13	libffi
libftdi	0.20	LibFTDI
libgcrypt	1.5.2	libgcrypt
libgda	4.2.13	libgda
libgdamm	4.1.3	libgdamm
libgee	0.5.0	libgee
libgeotiff	1.4.0	GeoTiff
libglade	2.6.4	glade
libgnurx	2.5.1	libgnurx
libgomp	4.8.1	GCC-libgomp
libgpg_error	1.11	libgpg-error
libgsasl	1.8.0	Libgsasl
libgsf	1.14.26	libgsf
libharu	2.2.1	libharu
libiberty	2.23.2	libiberty
libical	1.0	libical
libiconv	1.14	libiconv
libidn	1.26	Libidn
libircclient	1.6	libircclient
liblo	0.26	liblo
liblqr-1	0.4.2	liblqr-1
libmad	0.15.1b	libmad
libmikmod	3.2.0	libMikMod
libmng	1.0.10	libmng
libmodplug	0.8.8.4	libmodplug
libntlm	1.3	Libntlm
liboauth	1.0.1	liboauth
libodbc++	0.2.5	libodbc++
liboil	0.3.17	liboil
libpano13	2.9.18_rc2	libpano13
libpaper	1.1.24+nmu2	libpaper
libpng	1.6.1	libpng
librsvg	2.37.0	librsvg
librtmp	2.4	librtmp
libsamplerate	0.1.8	libsamplerate
libshout	2.3.1	libshout
libsigc++	2.3.1	libsigc++
libsndfile	1.0.25	libsndfile
libssh2	1.4.3	libssh2
libtool	2.4.2	GNU Libtool
libunistring	0.9.3	libunistring
libusb	1.2.6.0	LibUsb
libvpx	1.1.0	vpx
libxml++	2.36.0	libxml2
libxml2	2.9.1	libxml2
libxslt	1.1.28	libxslt
libzip	0.10.1	libzip
llvm	3.2	llvm
log4cxx	0.10.0	log4cxx
lua	5.2.2	Lua
lzo	2.06	lzo
matio	1.5.1	matio
mdbtools	0.7	mdbtools
mingw-utils	0.4-1	MinGW Utilities
mingwrt	3.20-2	MinGW Runtime
mpfr	3.1.2	mpfr
muparser	2.2.3	muParser
mxml	2.7	Mini-XML
mysql-connector-c	6.1.0	MySQL Connector C
ncurses	5.9	Ncurses
netcdf	4.3.0	NetCDF
netpbm	10.35.89	Netpbm
nettle	2.6	nettle
nsis	2.46	NSIS
ocaml	4.00.1	ocaml
cairo-ocaml	1.2.0	cairo-ocaml
camlimages	4.0.1	camlimages
ocaml	4.00.1	ocaml
ocaml-findlib	1.3.3	findlib
ocaml-flexdll	0.31	flexdll
ocaml-lablgl	20120306	lablgl
ocaml-lablgtk2	2.16.0	lablgtk2
ocaml-xml-light	2.2	xml-light
ogg	1.3.0	OGG
old	0.17	old
openal	1.15.1	openal
opencore-amr	0.1.2	opencore-amr
opencsg	1.3.2	opencsg
opencv	2.4.4	OpenCV
openexr	2.0.0	OpenEXR
openscenegraph	3.1.5	OpenSceneGraph
openssl	1.0.1e	openssl
opus	1.0.2	opus
opusfile	0.2	opusfile
pango	1.34.1	Pango
pangomm	2.28.4	Pangomm
pcl	1.6.0	PCL (Point Cloud Library)
pcre	8.32	PCRE
pdcurses	3.4	PDcurses
plib	1.8.5-rc1	Plib
plibc	0.1.7	Plibc
pdflib_lite	7.0.5p3	PDFlib Lite
pfstools	1.8.5	pfstools
physfs	2.0.3	physfs
picomodel	1142ad8	picomodel
pixman	0.29.4	pixman
plotmm	0.1.2	PlotMM
plotutils	2.6	plotutils
poco	1.4.6p1	POCO C++ Libraries
poppler	0.22.4	poppler
popt	1.16	popt
portablexdr	4.9.1	PortableXDR
portaudio	19_20111121	portaudio
portmidi	217	portmidi
postgresql	9.2.4	PostgreSQL
proj	4.8.0	proj
protobuf	2.5.0	protobuf
pthreads	2-9-1	Pthreads-w32
qdbm	1.8.78	QDBM
qjson	0.8.1	QJson
qt	4.8.4	Qt
qtactiveqt	5.0.2	Qt
qtbase	5.0.2	Qt
qtdeclarative	5.0.2	Qt
qtgraphicaleffects	5.0.2	Qt
qtimageformats	5.0.2	Qt
qtjsbackend	5.0.2	Qt
qtmultimedia	5.0.2	Qt
qtquick1	5.0.2	Qt
qtscript	5.0.2	Qt
qtsvg	5.0.2	Qt
qttools	5.0.2	Qt
qttranslations	5.0.2	Qt
qtxmlpatterns	5.0.2	Qt
qwt	6.0.2	Qwt
qwtplot3d	0.2.7	QwtPlot3D
readline	6.2	Readline
sdl	1.2.15	SDL
sdl_gfx	2.0.24	SDL_gfx
sdl_image	1.2.12	SDL_image
sdl_mixer	1.2.12	SDL_mixer
sdl_net	1.2.8	SDL_net
sdl_pango	0.1.2	SDL_Pango
sdl_sound	1.0.3	SDL_sound
sdl_ttf	2.0.11	SDL_ttf
smpeg	0.4.5+cvs20030824	smpeg
sox	14.4.1	SoX
speex	1.2rc1	Speex
sqlite	3071602	SQLite
suitesparse	4.2.1	SuiteSparse
t4k_common	0.1.1	t4k_common
taglib	1.7.2	TagLib
taglib	0.9.6	Taocrypt
teem	1.11.0	Teem
theora	1.1.1	Theora
tiff	4.0.3	LibTIFF
tinyxml	2.6.2	tinyxml
tre	0.8.0	TRE
twolame	0.3.13	TwoLAME
vigra	1.9.0	vigra
vmime	b755529	VMime
vorbis	1.3.3	Vorbis
vtk	5.8.0	vtk
w32api	3.17	MinGW Windows API
wavpack	4.60.1	WavPack
wget	1.14	wget
winpcap	4_1_2	WinPcap
wt	3.3.0	Wt
wxwidgets	2.9.4	wxWidgets
x264	20121211-2245	x264
xapian-core	1.2.15	Xapian-Core
xerces	3.1.1	Xerces-C++
xine-lib	1.1.21	xine-lib
xmlwrapp	0.6.3	xmlwrapp
xvidcore	1.3.2	xvidcore
xz	5.0.4	XZ
yassl	2.2.3	Yassl
zlib	1.2.8	zlib
zziplib	0.13.59	ZZIPlib

Guidelines for Creating Packages

The package should be a free software library that is really used by one of your applications.

BTW, we're always curious about the applications people are porting. We maintain a list of projects which use MXE. No matter whether your project is free or proprietary – as long as it has its own website, we'd be happy to link to it.

Also, feel free to link to us. :-)
Grep through the src/*.mk files to find a project that is most similar to yours. (Really, grep is your friend here.)

For instance, when adding a GNU library, you should take a package like gettext.mk or libiconv.mk as the base of your work. When using a SourceForge project, you could start with a copy of xmlwrapp.mk. And so on.
Adjust the comments, fill in the $(PKG)_* fields.

To fill the $(PKG)_CHECKSUM field, use a command such as (for file gettext.mk):
```
make update-checksum-gettext
```
Be especially careful with the $(PKG)_DEPS section. The easiest way to get the dependencies right is to start with a minimal setup. That is, initialize MXE with make gcc only, then check whether your package builds successfully.

Always list the dependency on gcc explicitly:
```
$(PKG)_DEPS     := gcc ...
```
Add your package to the list of packages.

Each package gets its own table row element with table cells having IDs specifying your .mk file, package version and website:
```
<tr>
    <td id="gettext-package">gettext</td>
    <td id="gettext-version">0.18.1.1</td>
    <td id="gettext-website"><a href="">gettext</a></td>
</tr>
        
```
Write your $(PKG)_BUILD. If your library has a ./configure script, enable/disable all dependency libraries explicitly via "--enable-*" and "--disable-*" options.
You might also have to provide a patch for it. In that case, have a look at other patches such as sdl-2-fix-dinput.patch. In particular, each patch file should be named as:
```
PACKAGE-PATCHNUMBER-DESCRIPTION.patch
```
and should start with:
```
This file is part of MXE.
See index.html for further information.

This patch has been taken from:
https://...
```
where the URL points to the bugtracker entry, mailing list entry or website you took the patch from.

If you created the patch yourself, please offer it to the upstream project first, and point to that URL, using the same wording: "This patch has been taken from:".

Depending on the feedback you get from the upstream project, you might want to improve your patch.
If you find some time, please provide a minimal test program for it. It should be simple, stand alone and should work unmodified for many (all?) future versions of the library. Test programs are named as:
```
PACKAGE-test.c
```
or
```
PACKAGE-test.cpp
```
depending on whether it is a C or C++ library. To get a clue, please have a look at existing test programs such as sdl-test.c.

At the very end of your *.mk file you should build the test program in a generic way, using strict compiler flags. The last few lines of sdl.mk will give you a clue.
You could also try to provide a $(PKG)_UPDATE section. However, that requires some experience and "feeling" for it. So it is perfectly okay if you leave a placeholder:
```
define $(PKG)_UPDATE
    echo 'TODO: write update script for $(PKG).' >&2;
    echo $($(PKG)_VERSION)
endef
```
We'll fill that in for you. It's a funny exercise.

Check that you don't have "dirty stuff" in your *.mk files, such as TAB characters or trailing spaces at lines endings. Have a look at random *.mk files to get a feeling for the coding style.

The same holds for your test program.

However, patch files should always appear in the same coding style as the files they are patching.

Finally, in your $(PKG)_BUILD section, please check that you use our portability variables:

`bash`	→	`$(SHELL)`
`install`	→	`$(INSTALL)`
`libtool`	→	`$(LIBTOOL)`
`libtoolize`	→	`$(LIBTOOLIZE)`
`make`	→	`$(MAKE)`
`patch`	→	`$(PATCH)`
`sed`	→	`$(SED)`
`sort`	→	`$(SORT)`
`wget`	→	`$(WGET)`

Check whether everything runs fine. If you have some trouble, don't hesitate to ask on the mailing list, providing your *.mk file so far.
Issue a pull request to propose your final *.mk file to us. If you have trouble with pull requests, send your file to the mailing list instead.

Either way, don't forget to tell us if there are some pieces in your *.mk file you feel unsure about. We'll then have a specific look at those parts, which avoids trouble for you and us in the future.

Copyright © 2007–2013

Volker Grabsch
Mark Brand
Tony Theodore
Martin Gerhardy
... and many other contributors

(contact via the project mailing list)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

History

2012-04-12 – Release 2.22

From:	Lars Engelhard
Subject:	Re: [Mingw-cross-env-list] no mysql plugin with qt5 (qtbase)
Date:	Sat, 08 Jun 2013 18:03:59 +0200
User-agent:	Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6