source: rtems-graphics-toolkit/fltk-1.1.10/jpeg/jmorecfg.h @ 513eea1

Last change on this file since 513eea1 was 513eea1, checked in by Joel Sherrill <joel.sherrill@…>, on 01/09/10 at 22:43:24

2010-01-08 Joel Sherrill <joel.sherrill@…>

fltk 1.1.10. imported

  • ORIGIN: Updated.
  • Property mode set to 100644
File size: 11.1 KB
Line 
1/*
2 * jmorecfg.h
3 *
4 * Copyright (C) 1991-1997, Thomas G. Lane.
5 * This file is part of the Independent JPEG Group's software.
6 * For conditions of distribution and use, see the accompanying README file.
7 *
8 * This file contains additional configuration options that customize the
9 * JPEG software for special applications or support machine-dependent
10 * optimizations.  Most users will not need to touch this file.
11 */
12
13
14/*
15 * Define BITS_IN_JSAMPLE as either
16 *   8   for 8-bit sample values (the usual setting)
17 *   12  for 12-bit sample values
18 * Only 8 and 12 are legal data precisions for lossy JPEG according to the
19 * JPEG standard, and the IJG code does not support anything else!
20 * We do not support run-time selection of data precision, sorry.
21 */
22
23#define BITS_IN_JSAMPLE  8      /* use 8 or 12 */
24
25
26/*
27 * Maximum number of components (color channels) allowed in JPEG image.
28 * To meet the letter of the JPEG spec, set this to 255.  However, darn
29 * few applications need more than 4 channels (maybe 5 for CMYK + alpha
30 * mask).  We recommend 10 as a reasonable compromise; use 4 if you are
31 * really short on memory.  (Each allowed component costs a hundred or so
32 * bytes of storage, whether actually used in an image or not.)
33 */
34
35#define MAX_COMPONENTS  10      /* maximum number of image components */
36
37
38/*
39 * Basic data types.
40 * You may need to change these if you have a machine with unusual data
41 * type sizes; for example, "char" not 8 bits, "short" not 16 bits,
42 * or "long" not 32 bits.  We don't care whether "int" is 16 or 32 bits,
43 * but it had better be at least 16.
44 */
45
46/* Representation of a single sample (pixel element value).
47 * We frequently allocate large arrays of these, so it's important to keep
48 * them small.  But if you have memory to burn and access to char or short
49 * arrays is very slow on your hardware, you might want to change these.
50 */
51
52#if BITS_IN_JSAMPLE == 8
53/* JSAMPLE should be the smallest type that will hold the values 0..255.
54 * You can use a signed char by having GETJSAMPLE mask it with 0xFF.
55 */
56
57typedef unsigned char JSAMPLE;
58#define GETJSAMPLE(value)  ((int) (value))
59
60#define MAXJSAMPLE      255
61#define CENTERJSAMPLE   128
62
63#endif /* BITS_IN_JSAMPLE == 8 */
64
65
66#if BITS_IN_JSAMPLE == 12
67/* JSAMPLE should be the smallest type that will hold the values 0..4095.
68 * On nearly all machines "short" will do nicely.
69 */
70
71typedef short JSAMPLE;
72#define GETJSAMPLE(value)  ((int) (value))
73
74#define MAXJSAMPLE      4095
75#define CENTERJSAMPLE   2048
76
77#endif /* BITS_IN_JSAMPLE == 12 */
78
79
80/* Representation of a DCT frequency coefficient.
81 * This should be a signed value of at least 16 bits; "short" is usually OK.
82 * Again, we allocate large arrays of these, but you can change to int
83 * if you have memory to burn and "short" is really slow.
84 */
85
86typedef short JCOEF;
87
88
89/* Compressed datastreams are represented as arrays of JOCTET.
90 * These must be EXACTLY 8 bits wide, at least once they are written to
91 * external storage.  Note that when using the stdio data source/destination
92 * managers, this is also the data type passed to fread/fwrite.
93 */
94
95typedef unsigned char JOCTET;
96#define GETJOCTET(value)  (value)
97
98/* These typedefs are used for various table entries and so forth.
99 * They must be at least as wide as specified; but making them too big
100 * won't cost a huge amount of memory, so we don't provide special
101 * extraction code like we did for JSAMPLE.  (In other words, these
102 * typedefs live at a different point on the speed/space tradeoff curve.)
103 */
104
105/* UINT8 must hold at least the values 0..255. */
106
107typedef unsigned char UINT8;
108
109/* UINT16 must hold at least the values 0..65535. */
110
111typedef unsigned short UINT16;
112
113/* INT16 must hold at least the values -32768..32767. */
114
115#ifndef XMD_H                   /* X11/xmd.h correctly defines INT16 */
116typedef short INT16;
117#endif
118
119/* INT32 must hold at least signed 32-bit values. */
120
121#ifndef XMD_H
122typedef int INT32;
123#endif
124
125/* Datatype used for image dimensions.  The JPEG standard only supports
126 * images up to 64K*64K due to 16-bit fields in SOF markers.  Therefore
127 * "unsigned int" is sufficient on all machines.  However, if you need to
128 * handle larger images and you don't mind deviating from the spec, you
129 * can change this datatype.
130 */
131
132typedef unsigned int JDIMENSION;
133
134#define JPEG_MAX_DIMENSION  65500L  /* a tad under 64K to prevent overflows */
135
136
137/* These macros are used in all function definitions and extern declarations.
138 * You could modify them if you need to change function linkage conventions;
139 * in particular, you'll need to do that to make the library a Windows DLL.
140 * Another application is to make all functions global for use with debuggers
141 * or code profilers that require it.
142 */
143
144/* a function called through method pointers: */
145#define METHODDEF(type)         static type
146/* a function used only in its module: */
147#define LOCAL(type)             static type
148/* a function referenced thru EXTERNs: */
149#define GLOBAL(type)            type
150/* a reference to a GLOBAL function: */
151#define EXTERN(type)            extern type
152
153
154/* This macro is used to declare a "method", that is, a function pointer.
155 * We want to supply prototype parameters if the compiler can cope.
156 * Note that the arglist parameter must be parenthesized!
157 * Again, you can customize this if you need special linkage keywords.
158 */
159
160#define JMETHOD(type,methodname,arglist)  type (*methodname) arglist
161
162/* Here is the pseudo-keyword for declaring pointers that must be "far"
163 * on 80x86 machines.  Most of the specialized coding for 80x86 is handled
164 * by just saying "FAR *" where such a pointer is needed.  In a few places
165 * explicit coding is needed; see uses of the NEED_FAR_POINTERS symbol.
166 */
167
168#undef FAR
169#define FAR
170
171
172/*
173 * On a few systems, type boolean and/or its values FALSE, TRUE may appear
174 * in standard header files.  Or you may have conflicts with application-
175 * specific header files that you want to include together with these files.
176 * Defining HAVE_BOOLEAN before including jpeglib.h should make it work.
177 */
178
179#ifndef HAVE_BOOLEAN
180typedef char boolean;
181#endif
182#ifndef FALSE                   /* in case these macros already exist */
183#define FALSE   0               /* values of boolean */
184#endif
185#ifndef TRUE
186#define TRUE    1
187#endif
188
189
190/*
191 * The remaining options affect code selection within the JPEG library,
192 * but they don't need to be visible to most applications using the library.
193 * To minimize application namespace pollution, the symbols won't be
194 * defined unless JPEG_INTERNALS or JPEG_INTERNAL_OPTIONS has been defined.
195 */
196
197#ifdef JPEG_INTERNALS
198#define JPEG_INTERNAL_OPTIONS
199#endif
200
201#ifdef JPEG_INTERNAL_OPTIONS
202
203
204/*
205 * These defines indicate whether to include various optional functions.
206 * Undefining some of these symbols will produce a smaller but less capable
207 * library.  Note that you can leave certain source files out of the
208 * compilation/linking process if you've #undef'd the corresponding symbols.
209 * (You may HAVE to do that if your compiler doesn't like null source files.)
210 */
211
212/* Arithmetic coding is unsupported for legal reasons.  Complaints to IBM. */
213
214/* Capability options common to encoder and decoder: */
215
216#define DCT_ISLOW_SUPPORTED     /* slow but accurate integer algorithm */
217#define DCT_IFAST_SUPPORTED     /* faster, less accurate integer method */
218#define DCT_FLOAT_SUPPORTED     /* floating-point: accurate, fast on fast HW */
219
220/* Encoder capability options: */
221
222#undef  C_ARITH_CODING_SUPPORTED    /* Arithmetic coding back end? */
223#define C_MULTISCAN_FILES_SUPPORTED /* Multiple-scan JPEG files? */
224#define C_PROGRESSIVE_SUPPORTED     /* Progressive JPEG? (Requires MULTISCAN)*/
225#define ENTROPY_OPT_SUPPORTED       /* Optimization of entropy coding parms? */
226/* Note: if you selected 12-bit data precision, it is dangerous to turn off
227 * ENTROPY_OPT_SUPPORTED.  The standard Huffman tables are only good for 8-bit
228 * precision, so jchuff.c normally uses entropy optimization to compute
229 * usable tables for higher precision.  If you don't want to do optimization,
230 * you'll have to supply different default Huffman tables.
231 * The exact same statements apply for progressive JPEG: the default tables
232 * don't work for progressive mode.  (This may get fixed, however.)
233 */
234#define INPUT_SMOOTHING_SUPPORTED   /* Input image smoothing option? */
235
236/* Decoder capability options: */
237
238#undef  D_ARITH_CODING_SUPPORTED    /* Arithmetic coding back end? */
239#define D_MULTISCAN_FILES_SUPPORTED /* Multiple-scan JPEG files? */
240#define D_PROGRESSIVE_SUPPORTED     /* Progressive JPEG? (Requires MULTISCAN)*/
241#define SAVE_MARKERS_SUPPORTED      /* jpeg_save_markers() needed? */
242#define BLOCK_SMOOTHING_SUPPORTED   /* Block smoothing? (Progressive only) */
243#define IDCT_SCALING_SUPPORTED      /* Output rescaling via IDCT? */
244#undef  UPSAMPLE_SCALING_SUPPORTED  /* Output rescaling at upsample stage? */
245#define UPSAMPLE_MERGING_SUPPORTED  /* Fast path for sloppy upsampling? */
246#define QUANT_1PASS_SUPPORTED       /* 1-pass color quantization? */
247#define QUANT_2PASS_SUPPORTED       /* 2-pass color quantization? */
248
249/* more capability options later, no doubt */
250
251
252/*
253 * Ordering of RGB data in scanlines passed to or from the application.
254 * If your application wants to deal with data in the order B,G,R, just
255 * change these macros.  You can also deal with formats such as R,G,B,X
256 * (one extra byte per pixel) by changing RGB_PIXELSIZE.  Note that changing
257 * the offsets will also change the order in which colormap data is organized.
258 * RESTRICTIONS:
259 * 1. The sample applications cjpeg,djpeg do NOT support modified RGB formats.
260 * 2. These macros only affect RGB<=>YCbCr color conversion, so they are not
261 *    useful if you are using JPEG color spaces other than YCbCr or grayscale.
262 * 3. The color quantizer modules will not behave desirably if RGB_PIXELSIZE
263 *    is not 3 (they don't understand about dummy color components!).  So you
264 *    can't use color quantization if you change that value.
265 */
266
267#define RGB_RED         0       /* Offset of Red in an RGB scanline element */
268#define RGB_GREEN       1       /* Offset of Green */
269#define RGB_BLUE        2       /* Offset of Blue */
270#define RGB_PIXELSIZE   3       /* JSAMPLEs per RGB scanline element */
271
272
273/* Definitions for speed-related optimizations. */
274
275
276/* If your compiler supports inline functions, define INLINE
277 * as the inline keyword; otherwise define it as empty.
278 */
279
280#ifndef INLINE
281#ifdef __GNUC__                 /* for instance, GNU C knows about inline */
282#define INLINE __inline__
283#endif
284#ifndef INLINE
285#define INLINE                  /* default is to define it as empty */
286#endif
287#endif
288
289
290/* On some machines (notably 68000 series) "int" is 32 bits, but multiplying
291 * two 16-bit shorts is faster than multiplying two ints.  Define MULTIPLIER
292 * as short on such a machine.  MULTIPLIER must be at least 16 bits wide.
293 */
294
295#ifndef MULTIPLIER
296#define MULTIPLIER  int         /* type for fastest integer multiply */
297#endif
298
299
300/* FAST_FLOAT should be either float or double, whichever is done faster
301 * by your compiler.  (Note that this type is only used in the floating point
302 * DCT routines, so it only matters if you've defined DCT_FLOAT_SUPPORTED.)
303 * Typically, float is faster in ANSI C compilers, while double is faster in
304 * pre-ANSI compilers (because they insist on converting to double anyway).
305 * The code below therefore chooses float if we have ANSI-style prototypes.
306 */
307
308#ifndef FAST_FLOAT
309#ifdef HAVE_PROTOTYPES
310#define FAST_FLOAT  float
311#else
312#define FAST_FLOAT  double
313#endif
314#endif
315
316#endif /* JPEG_INTERNAL_OPTIONS */
Note: See TracBrowser for help on using the repository browser.