Back to the Gaia-SINS home page

Index of contents

Setting up the MinGW 64 environment

MinGW 64 is an open source C/C++ compiler based on the popular gcc; basically, it is intended to generate executables for Windows 64 bit.

We'll suppose that you already have a basic familiarity with standard MinGW 32 + MSYS: MinGW 64 is more or less the same, but acting (more or less) as a cross-compiler.
This practically means that you can build 64 bit executables on any Win32 platform: but obviously any 64 bit program requires some Windows 64 platform to be executed.

The standard build tool-chain [originally developed for Linux] natively supports cross-compilers: and this works under Windows as well, e.g. using MinGW 64.
As you surely already know, the standard build procedure is the following one:

./configure
make
make install

Using the MinGW 64 cross-compiler is the same of using standard MinGW32: but in this case you are required to always specify the following ./configure argument:

./configure --host=x86_64-w64-mingw32
make
make install

The above --host directive is enough for ./configure to intend that a cross-compilation is required: and that the intended target is Windows 64 bit.
There are many different ways to deploy MinGW 64 (this including cross-compiling on Linux or Cygwin).
After some careful preliminary testing, I choosed the following one because it appairs the most straightforward: mingw disk layout
Once I decided the most appropriate disk layout, I duly started installing MinGW 64 on Windows 7 Pro 64 bit:

PostInstallation tasks

Step #1: carefully check the C:\msys64\etx\fstab file; it must contain the following row: (this will automatically mount C:\MinGW64 as /mingw)
C:/MinGW64 /mingw

Step #2: a dangerous issue exists: the MinGW 64 own MSYS is someway broken (as I painfully discoverd by trial and error ...): the C:\msys64\bin\find.exe executable is badly missing.
Unhappily enough, Windows has its own FIND.EXE (and it's a completely different thing from the Linux find): this may cause several builds to misteriously fail ... but now you are well aware of this dangerous pitfall. You simply have to manually pick find.exe from the standard MinGW 32 / MSYS installation, then copying this executable file into C:\msys64\bin.

Step #3: the cross-compiler tool-chain seems to be a little bit confused about strip real name: this simple trick seems to definitively resolve any related issue.
cp /mingw/bin/x86_64-w64-mingw32-strip.exe /mingw/bin/strip.exe

Preparing to use PKG-CONFIG:

You simply have to follow the same identical procedure already explained for standard MinGW 32 + MSYS

Learming to identify 32 bit and 64 bit exacutables

32 bit binaries file iconv.exe
PE32 executable for MS Windows (console) Intel 80386 32-bit

file libiconv-2.dll
PE32 executable for MS Windows (DLL) (console) Intel 80386 32-bit
64 bit binaries file iconv.exe
PE32+ executable for MS Windows (console) Mono/.Net assembly

file libiconv-2.dll
PE32+ executable for MS Windows (DLL) (console) Mono/.Net assembly

Setting up Windows own (SYSTEM) libraries

Some apps (and libraries) require to be actually linked against MS Windows system libraries. And this is a really puzzling task using MinGW 64.

Very shortly explained: the standard GCC tool-chain has the ability to link both .DLL dynamic libraries and .a static libraries.
When Windows own system libraries are required, this isn't at all an issue for MinGW 32:
  • any required system .dll is surely installed (usually on C:\Windows\System32)
  • the corresponding .a static libraries are shipped by MinGW itself (and actually simply are stubs pointing to the corresponding DLL)
But when using MinGW 64 a catastrophical issue arises:
  • on Windows 64 bit platforms C:\Windows\System32 is somehow wizardry cursed (as I discovered in the most painfull way ...)
  • when a 32 bit executable attemptes to get any DLL from C:\Windows\System32 then the 32 bit DLL will be found
  • and when a 64 bit executable attemptes to get any DLL from C:\Windows\System32 then the 64 bit DLL will be found
  • sadly, there is absolutely no way to explicity identify (by path) which one version do you really intend to access.
    a damned automamagical trick, acting as a black magic spell decides for you what are you loocking for: and there is no way to circumvent this odd behaviour.
    you can get further details from this Wikipedia article: SysWOW64
  • unhappily, the MinGW 64 tool-chain actually is a cross-compiler: it actually generates 64 bit executables, but the tool-chain tools themselves are 32 bit
  • and accordingly to this, the GCC linker will always fail when some system DLL is required, simply because it will inexorably found the corresponding 32 bit DLL instead ...
    obviously not at compatible with a 64 bit executable.

How to circumvent this dangerous pitfall

Once we have identified the reasons causing the above link failure, caring any nursing isn't too much difficult.
  • we simply have to copy any required Windows own system DLL on some sane and safe location, i.e. on some normal, not cursed) directory, possibly included within the linker search path.
  • all this isn't at all difficult: you simply have to use Windows own tools (e.g. GUI copy & paste, or the command copy from the command shell).
    Windows own tools are 64 bit executables, and will consequently magically pick up the 64 bit version of any DLL from C:\Windows\System32
  • I've personally choosen C:\MinGW64\x86_x64-w64-mingw32\lib (corresponding to /mingw/x86_64-w64-mingw32-lib) as my default location.
  • The DLLs required to build SpatiaLite and friends are: gdi32.dll, msimg32, ws2_32.dll, crypt32.dll and Wldap32.dll
    Please note well: you must rename theam respectively as: libgdi32.dll, libmsimg32, libws2_32.dll, libcrypt32.dll and libwldap32.dll

Cleaning the system libraries

MinGW 64 seems to generate absolutely crazy .la files, and this may cause many problems.
The cause has been identified in few system libraries defining crazy paths in their .la files;
and such odd definitions will then propagate polluting any further .la file created by MinGW 64.

So you have to manually apply the following patches to avoid any possible further issue:
  • go to the C:\MinGW64\x86_64-w64-mingw32\lib directory.
  • identify and open any .la file you'll find using some text editor.
  • for each .la file you must apply the following patches:
    • search for a line starting with: dependency_libs=
      ignore (delete) any crazy value
      replace with: dependency_libs='-L/mingw/x86_64-w64-mingw32/lib'
    • search for a line starting with: libdir=
      ignore (delete) any crazy value
      replace with: libdir='/mingw/x86_64-w64-mingw32/lib'
    • save and exit
  • carefully check if you really have successfully applied any required patch.

All right: we are now ready to start creating our Windows 64 bit software. Let's go !

Be warned: building on MinGW 64 is more or less the same as building on MinGW 32: anyway here and there some further patch is absolutely required.

Please, carefully read and verbatim follow any given instruction.

Step 1) building libiconv

libiconv is the standard GNU library supporting locale charsets.
Required by: libspatialite, spatialite-tools

Building under Windows is not too much difficult. cd libiconv-1.14
./configure --host=x86_64-w64-mingw32
make
make install-strip

Anyway, this will simply build and install the DLL: a further step is required in order to get the static library as well.

make distclean
./configure --host=x86_64-w64-mingw32 --disable-shared
make
make install-strip

Now you've built and installed both the static library and the DLL.
However the above process has installed badly misconfigured libcharset.la and libiconv.la files
(which are required to build other libraries in the following steps).
So in order to get a properly configured libiconv you have to accomplish a further operation:

Step 2) building libz

libz is a popular library implementing Deflate, i.e. the compression algorithm used by gzip and Zip.
Depends on: nothing
Required by: libpng, libtiff, ...

Building under Windows is quite easy, but requires to pay some attenction. A very simple patch is required: you must first edit the zlib-1.2.5/win32/Makefile.gcc file:
38c38
< PREFIX =
---
> PREFIX = x86_64-w64-mingw32-

After applying the above patch you are now to build zlib:

cd zlib-1.2.5
make -f win32/Makefile.gcc

Now you simply have to manually copy the following files:

cp zlib1.dll /usr/local/bin
cp zconf.h zlib.h /usr/local/include
cp libz.a /usr/local/lib
cp libzdll.a /usr/local/lib/libz.dll.a

All this will build and install both the static library and the DLL as well.
Anyway this process will not generate the libz.la file (which is required to build libtiff in one of the following steps.
So in order to get a fully installed libz you have to accomplish a further operation:

Step 3) building libjpeg

libjpeg is a popular library supporting the JPEG image compression.
Depends on: nothing
Required by: libtiff, libgaiagraphics

Important notice: you can now choose between two alternative implementations: Building the one or the other under Windows is absolutely a plain and easy task.

How-to-build libjpeg-turbo

Please note: the NASM assembler is absolutely required: if you don't have it already installed on your system, you can download and install now. cd libjpeg-turbo-1.1.90
./configure --host=x86_64-w64-mingw32 --prefix=/usr/local
make
make install-strip

This will build and install both the static library and the DLL as well.

How-to-build libjpeg

cd jpeg-8b
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 4) building libpng

libpng is a popular library supporting the PNG image compression.
Depends on: libz
Required by: libgaiagraphics

Building under Windows is absolutely a plain and easy task. cd libpng-1.5.7
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

Important notice: you have to properly set the shell environment in order to retrieve the already installed libz; this is the duty of the two above export directives.
This will build and install both the static library and the DLL as well.

Important notice #2: in order to get ./configure support you must absolutely download the .tar.gz, because the .zip doesn't supports it.

Step 5) building libtiff

libtiff is a popular library supporting the TIFF image format.
Depends on: libz, libjpeg
Required by: libgaiagraphics

Building under Windows is absolutely a plain and easy task. cd tiff-3.9.5
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

Important notice: you have to properly set the shell environment in order to retrieve the already installed libz; this is the duty of the two above export directives.

This will build and install both the static library and the DLL as well.

Step 6) building libproj

libproj is a library supporting coordinate's transformation between different Reference Systems [PROJ.4]
Depends on: nothing
Required by: libgeotiff, libspatialite, spatialite-tools

Building under Windows is an easy task. cd proj-4.7.0
./configure --host=x86_64-w64-mingw32 --without-mutex
make
make install-strip

Important notice: may well be you'll get the following fatal errors:

pj_mutex.c:167: error: redefinition of 'pj_acquire_lock'
pj_mutex.c:65: error: previous definition of 'pj_acquire_lock' was here
pj_mutex.c:181: error: redefinition of 'pj_release_lock'
pj_mutex.c:75: error: previous definition of 'pj_release_lock' was here
pj_mutex.c:192: error: redefinition of 'pj_cleanup_lock'
pj_mutex.c:82: error: previous definition of 'pj_cleanup_lock' was here
pj_mutex.c:206: error: redefinition of 'pj_init_lock'
pj_mutex.c:91: error: previous definition of 'pj_init_lock' was here

in such an evenience you have to edit the -/src/pj_mutex.c source as follows:

33c33
< #ifndef _WIN32
---
> #if defined (_WIN32) && !defined(__MINGW32__)
40c40
< #ifndef _WIN32
---
> #if defined (_WIN32) && !defined(__MINGW32__)

Step 7) building libgeotiff

libgeotiff is a library supporting the GeoTIFF raster format
Depends on: libtiff, libproj
Required by: libgaiagraphics

Building under Windows is an easy task. cd libgeotiff-1.3.0
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --enable-incode-epsg
make
make install-strip

Important notice: it doesn't seem possible to build as a DLL using MinGW + MSYS. AFAIK, there is no way to do such a thing.
So you have to manually apply the following patch to circumvent this issue. Edit the /usr/local/lib/libgeotiff.la file as follows:

10c10
< library_names=''
---
> library_names='libgeotiff.a'

Step 8) building libgeos

libgeos is a library representing a C++ porting of JTS [Java Topology Suite].
Depends on: nothing
Required by: libspatialite, spatialite-tools

This library really is an huge and complex piece of software; building on Windows is an incredibly time consuming task. cd geos-3.3.2
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 9) building libexpat

libexpat is a well known standard library supporting XML parsing.
Depends on: nothing
Required by: libfontconfig, spatialite-tools, ...

Building under Windows really is a piece-of-cake. cd expat-2.0.1
./configure --host=x86_64-w64-mingw32

Important notice: before attempting to start compiling you are required to manually apply the following patch:
(not at all elegant, but fully effective); so edit the C:\MinGW64\x86_64-w64-mingw32\include\process.h header:
165c165:
------------
< int __cdecl execv(const char *_Filename,char *const _ArgList[]) __MINGW_ATTRIB_DEPRECATED_MSVC2005;
---
> int __cdecl execv(const char *_Filename,const char * _ArgList[]) __MINGW_ATTRIB_DEPRECATED_MSVC2005;
and now you are really ready to start building expat (you can recover back again the above change once you've terminated):

make
make install

This will build and install both the static library and the DLL as well.

Step 10) building FreeXL

FreeXL is an utility library implementing read-access for Excel (.xls) spreadsheets
Depends on: libiconv
Required by: spatialite-tools, libspatialite, spatialite-gui

Building under Windows is an easy task. cd freexl-1.0.0b
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 11) building libspatialite

libspatialite is the main core of SpatiaLite
Depends on: libiconv, libproj, libgeos
Required by: spatialite-tools, librasterlite

Building under Windows is an easy task. cd libspatialite-amalgamation-3.0.0-stable
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --target=mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 12) building spatialite-tools

spatialite-tools the SpatiaLite command-line management tools
Depends on: libiconv, libproj, libgeos, libspatialite, libexpat
Building under Windows is an easy task. First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

After this you are now ready to build as usual:

cd spatialite-tools-3.0.0-stable
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --target=mingw32
make
make install-strip

Please note: following the above method you'll get dynamically linked tools [i.e. depending on DLLs].
If you wish instead to build statically linked tools [i.e. self contained, not depending on DLLs], you must first
manually edit the Makefile-static-MinGW file as follows:
< GG = g++
< CC = gcc
---
> GG = x86_64-w64-mingw32-g++
> CC = x86_64-w64-mingw32-gcc
after this you are now ready to build your statically linked tools:

mkdir static_bin
make -f Makefile-static-MinGW
cp static_bin/* /usr/local/bin

Step 13) building wxWidgets MSW

wxWidgets is a popular widgets library, supporting GUI in a cross-platform fashion; MSW is the specific porting supporting Windows.
Depends on: nothing
Required by: spatialite-gui, spatialite-gis

This library really is an huge and complex piece of software; building on Windows is an incredibly time consuming task, but is quite plain and easy. cd wxMSW-2.8.12
mkdir msw_build
cd msw_build
export "CFLAGS=-I/usr/local/include"
export "CXXFLAGS=-I/usr/local/include -fpermissive" [this directive is absolutely required to skip some blocking errors]
export "LDFLAGS=-L/usr/local/lib"
../configure --host=x86_64-w64-mingw32 --disable-shared --disable-debug \
    --disable-threads --enable-monolithic --enable-unicode \
    --without-expat --without-regex --enable-graphics_ctx

Please note: the wxMSW ./configure is highly configurable: you must apply exactly the above settings.
Anyway, when ./configure stops, it's a good practice to check if the final report looks exactly like this:

Configured wxWidgets 2.8.12 for `x86_64-w64-mingw32'

  Which GUI toolkit should wxWidgets use?                 msw
  Should wxWidgets be compiled into single library?       yes
  Should wxWidgets be compiled in debug mode?             no
  Should wxWidgets be linked as a shared library?         no
  Should wxWidgets be compiled in Unicode mode?           yes
  What level of wxWidgets compatibility should be enabled?
                                       wxWidgets 2.4      no
                                       wxWidgets 2.6      yes
  Which libraries should wxWidgets use?
                                       jpeg               sys
                                       png                sys
                                       regex              no
                                       tiff               sys
                                       zlib               sys
                                       odbc               no
                                       expat              no
                                       libmspack          no
                                       sdl                no

now, when ./configure stops, you have to continue as usual:

make
make install-strip

Important notice: wxWidgets is now configured for any further usage: but unhappily it assumes being on Win32, and this is obviously wrong.
So you must manually adjust the wx-config script (/usr/local/bin/wx-config) as follows:

Step 14) building libfreetype

libfreetype is a standard library supporting TrueType fonts.
Depends on: nothing
Required by: libcairo, ...

Building under Windows is an easy task. cd freetype-2.4.8
./configure --host=x86_64-w64-mingw32
make
make install

This will build and install both the static library and the DLL as well.

Step 15) building libfontconfig

libfontconfig is a standard library supporting font customization and configuration.
Depends on: libexpat, libfreetype, libiconv
Required by: libcairo, ...

Building under Windows is an easy task. cd fontconfig-2.8.0
export "CFLAGS=-I/usr/local/include -DLIBICONV_STATIC"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --disable-docs
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 16) building libpixman

libpixman is the standard library implementing pixel manipulation for Cairo.
Depends on: nothing
Required by: libcairo, ...

Building under Windows is an easy task.
First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

All right, your system configuration is ready to build pixman, so you can now: cd pixman-0.24.0
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 17) building libcairo

libcairo is a very popular graphics library.
Depends on: libpixman, libfreetype, libfontconfig, libpng
Required by: libgaiagraphics, ...

Building under Windows is a little bit harder than usual.
First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

All right, your system configuration is ready to build libcairo, so you can now: cd cairo-1.10.2
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --disable-pthread
make
make install-strip

Important notice: you'll probably get a fatal error at some time during the compilation:
to resolve this issue you should manually edit the cairo-1.10.2/src/cairo.c source:
near line 149:
------------
< };
< #include <assert.h>
<
< /**
<  * _cairo_error:
---
> };
> #include <assert.h>
>
> #ifdef __MINGW32__
> #define ffs __builtin_ffs
> #endif
>
> /**
>  * _cairo_error:

This will build and install both the static library and the DLL as well.

Step 18) building libgaiagraphics

libgaiagraphics is a common utility library supporting graphics rendendering
Depends on: libjpeg, libpng, libtiff, libgeotiff, libcairo

Required by: spatialite-gui [next-to-come releases of librasterlite and spatialite-gis]

Building under Windows is an easy task.
First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

All right, your system configuration is ready to build libgaiagraphics, so you can now: cd libgaiagraphics-0.4b
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --target=mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Step 19) building spatialite_gui

spatialite_gui the SpatiaLite GUI user-friendly tool
Depends on: libspatialite, wxWidgets, libgaiagraphics
Building under Windows is an easy task. First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

After this you are now ready to build as usual:

cd spatialite_gui-1.5.0-stable
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

Please note: following the above method you'll get a dynamically linked GUI tool [i.e. depending on DLLs].
If you wish instead to build a statically linked GUI tool [i.e. self contained, not depending on DLLs], you must first
manually edit the Makefile-static-MinGW file and then insert the following line at the very beginning:
> CXX = x86_64-w64-mingw32-g++
after this you are now ready to build your statically linked tool:

mkdir static_bin
make -f Makefile-static-MinGW
cp static_bin/* /usr/local/bin

Step 20) building RasterLite

librasterlite is a library allowing to store huge raster coverages within a SpatiaLite DB
Depends on: libjpeg, libpng, libtiff, libgeotiff, libspatialite

Required by: spatialite-gis

Building under Windows is an easy task.
First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

All right, your system configuration is ready to build librasterlite, so you can now: cd librasterlite-1.1b
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library, the DLL and the supporting tools as well.

Please note: following the above method you'll get dynamically linked tools [i.e. depending on DLLs].
If you wish instead to build statically linked tools [i.e. self contained, not depending on DLLs], you must first
manually edit the Makefile-static-MinGW file as follows:
< GG = g++
< CC = gcc
---
> GG = x86_64-w64-mingw32-g++
> CC = x86_64-w64-mingw32-gcc
after this you are now ready to build your statically linked tools:

mkdir static_bin
make -f Makefile-static-MinGW
cp static_bin/* /usr/local/bin

Step 21) building libharu

libharu [aka libhpdf] is a library supporting output to PDF documents
Depends on: libpng

Required by: spatialite-gis

Building under Windows is an easy task: cd libharu-2.2.1
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Important notice: libharu 2.2.1 isn't fully compatible with recent libpng versions;
you are required to manually edit the -/src/hpdf_image_png.c source as follows:

replace any occurrence of: info_ptr->height as: getHeight(info_ptr)
replace any occurrence of: info_ptr->width as: getWidth(info_ptr)
replace any occurrence of: info_ptr->bit_depth as: getBitDepth(info_ptr)
replace any occurrence of: info_ptr->color_type as: getColorType(info_ptr)

Step 22) building spatialite_gis

spatialite_gis a minimalistic GIS built on the top of SpatiaLite and RasterLite
Depends on: libspatialite, wxWidgets, librasterlite
Building under Windows is an easy task. First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

After this you are now ready to build as usual:

cd spatialite_gis-1.0.0c
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32 --target=mingw32
make
make install-strip

Please note: following the above method you'll get a dynamically linked GUI tool [i.e. depending on DLLs].
If you wish instead to build a statically linked GUI tool [i.e. self contained, not depending on DLLs], you must first
manually edit the Makefile-static-MinGW file and then insert the following line at the very beginning:
> CXX = x86_64-w64-mingw32-g++
Then you must delete any reference to: -lctl3d32
after this you are now ready to build your statically linked tool:

mkdir static_bin
make -f Makefile-static-MinGW
cp static_bin/* /usr/local/bin

Step 23) building OpenSSL

OpenSSL is a well known standard library supporting SSL, i.e. the encrypted HTTPS web protocol.
Depends on: nothing
Required by: libcurl

Building under Windows is a little bit difficult, and requires to pay close attention.
The configure script isn't at all a standard one: please read carefully the following instructions.
tar zxvf openssl-1.0.0e.tar.gz
cd openssl-1.0.0e
./Configure mingw64 --prefix=/usr/local shared

Several manual adjustments are now required; you must first edit openssl-1.0.0e/Makefile:
62c62
< CC= gcc
---
> CC= x86_64-w64-mingw32-gcc
69,71c69,71
< AR= ar $(ARFLAGS) r
< RANLIB= /c/MinGW/bin/ranlib.exe
< NM= nm
---
> AR= x86_64-w64-mingw32-ar $(ARFLAGS) r
> RANLIB= x86_64-w64-mingw32-ranlib.exe
> NM= x86_64-w64-mingw32-nm
75c75
< MAKEDEPPROG= gcc
---
> MAKEDEPPROG= x86_64-w64-mingw32-gcc

After applying the above patches you are now to build OpenSSL:

export "CROSS_COMPILE=x86_64-w64-mingw32-"
make
make install

This will build and install both the static libraries and the DLLs as well.

Step 24) building libcurl [not strictly required by the current SpatiaLite version !!!]

libcurl is a well known library supporting URLs (networking, web protocols)
Depends on: libz, OpenSSL
Required by: ?

Building under Windows is an easy task. First of all, you must check if you've already installed pkg-config.exe
If not, please read the above instructions

And now you must set the PKG_CONFIG_PATH as appropriate:

export "PKG_CONFIG_PATH=/usr/local/lib/pkgconfig"

After this you are now ready to build as usual:

cd curl-7.23.1
export "CFLAGS=-I/usr/local/include"
export "LDFLAGS=-L/usr/local/lib"
./configure --host=x86_64-w64-mingw32
make
make install-strip

This will build and install both the static library and the DLL as well.

Back to the Gaia-SINS home page