• gdImageStringTTF - scalable, rotatable, anti-aliased, TrueType strings using the FreeType library, but only if libttf is found by configure. We do not provide TrueType fonts. Obtaining them is entirely up to you.
• gdImageColorResolve - an efficient alternative for the common code fragment:

  
        if ((color=gdImageColorExact(im,R,G,B)) < 0)
            if ((color=gdImageColorAllocate(im,R,G,B)) < 0)
                color=gdImageColorClosest(im,R,G,B);
  

Also in this release the build process has been converted to GNU autoconf/automake/libtool conventions so that both (or either) static and shared libraries can be built.

What's new in version 1.6.1?

Unlike gd 1.6, users should have no trouble linking with gd 1.6.1 if they follow the instructions and install all of the pieces. However, If you get undefined symbol errors, be sure to check for older versions of libpng in your library directories!

What's new in version 1.6?

Support for 8-bit palette PNG images has been added. Support for GIF has been removed. This step was taken to completely avoid the legal controversy regarding the LZW compression algorithm used in GIF. Unisys holds a patent which is relevant to LZW compression. PNG is a superior image format in any case. Now that PNG is supported by both Microsoft Internet Explorer and Netscape (in their recent releases), we highly recommend that GD users upgrade in order to get well-compressed images in a format which is legally unemcumbered.

What's new in version 1.5?

New GD2 format

An improvement over the GD format, the GD2 format uses the zlib compression library to compress the image in chunks. This results in file sizes comparable to GIFs, with the ability to access parts of large images without having to read the entire image into memory.

This format also supports version numbers and rudimentary validity checks, so it should be more 'supportable' than the previous GD format.

Re-arranged source files

gd.c has been broken into constituant parts: io, gif, gd, gd2 and graphics functions are now in separate files.

Extended I/O capabilities.

The source/sink feature has been extended to support GD2 file formats (which require seek/tell functions; seek must return 1 for success, 0 for failure), and to allow more general non-file I/O.

Better support for Lincoln Stein's Perl Module

The new gdImage*Ptr function returns the chosen format stored in a block of memory. This can be directly used by the GD perl module.

Added functions

gdImageCreateFromGd2Part - allows retrieval of part of an image (good for huge images, like maps),
gdImagePaletteCopy - Copies a palette from one image to another, doing it's best to match the colors in the target image to the colors in the source palette.
gdImageGd2, gdImageCreateFromGd2 - Support for new format
gdImageCopyMerge - Merges two images (useful to highlight part of an image)
gdImageCopyMergeGray - Similar to gdImageCopyMerge, but tries to preserve source image hue.
gdImagePngPtr, gdImageJpegPtr, gdImageWBMPPtr, gdImageGdPtr, gdImageGd2Ptr - return memory blocks for each type of image.
gdImageCreateFromPngCtx, gdImageCreateFromGdCtx, gdImageCreateFromGd2Ctx, gdImageCreateFromGd2PartCtx - Support for new I/O context.

What's new in version 1.4?

Fixed polygon fill routine (again)

Thanks to Kirsten Schulz, version 1.4 is able to fill numerous types of polygons that caused problems with previous releases, including version 1.3.

Support for alternate data sources

Programmers who wish to load a GIF from something other than a stdio FILE * stream can use the new gdImageCreateFromPngSource function.

Support for alternate data destinations

Programmers who wish to write a GIF to something other than a stdio FILE * stream can use the new gdImagePngToSink function.

More tolerant when reading GIFs

Version 1.4 does not crash when reading certain animated GIFs, although it still only reads the first frame. Version 1.4 also has overflow testing code to prevent crashes when reading damaged GIFs.

What's new in version 1.3?

Non-LZW-based GIF compression code

Version 1.3 contained GIF compression code that uses simple Run Length Encoding instead of LZW compression, while still retaining compatibility with normal LZW-based GIF decoders (your browser will still like your GIFs). LZW compression is patented by Unisys. We are currently reevaluating the approach taken by gd 1.3. The current release of gd does not support this approach. We recommend that you use the current release, and generate PNG images. Thanks to Hutchison Avenue Software Corporation for contributing the RLE GIF code.

8-bit fonts, and 8-bit font support

This improves support for European languages. Thanks are due to Honza Pazdziora and also to Jan Pazdziora . Also see the provided bdftogd Perl script if you wish to convert fixed-width X11 fonts to gd fonts.

16-bit font support (no fonts provided)

Although no such fonts are provided in the distribution, fonts containing more than 256 characters should work if the gdImageString16 and gdImageStringUp16 routines are used.

Improvements to the "webpng" example/utility

The "webpng" utility is now a slightly more useful application. Thanks to Brian Dowling for this code.

Corrections to the color resolution field of GIF output

Thanks to Bruno Aureli.

Fixed polygon fills

A one-line patch for the infamous polygon fill bug, courtesy of Jim Mason. I believe this fix is sufficient. However, if you find a situation where polygon fills still fail to behave properly, please send code that demonstrates the problem, and a fix if you have one. Verifying the fix is important.

Row-major, not column-major

Internally, gd now represents the array of pixels as an array of rows of pixels, rather than an array of columns of pixels. This improves the performance of compression and decompression routines slightly, because horizontally adjacent pixels are now next to each other in memory. This should not affect properly written gd applications, but applications that directly manipulate the pixels array will require changes.

To use gd, you will need an ANSI C compiler. All popular Windows 95 and NT C compilers are ANSI C compliant. Any full-ANSI-standard C compiler should be adequate. The cc compiler released with SunOS 4.1.3 is not an ANSI C compiler. Most Unix users who do not already have gcc should get it. gcc is free, ANSI compliant and a de facto industry standard. Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library, and the libpng library. As of version 1.6.2, you can draw text using antialiased TrueType fonts if you also have the libttf library installed, but this is not mandatory. zlib is available for a variety of platforms from the zlib web site. libpng is available for a variety of platforms from the PNG web site.

You will also want a PNG viewer, if you do not already have one for your system, since you will need a good way to check the results of your work. Netscape 4.04 and higher, and Microsoft Internet Explorer 4.0 or higher, both support PNG. Not every PNG-compatible viewer supports alpha channel transparency, which is why gd 2.0.2 and above do alpha blending in the library by default; it is possible to turn on the saving of alpha channel information to the file instead.

How do I get gd?

Binaries (DLL for Windows programmers):

• .ZIP File of DLL, Headers, Et Cetera

Source Code:

• Gzipped Tar File (Unix)
• .ZIP File of SOURCE CODE (Windows)

How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file makemsvcimport.bat to make a bgd.lib import library corresponding to the provided bgd.dll. Copy bgd.dll to your application directory, or to your Windows sytem directory. In the settings of your MSVC project, you MUST choose the "multithreaded DLL" library option under "code generation." mingw32 and cygwin users can simply link with the provided libbgd.a stub library in order to use the DLL.

In order to build gd, you must first unpack the archive you have downloaded. If you are not familiar with tar and gunzip (Unix) or ZIP (Windows), please consult with an experienced user of your system. Sorry, we cannot answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix

./configure

NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN /usr/local/lib and the include files are installed in /usr/local/include. IF YOU ARE UPGRADING, you may wish to use:

./configure --prefix=/usr

Rather than just ./configure, before typing make and make install.

If all goes well, this will create a Makefile. If all does not go well -- for instance, if neither the the JPEG nor the PNG and ZLIB libraries are found -- you will need to install those libraries, then come back and run configure again.

If necessary, make changes to the resulting Makefile. Then, type "make". If there are no errors, follow this with "make install". Because gd 2.0 and above installs as a shared library, it is necessary to install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more information about the available options. In the unlikely event that the GNU autoconf-produced configure script does not work well for you, you may wish to try configure.pl, a simple Perl script with similar but less complete capabilities. If all else fails, try renaming makefile.sample to Makefile. However, ./configure is almost always your best bet.

For Windows

Use the DLL version! See the paragraph at the beginning of this sectino. If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment. Copy all of the gd files to the project directory. Add gd.c to your project. Add other source files as appropriate. Learning the basic skills of creating projects with your chosen C environment is up to you. Alternatively, use the free mingw32 or cygwin tools, which may prove to be compatible with the provided configure script.

If you wish to test the library, type "make test" AFTER you have successfully executed "make install". This will build several test programs, including "gddemo". (Not all of these programs are expected to print completely successful messages, depending on the nature of the image formats with which some of the tests are tried; for instance, WBMP is a black and white format, so loss of color information is expected there.) Run gddemo to see some of the capabilities of gd. Run gdtestft to play with the freetype support, if you have built gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file demoout.png. (Note there is also a file named demoin.png, which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should be 128x128 pixels and should contain an image of the space shuttle with quite a lot of graphical elements drawn on top of it.

(If you are missing the demoin.png file, the other items should appear anyway.)

Look at demoin.png to see the original space shuttle image which was scaled and copied into the output image.

gd basics: using gd in your program

-lgd -lpng -lz -ljpeg -lfreetype -lm

If you want to use the provided simple fonts, include gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For more impressive results, install FreeType 2.x and use the gdImageStringFT function. If you are not using the provided Makefile and/or a library-based approach, be sure to include the source modules as well in your project. (They may be too large for 16-bit memory models, that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example, see gddemo.c, included in the distribution. gddemo.c is NOT the same program; it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive will produce a directory called "gd-2.0.33".

For Unix
cd to the 2.0.33 directory and type:

./configure


NOTE: BY DEFAULT, THE LIBRARY IS INSTALLED IN 
/usr/local/lib and the include files are
installed in /usr/local/include. IF YOU ARE
UPGRADING, you may wish to use:
./configure --prefix=/usr

Rather than just ./configure, before typing
make and make install.


If all goes well, this will create a Makefile. If all does not go well --
for instance, if neither the the JPEG nor the PNG and ZLIB libraries
are found -- you will need to install those libraries, then come back
and run configure again. 

If necessary, make changes to the resulting Makefile. Then, 
type "make". If there are no errors, follow this with "make install". 
Because gd 2.0 and above installs as a shared library, it is necessary to 
install the library properly before running gd-based programs.

If you get errors, type ./configure --help for more
information about the available options. In the unlikely event
that the GNU autoconf-produced configure script does not work well
for you, you may wish to try configure.pl, a
simple Perl script with similar but less complete capabilities.
If all else fails, try renaming makefile.sample
to Makefile. However, ./configure is
almost always your best bet.

For Windows
Use the DLL version! See the paragraph at the beginning of this sectino.
If you really want to compile it yourself for some strange reason, read on.

Create a project using your favorite programming environment.
Copy all of the gd files to the project directory. Add gd.c
to your project. Add other source files as appropriate. Learning the
basic skills of creating projects with your chosen C environment
is up to you. Alternatively, use the free mingw32 
or cygwin tools, which may prove to be compatible
with the provided configure script.


If you wish to test the library, type "make test" AFTER you have
successfully executed "make install". This will build
several test programs, including "gddemo". (Not all of these
programs are expected to print completely successful messages,
depending on the nature of the image formats with which some of
the tests are tried; for instance, WBMP is a black and white
format, so loss of color information is expected there.)
Run gddemo to see some of the capabilities of gd. Run
gdtestft to play with the freetype support, if you have built
gd with it and have access to truetype fonts.

gddemo should execute without incident, creating the file
demoout.png. (Note there is also a file named demoin.png,
which is provided in the package as part of the demonstration.)

Display demoout.png in your PNG viewer. The image should
be 128x128 pixels and should contain an image of the
space shuttle with quite a lot of graphical elements drawn
on top of it.

(If you are missing the demoin.png file, the other items
should appear anyway.)

Look at demoin.png to see the original space shuttle
image which was scaled and copied into the output image.

gd basics: using gd in your program
gd lets you create PNG or JPEG images on the fly. To use gd in your
program, include the file gd.h, and link with the gd
library and the other required libraries; the syntax for
most Unix flavors is:
-lgd -lpng -lz -ljpeg -lfreetype -lm

Assuming that all of these libraries are available.

If you want to use the provided simple fonts, include
gdfontt.h, gdfonts.h, gdfontmb.h, gdfontl.h and/or gdfontg.h. For
more impressive results, install FreeType 2.x and use the 
gdImageStringFT
function. If you are not using the provided Makefile and/or a 
library-based approach, be sure to include the source modules as well in your
project. (They may be too large for 16-bit memory models,
that is, 16-bit DOS and Windows.)

Here is a short example program. (For a more advanced example,
see gddemo.c, included in the distribution. gddemo.c is NOT the same program;
it demonstrates additional features!)

/* Bring in gd library functions */
#include "gd.h"

/* Bring in standard I/O so we can output the PNG to a file */
#include <stdio.h>

int main() {
  /* Declare the image */
  gdImagePtr im;
  /* Declare output files */
  FILE *pngout, *jpegout;
  /* Declare color indexes */
  int black;
  int abiliolygon fills still fail to behave properly,
please send code that demonstrates the problem, and a fix if
you have one. Verifying the fix is important.
Row-major, not column-major
Internally, gd now represents the array of pixels as
an array of rows of pixels, rather than an array of columns
of pixels. This improves the performance of compression and
decompression routines slightly, because horizontally adjacent
pixels are now next to each other in memory. This should
not affect properly written gd applications, but applications that
directly manipulate the pixels array will require
changes.

What else do I need to use gd?

To use gd, you will need an ANSI C compiler. All popular
Windows 95 and NT C compilers are ANSI C compliant. Any
full-ANSI-standard C compiler should be adequate. The cc
compiler released with SunOS 4.1.3 is not an ANSI C compiler.
Most Unix users who do not already have gcc should get it.
gcc is free, ANSI compliant and a de facto industry standard.
Ask your ISP why it is missing.

As of version 1.6, you also need the zlib compression library,
and the libpng library. As of version 1.6.2, you can draw text
using antialiased TrueType fonts if you also have the libttf
library installed, but this is not mandatory.
zlib is available for a variety of platforms from
the zlib web site.
libpng is available for a variety of platforms from
the PNG web site.


You will also want a PNG viewer, if you do not already have
one for your system, since you will need a good way to check the
results of your work. Netscape 4.04 and higher, and Microsoft
Internet Explorer 4.0 or higher, both support PNG.
Not every PNG-compatible viewer supports alpha channel
transparency, which is why gd 2.0.2 and above do alpha
blending in the library by default; it is possible to turn on the
saving of alpha channel information to the file instead.

How do I get gd?
Binaries (DLL for Windows programmers):

.ZIP File of DLL, Headers, Et Cetera


Source Code:

Gzipped Tar File (Unix)
.ZIP File of SOURCE CODE (Windows)


How do I build gd?

Win32 DLL users: if you are using MSVC, use the provided batch file
makemsvcimport.bat to make a bgd.lib import library
corresponding to the provided bgd.dll. Copy bgd.dll to your
application directory, or to your Windows sytem directory. In the
settings of your MSVC project, you MUST choose the
"multithreaded DLL" library option under "code generation." 
mingw32 and cygwin users can simply link with the provided libbgd.a 
stub library in order to use the DLL.

Building gd From the Source

In order to build gd, you must first unpack the archive you have
downloaded. If you are not familiar with tar and
gunzip (Unix) or ZIP (Windows), please
consult with an experienced user of your system. Sorry, we cannot
answer questions about basic Internet skills.

Unpacking the archive