Building Ekiga for Windows
From Ekiga
Windows-related links: Building Ekiga for Windows → Pre-built setup programs → Execute and Debug
The current process to build Ekiga for Windows is to generate a 32bit program (win32) through cross-building on a GNU/Linux system. Currently, there is no native Windows build of Ekiga available. In other words, you cannot build Ekiga for Windows on a Windows system.
We are interested in any feedback for cross-compilation and execution of ekiga on windows.
Contents |
Dependencies
You need an installed, working version of Minimalist GNU for Windows (mingw) together with its binutils and runtime libraries, and some other libraries/programs. On a debian system you can install them via apt-get:
apt-get install gcc-mingw32 mingw32-binutils mingw32-runtime nsis apt-get install build-essential make automake bison flex zip unzip git-core subversion apt-get install gnome-common gnome-doc-utils libgtk2.0-dev xmlto yasm libgconf2-dev libavahi-glib-dev libavahi-client-dev intltool
Notes:
- you need a version of mingw32-runtime >= 3.15, while debian unstable has version 3.13 as of April 2010; you can download 3.15 from Michael's site for example
Downloading building program
Create an empty directory and save into it the following file under the name Makefile:
- for stable version (use this one if you do not know which one): http://git.gnome.org/browse/ekiga/plain/win32/Makefile?h=gnome-2-26
- for unstable version: http://git.gnome.org/browse/ekiga/plain/win32/Makefile. Currrently, there are three glitches for unstable version:
- gtk 2.20 has not yet an "official" repository; remove the '#' in the Makefile if you want to use Thierry Simonnet's gtk installer
- video is shown in the roster instead of its usual place
- you must use RELEASE=0 (see below), since there is no unstable Ekiga release currently
Compiling instructions
1. Now you execute the automated download process that gets ekiga sources and its required libraries (such as ptlib, opal, theora and speex) from the Internet. Go to the directory where you saved the Makefile file, and execute:
make update-sources RELEASE=0
(or, if you prefer the latest release, make update-sources).
Be patient. Some file downloading and git/svn checkouts will happen. Depending on your network speed, it might look for some minutes as if the make process stalled.
2. Then start the build process by simply executing:
make RELEASE=0
(or make for latest release) (you must have executed the similar command at the previous step too).
You can add DEBUG=1 if you wish to compile with debug information (-g when compiling everything, use of DEBUG=1 for ptlib, opal and ekiga, and no executable stripping).
This step compiles all the libraries and finally ekiga itself as usually, but through mingw32 (note that even if these libraries might be installed on your GNU/Linux computer, they are useless for cross-build for the Win32 target). It also puts together all the libraries and ekiga in a single file ekiga-setup.exe.
Your cross-compiled windows version is now located in dist directory.
Execution
Execute dist/ekiga-setup...exe on a Windows system.
(Note: If you have GTK+2 >=2.16 runtime environment already installed, you can instead, if you wish, transfer dist/Ekiga directory to a win32 system and simply run ekiga.exe from it.)
See also
- If you have 20 minutes, help us with translating the installation program for windows, instructions are at http://git.gnome.org/browse/ekiga/plain/win32/nsisinstaller/language_files/english.nsh , list of already available translations: http://git.gnome.org/browse/ekiga/tree/win32/nsisinstaller/language_files

