0457d6914a
* plug-ins/makefile.msc: New file.
* plug-ins/*/*.c (Well, not really all files, but many):
Portability fixes. Include config.h, and guard inclusion of POSIX
and Unix headers like <unistd.h>, <dirent.h> and
<sys/time.h>. Include <string.h> if functions from it are
used. Use g_ntohl() and g_htonl() insteead of ntohl() and htonl(),
thus no need to include <netinet/in.h>. Include <io.h> on Win32
when using open/read/write (which actually are defined as
_open/_read/_write by glib.h). Define S_* macros if necessary on
Win32. Define rint() and M_PI if necessary (these definitions
should be factored out somewhere, no sense repeating them in lots
of files). Open files in binary mode when needed.
* plug-ins/FractalExplorer/FractalExplorer.c: Use
g_malloc()/g_free(). Use g_strdup_printf().
* plug-ins/dbbrowser/dbbrowser.c: No need to include <X11/Xlib.h>.
* plug-ins/destripe/destripe.c: Guard use of SIGBUS.
* plug-ins/{flame/flame,hrz/hrz,pnm/pnm}.c: No need to check for
NULL returns from g_malloc() and g_new() as they abort on failure.
Use g_strdup_printf().
* plug-ins/gz/gz.c: Win32 version of running the subprocess.
* plug-ins/hrz/hrz.c: Win32 version. Use more generic tests for
non-Unix (OS/2 and Win32), for instance HAVE_MMAP.
* plug-ins/script-fu/interp_slib.c: Win32 version of myruntime().
* plug-ins/script-fu/interp_sliba.c: Handle \\ (escaped backslahsh).
* plug-ins/script-fu/script-fu-console.c: Bypass on Win32.
* plug-ins/script-fu/script-fu-scripts.c: Portability fixes. Use
g_strdup_printf() instead of separate malloc() and sprintf(). Use
g_strescape() for strings being passed to Scheme. Some Win32-only
stuff.
25 lines
980 B
Plaintext
25 lines
980 B
Plaintext
This is an unstable version of the GIMP, intended for developers
|
|
only. Even more so the Win32 port.
|
|
|
|
For more information about the port or GLib, GTk+ and the GIMP to
|
|
native Windows, and pre-built binary packages, see
|
|
http://www.iki.fi/tml/gimp/win32/ or
|
|
http://www.gimp.org/~tml/gimp/win32/
|
|
|
|
To build the GIMP on Win32, you will need (for now) the Microsoft
|
|
compiler. Eventually gcc (egcs) on cygwin will also be supported, but
|
|
without the produced executables depending on the cygwin dll (gcc
|
|
-mno-cygwin).
|
|
|
|
First, build in the libgimp directory, then in tools/gcg, then in app,
|
|
plug-ins, and finally in modules. Check the makefile.msc files in said
|
|
directories.
|
|
|
|
The current build setup for Windows is a mess, with complex
|
|
hand-maintained makefiles. I know. Adding parallel makefiles for gcc
|
|
isn't going to make it any better. On the other hand, I don't think
|
|
using the Unix style configuration mechanism (under cygwin) is quite
|
|
feasible, either.
|
|
|
|
--Tor Lillqvist <tml@iki.fi>
|