| Index: jconfig.txt
|
| diff --git a/jconfig.txt b/jconfig.txt
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..808f87fcd44299f4fac005daff8a63ace98430e7
|
| --- /dev/null
|
| +++ b/jconfig.txt
|
| @@ -0,0 +1,143 @@
|
| +/*
|
| + * jconfig.txt
|
| + *
|
| + * This file was part of the Independent JPEG Group's software:
|
| + * Copyright (C) 1991-1994, Thomas G. Lane.
|
| + * It was modified by The libjpeg-turbo Project to include only code relevant
|
| + * to libjpeg-turbo.
|
| + * For conditions of distribution and use, see the accompanying README.ijg
|
| + * file.
|
| + *
|
| + * This file documents the configuration options that are required to
|
| + * customize the JPEG software for a particular system.
|
| + *
|
| + * The actual configuration options for a particular installation are stored
|
| + * in jconfig.h. On many machines, jconfig.h can be generated automatically
|
| + * or copied from one of the "canned" jconfig files that we supply. But if
|
| + * you need to generate a jconfig.h file by hand, this file tells you how.
|
| + *
|
| + * DO NOT EDIT THIS FILE --- IT WON'T ACCOMPLISH ANYTHING.
|
| + * EDIT A COPY NAMED JCONFIG.H.
|
| + */
|
| +
|
| +
|
| +/*
|
| + * These symbols indicate the properties of your machine or compiler.
|
| + * #define the symbol if yes, #undef it if no.
|
| + */
|
| +
|
| +/* Does your compiler support the declaration "unsigned char" ?
|
| + * How about "unsigned short" ?
|
| + */
|
| +#define HAVE_UNSIGNED_CHAR
|
| +#define HAVE_UNSIGNED_SHORT
|
| +
|
| +/* Define "void" as "char" if your compiler doesn't know about type void.
|
| + * NOTE: be sure to define void such that "void *" represents the most general
|
| + * pointer type, e.g., that returned by malloc().
|
| + */
|
| +/* #define void char */
|
| +
|
| +/* Define "const" as empty if your compiler doesn't know the "const" keyword.
|
| + */
|
| +/* #define const */
|
| +
|
| +/* Define this if an ordinary "char" type is unsigned.
|
| + * If you're not sure, leaving it undefined will work at some cost in speed.
|
| + * If you defined HAVE_UNSIGNED_CHAR then the speed difference is minimal.
|
| + */
|
| +#undef __CHAR_UNSIGNED__
|
| +
|
| +/* Define this if your system has an ANSI-conforming <stddef.h> file.
|
| + */
|
| +#define HAVE_STDDEF_H
|
| +
|
| +/* Define this if your system has an ANSI-conforming <stdlib.h> file.
|
| + */
|
| +#define HAVE_STDLIB_H
|
| +
|
| +/* Define this if your system does not have an ANSI/SysV <string.h>,
|
| + * but does have a BSD-style <strings.h>.
|
| + */
|
| +#undef NEED_BSD_STRINGS
|
| +
|
| +/* Define this if your system does not provide typedef size_t in any of the
|
| + * ANSI-standard places (stddef.h, stdlib.h, or stdio.h), but places it in
|
| + * <sys/types.h> instead.
|
| + */
|
| +#undef NEED_SYS_TYPES_H
|
| +
|
| +/* Although a real ANSI C compiler can deal perfectly well with pointers to
|
| + * unspecified structures (see "incomplete types" in the spec), a few pre-ANSI
|
| + * and pseudo-ANSI compilers get confused. To keep one of these bozos happy,
|
| + * define INCOMPLETE_TYPES_BROKEN. This is not recommended unless you
|
| + * actually get "missing structure definition" warnings or errors while
|
| + * compiling the JPEG code.
|
| + */
|
| +#undef INCOMPLETE_TYPES_BROKEN
|
| +
|
| +/* Define "boolean" as unsigned char, not int, on Windows systems.
|
| + */
|
| +#ifdef _WIN32
|
| +#ifndef __RPCNDR_H__ /* don't conflict if rpcndr.h already read */
|
| +typedef unsigned char boolean;
|
| +#endif
|
| +#define HAVE_BOOLEAN /* prevent jmorecfg.h from redefining it */
|
| +#endif
|
| +
|
| +
|
| +/*
|
| + * The following options affect code selection within the JPEG library,
|
| + * but they don't need to be visible to applications using the library.
|
| + * To minimize application namespace pollution, the symbols won't be
|
| + * defined unless JPEG_INTERNALS has been defined.
|
| + */
|
| +
|
| +#ifdef JPEG_INTERNALS
|
| +
|
| +/* Define this if your compiler implements ">>" on signed values as a logical
|
| + * (unsigned) shift; leave it undefined if ">>" is a signed (arithmetic) shift,
|
| + * which is the normal and rational definition.
|
| + */
|
| +#undef RIGHT_SHIFT_IS_UNSIGNED
|
| +
|
| +
|
| +#endif /* JPEG_INTERNALS */
|
| +
|
| +
|
| +/*
|
| + * The remaining options do not affect the JPEG library proper,
|
| + * but only the sample applications cjpeg/djpeg (see cjpeg.c, djpeg.c).
|
| + * Other applications can ignore these.
|
| + */
|
| +
|
| +#ifdef JPEG_CJPEG_DJPEG
|
| +
|
| +/* These defines indicate which image (non-JPEG) file formats are allowed. */
|
| +
|
| +#define BMP_SUPPORTED /* BMP image file format */
|
| +#define GIF_SUPPORTED /* GIF image file format */
|
| +#define PPM_SUPPORTED /* PBMPLUS PPM/PGM image file format */
|
| +#undef RLE_SUPPORTED /* Utah RLE image file format */
|
| +#define TARGA_SUPPORTED /* Targa image file format */
|
| +
|
| +/* Define this if you want to name both input and output files on the command
|
| + * line, rather than using stdout and optionally stdin. You MUST do this if
|
| + * your system can't cope with binary I/O to stdin/stdout. See comments at
|
| + * head of cjpeg.c or djpeg.c.
|
| + */
|
| +#undef TWO_FILE_COMMANDLINE
|
| +
|
| +/* By default, we open image files with fopen(...,"rb") or fopen(...,"wb").
|
| + * This is necessary on systems that distinguish text files from binary files,
|
| + * and is harmless on most systems that don't. If you have one of the rare
|
| + * systems that complains about the "b" spec, define this symbol.
|
| + */
|
| +#undef DONT_USE_B_MODE
|
| +
|
| +/* Define this if you want percent-done progress reports from cjpeg/djpeg.
|
| + */
|
| +#undef PROGRESS_REPORT
|
| +
|
| +
|
| +#endif /* JPEG_CJPEG_DJPEG */
|
|
|