Screenshots
Cross compiling 4tH:
and running it:
This Makefile compiles a MinGW cross compiler and cross compiles many free libraries such as GD, SDL and Qt. Thus, it provides a nice MinGW cross compiling environment which
First, you should ensure that your system meets mingw-cross-env's requirements. You will almost certainly have to install some stuff.
When everything is fine, download the latest release:
wget https://bitbucket.org/vog/mingw-cross-env/downloads/mingw-cross-env-X.Y.tar.gz
and unpack the tarball:
tar -xzvf mingw-cross-env-X.Y.tar.gz
If you don't mind installing it in your home directory, just skip the following step and go straight to step 3.
Now you should save any previous installation of the mingw-cross-env. Assuming you've installed it under /opt/mingw (any other directory will do as well), you should execute the following commands:
su mv /opt/mingw /opt/mingw.old exit
Then you need to transfer the entire directory to its definitive location. We will assume again you use /opt/mingw, but feel free to use any other directory if you like.
su
mv mingw-cross-env-X.Y /opt/mingw
exit
We're almost done. Just change to your newly created directory and get going:
cd /opt/mingw
Enter the directory where you've unpacked the mingw-cross-env. 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.
After you're done it just needs a little post-installation.
Edit your .bashrc script in order to change $PATH:
export PATH=/where mingw-cross-env is installed/usr/bin:$PATH
In case you are using custom $PKG_CONFIG_PATH entries, you can add separate entries for MinGW cross builds:
export PKG_CONFIG_PATH="entries for native builds"
export PKG_CONFIG_PATH_i686_pc_mingw32="entries for mingw-cross-env 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.
If you use the Autotools, all you have to do is:
./configure --host=i686-pc-mingw32
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.
If you have a CMake project, you can use the provided toolchain file:
cmake ... -DCMAKE_TOOLCHAIN_FILE=/where mingw-cross-env is installed/usr/i686-pc-mingw32/share/cmake/mingw-cross-env-conf.cmake
If you have a Qt application, all you have to do is:
i686-pc-mingw32-qmake
make
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.
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!
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 mingw-cross-env will
automatically add -DOSG_LIBRARY_STATIC to your compiler flags.
If you need further assistance, feel free to join the project mailing list where you'll get in touch with the mingw-cross-env developers and other users.
To obtain the current development version, install Mercurial and run:
hg clone http://hg.savannah.nongnu.org/hgweb/mingw-cross-env
To retrieve updates, run:
hg pull -u
You can also browse the web repository.
In addition, feel free to join the project mailing list and to propose new packages.
Mingw-cross-env requires a recent Unix system where all components as stated in the table below are installed. Detailed instructions are available for:
| Autoconf | ≥ 2.64 |
| Automake | ≥ 1.10 |
| Bash | |
| Bison | |
| Bzip2 | |
| CMake | ≥ 2.8.0 |
| Flex | ≥ 2.5.31 |
| GCC (gcc, g++) | |
| GNU Make | ≥ 3.81 |
| GNU Sed | |
| Intltool | ≥ 0.40 |
| LibC for 32-bit | |
| Libtool | ≥ 2.2 |
| OpenSSL-dev | |
| Patch | |
| Perl | |
| Perl XML::Parser | |
| Pkg-config | ≥ 0.16 |
| SCons | ≥ 0.98 |
| UnZip | |
| Wget | |
| XZ Utils | |
| Yasm |
aptitude install -R autoconf automake bash bison bzip2 \
cmake flex g++ intltool make sed \
libtool libltdl-dev openssl libssl-dev \
libxml-parser-perl patch perl \
pkg-config scons unzip wget \
xz-utils yasm
On 64-bit Debian, install also:
aptitude install -R g++-multilib
yum install autoconf automake bash bison bzip2 cmake \
flex gcc-c++ intltool make sed libtool \
openssl-devel patch perl pkgconfig scons \
yasm unzip wget xz
On 64-bit Fedora, there are open issues with the NSIS package.
pkg_add -r automake111 autoconf268 bash bison cmake \
flex gmake gsed intltool libtool openssl \
patch perl p5-XML-Parser pkg-config 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 open issues with the NSIS package.
pacman-g2 -S autoconf automake bash bzip2 bison cmake \
flex gcc intltool make sed libtool openssl \
patch perl perl-xml-parser pkgconfig scons \
unzip wget xz xz-lzma yasm
On 64-bit Frugalware, there are open issues with the NSIS package.
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 \
dev-util/intltool sys-devel/make sys-apps/sed \
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
Install Xcode 3 and MacPorts, then run:
sudo port install autoconf automake bison cmake flex \
gsed intltool libtool openssl \
p5-xml-parser pkgconfig scons \
wget xz yasm
On Mac OS X ≤ 10.5, also select a more recent GCC:
sudo port install gcc_select sudo gcc_select gcc42
Xcode 4 is not supported yet.
zypper install -R autoconf automake bash bison bzip2 \
cmake flex gcc-c++ gettext-tools \
intltool 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 \
libgcc45-32bit libgomp45-32bit \
libstdc++45-devel-32bit
The NSIS package contains some 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.
Since no other packages depend on it, the remainder of mingw-cross-env can be successfully built by simply removing the package:
rm where mingw-cross-env is unpacked/src/nsis.mk
All build commands also download the packages if necessary.
In a BSD userland, substitute "make" with "gmake".
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 mingw-cross-env. 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.
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 mingw-cross-env with make gcc only,
then check whether your package builds successfully.
Always list the dependency on gcc explicitly:
$(PKG)_DEPS := gcc ...
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 mingw-cross-env. See doc/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.cor
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 the $(PKG)_UPDATE section empty.
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) |
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.
Propose your final *.mk file to the mailing list.
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.
(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.
Minor bugfixes in several packages.
Almost all packages are updated to their latest version.
Packages gtkmm and gtksourceviewmm have been renamed to gtkmm2 and gtksourceviewmm2.
New packages are supported: libass, poco, and t4k_common.
This release fixes a download error caused by the pixman project (a sudden change of their URL scheme without proper redirects). That sort of thing should never happen!
The download mechanisms are improved.
A CMake toolchain file is provided to simplify cross-compiling projects which use CMake.
Support for Debian/Lenny is dropped.
Package gtk is renamed to gtk2.
Almost all packages are updated to their latest version.
New packages are supported: dbus, graphicsmagick, libical, liboauth, physfs, and vigra.
Note for boost::filesystem users:
Version 3 is a major revision
and now the default in 1.46.
This release fixes a checksum error caused by the atkmm project (a sudden change of their current source tarball). That sort of thing should never happen!
This release provides some improvements of the build system such as an automatic check for most of the requirements.
All packages are updated to their latest version.
New packages are supported: bfd, blas, cblas, dcmtk, ftgl, lapack, lcms1, mingw-utils, mxml, suitesparse and tinyxml.
This release provides lots of improvements to the build system as well as the documentation.
Support for OpenSolaris is dropped.
Almost all packages are updated to their latest version.
Many new packages are supported: atkmm, cairomm, cunit, faac, faad2, ffmpeg, gdk-pixbuf, glibmm, gtkglextmm, gtkmm, gtksourceview, gtksourceviewmm, imagemagick, lame, libsigc++, libvpx, matio, openal, opencore-amr, pangomm, pfstools, plotmm, sdl_sound and x264.
This release fixes download errors caused by the Qt project (a sudden change of their current source tarball).
Almost all packages are updated to their latest version.
This release fixes download errors caused by the MinGW project (a sudden change of their URL scheme without proper redirects). That sort of thing should never happen!
Almost all packages are updated to their latest version.
New packages are supported: libarchive, libgee and xvidcore.
This release switches back from TDM to the official GCC, thus supporting the current GCC 4.5.
The set of DirectX headers is improved and more complete.
The deadlock issues with Pthreads-w32 are fixed.
A static build of GDB is provided, i.e. a standalone "gdb.exe" that doesn't require any extra DLLs.
More packages are backed by test programs.
Many "sed hacks" are replaced by proper portability patches.
Almost all packages are updated to their latest version.
Many new packages are supported: fribidi, gc, gdb, gmp, gsl, gst-plugins-base, gst-plugins-good, gstreamer, gtkglext, guile, libcroco, libffi, liboil, libpaper, libshout, libunistring and xine-lib.
This release fixes some minor build issues, and contains a first small set of test programs to check the package builds.
The build rules are simplified by calling generators like Autotools and Flex, instead of patching the generated files.
Almost all packages are updated to their latest version.
Many new packages are supported: aubio, devil, directx, exiv2, fftw, freeimage, gsoap, id3lib, liblo, libpano13, librsvg, libsamplerate, muparser, openscenegraph, portaudio and sdl_pango.
This release contains a packaging bug. Please use release 2.12 instead.
This release adds support for many new packages: flac, libmad, libsndfile, sdl_net, speex, postgresql, freetds, openssl, plotutils, taglib, lcms, freeglut, xerces and zziplib.
Almost all packages are updated to their latest version.
In addition to the libraries some command line tools such as psql.exe are built, too.
The placements of logfiles, as well as many other build details, have been improved.
This release adds support for Qt, VMime and libmng.
The target triplet is updated to i686-pc-mingw32.
OpenMP support is enabled in GCC.
Almost all packages are updated to their latest version.
This release comes with a better look & feel by providing a highlevel overview of the build process.
The detailed build messages are stored into separate log files for each package, so parallel builds don't intermix them anymore.
The download URLs of SourceForge packages are adjusted to ensure that the selected SourceForge mirror is really used and not circumvalented via HTTP redirects to other mirrors.
Almost all packages are updated to their latest version.
The whole mingw-cross-env project has moved to Savannah. So all URIs have changed, but the old URIs redirect to the new locations seamlessly.
Everyone is invited to join the freshly created project mailing list.
This release provides an improved version recognition for SourceForge packages. SourceForge changed their page layout in a way that makes it much harder to identify the current version of a package.
Additionally, almost all packages are updated to their latest version.
This release contains some portability fixes which allow it to run on a wider range of systems such as Frugalware.
The documentation and website are completely revised.
New packages such as CppUnit, libUsb, NSIS, Popt, SQLite and Theora are supported.
Almost all packages are updated to their latest version.
A new command "make download" is implemented.
This release fixes a download error caused by the MinGW project. They suddenly changed the names of their source tarballs. That sort of thing should never happen!
This release also contains some bugfixes which allow it to run on a wider range of systems.
All downloaded files are now verified by their SHA-1 checksums.
New versions of various packages are supported.
This release provides many new libraries such as wxWidgets, GTK+ and OpenEXR.
In addition, new versions of various packages are supported.
This release fixes some serious build problems on FreeBSD and MacOS-X.
The Makefile has a new target "clean-pkg" and allows to be called from a separate build directory via "make -f .../Makefile".
Some new versions of the packages are supported, especially GCC-4.3 by switching from MinGW GCC to TDM-GCC.
This release fixes some minor build problems.
It also supports some new packages and some newer versions of the already supported packages.
Parallelization is now disabled by default.
This release fixes a download error caused by the GDAL project. They suddenly changed their download URLs. That sort of thing should never happen!
In addition, some newer versions of various packages are supported.
There is also a small compatibility fix for OS X.
The shell script has been rewritten as Makefile and supports partial builds and parallel builds.
As usual, this release also supports some new packages and some newer versions of the already supported packages.
This release now includes a tutorial by Hans Bezemer and has improved compile options of FLTK. As usual, it supports some newer versions of the libraries.
At the request of its author, libowfat is no longer supported from this release on.
The script now uses a specific SourceForge mirror instead of randomly chosen ones, because the download phase often stumbled on some very slow mirrors.
A sudden change in the download URLs of GEOS made the automatic download fail. Such changes should never happen! But it happened, and this quick release is an attempt to limit the damage.
This release also supports some newer versions of the libraries including support for fontconfig-2.5.0.
This release is a switch from gcc-3 to gcc-4. It also supports a new library and some newer versions of the already supported libraries.
This release is the result of the public attention the release 1.0 got. It contains many improvements suggested by its first users, and adds support for many new libraries.
Thanks to Rocco Rutte who contributed many code snippets.
This first release has been created in a 7-day-sprint.