]> git.saurik.com Git - wxWidgets.git/blame - src/jpeg/jmorecfg.h
1. DLL compilation fixes (wrong WXDLLEXPORT placement) in db.h/cpp
[wxWidgets.git] / src / jpeg / jmorecfg.h
CommitLineData
e1929140
RR
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
57#ifdef HAVE_UNSIGNED_CHAR
58
59typedef unsigned char JSAMPLE;
60#define GETJSAMPLE(value) ((int) (value))
61
62#else /* not HAVE_UNSIGNED_CHAR */
63
64typedef char JSAMPLE;
65#ifdef CHAR_IS_UNSIGNED
66#define GETJSAMPLE(value) ((int) (value))
67#else
68#define GETJSAMPLE(value) ((int) (value) & 0xFF)
69#endif /* CHAR_IS_UNSIGNED */
70
71#endif /* HAVE_UNSIGNED_CHAR */
72
73#define MAXJSAMPLE 255
74#define CENTERJSAMPLE 128
75
76#endif /* BITS_IN_JSAMPLE == 8 */
77
78
79#if BITS_IN_JSAMPLE == 12
80/* JSAMPLE should be the smallest type that will hold the values 0..4095.
81 * On nearly all machines "short" will do nicely.
82 */
83
84typedef short JSAMPLE;
85#define GETJSAMPLE(value) ((int) (value))
86
87#define MAXJSAMPLE 4095
88#define CENTERJSAMPLE 2048
89
90#endif /* BITS_IN_JSAMPLE == 12 */
91
92
93/* Representation of a DCT frequency coefficient.
94 * This should be a signed value of at least 16 bits; "short" is usually OK.
95 * Again, we allocate large arrays of these, but you can change to int
96 * if you have memory to burn and "short" is really slow.
97 */
98
99typedef short JCOEF;
100
101
102/* Compressed datastreams are represented as arrays of JOCTET.
103 * These must be EXACTLY 8 bits wide, at least once they are written to
104 * external storage. Note that when using the stdio data source/destination
105 * managers, this is also the data type passed to fread/fwrite.
106 */
107
108#ifdef HAVE_UNSIGNED_CHAR
109
110typedef unsigned char JOCTET;
111#define GETJOCTET(value) (value)
112
113#else /* not HAVE_UNSIGNED_CHAR */
114
115typedef char JOCTET;
116#ifdef CHAR_IS_UNSIGNED
117#define GETJOCTET(value) (value)
118#else
119#define GETJOCTET(value) ((value) & 0xFF)
120#endif /* CHAR_IS_UNSIGNED */
121
122#endif /* HAVE_UNSIGNED_CHAR */
123
124
125/* These typedefs are used for various table entries and so forth.
126 * They must be at least as wide as specified; but making them too big
127 * won't cost a huge amount of memory, so we don't provide special
128 * extraction code like we did for JSAMPLE. (In other words, these
129 * typedefs live at a different point on the speed/space tradeoff curve.)
130 */
131
132/* UINT8 must hold at least the values 0..255. */
133
134#ifdef HAVE_UNSIGNED_CHAR
135typedef unsigned char UINT8;
136#else /* not HAVE_UNSIGNED_CHAR */
137#ifdef CHAR_IS_UNSIGNED
138typedef char UINT8;
139#else /* not CHAR_IS_UNSIGNED */
140typedef short UINT8;
141#endif /* CHAR_IS_UNSIGNED */
142#endif /* HAVE_UNSIGNED_CHAR */
143
144/* UINT16 must hold at least the values 0..65535. */
145
146#ifdef HAVE_UNSIGNED_SHORT
147typedef unsigned short UINT16;
148#else /* not HAVE_UNSIGNED_SHORT */
149typedef unsigned int UINT16;
150#endif /* HAVE_UNSIGNED_SHORT */
151
152/* INT16 must hold at least the values -32768..32767. */
153
154#ifndef XMD_H /* X11/xmd.h correctly defines INT16 */
155typedef short INT16;
156#endif
157
158/* INT32 must hold at least signed 32-bit values. */
159
ea64e17a
JS
160/* Modified JACS 23/4/99. 1200 means VC++ 6 */
161#if !defined(XMD_H) && !(_MSC_VER >= 1200) /* X11/xmd.h correctly defines INT32 */
e1929140
RR
162typedef long INT32;
163#endif
164
ea64e17a
JS
165/* Added JACS 23/4/99, to get INT32 definition */
166#if (_MSC_VER >= 1200)
167#include <windows.h>
168#endif
169
e1929140
RR
170/* Datatype used for image dimensions. The JPEG standard only supports
171 * images up to 64K*64K due to 16-bit fields in SOF markers. Therefore
172 * "unsigned int" is sufficient on all machines. However, if you need to
173 * handle larger images and you don't mind deviating from the spec, you
174 * can change this datatype.
175 */
176
177typedef unsigned int JDIMENSION;
178
179#define JPEG_MAX_DIMENSION 65500L /* a tad under 64K to prevent overflows */
180
181
182/* These macros are used in all function definitions and extern declarations.
183 * You could modify them if you need to change function linkage conventions;
184 * in particular, you'll need to do that to make the library a Windows DLL.
185 * Another application is to make all functions global for use with debuggers
186 * or code profilers that require it.
187 */
188
b7a34956
DW
189#if defined(__VISAGECPP__)
190/* a function called through method pointers: */
191#define METHODDEF(type) static type _Optlink
192/* a function used only in its module: */
193#define LOCAL(type) static type _Optlink
194/* a function referenced thru EXTERNs: */
195#define GLOBAL(type) type
196/* a reference to a GLOBAL function: */
197#define EXTERN(type) extern type _Optlink
198#else
e1929140
RR
199/* a function called through method pointers: */
200#define METHODDEF(type) static type
201/* a function used only in its module: */
202#define LOCAL(type) static type
203/* a function referenced thru EXTERNs: */
204#define GLOBAL(type) type
205/* a reference to a GLOBAL function: */
206#define EXTERN(type) extern type
b7a34956
DW
207#endif
208
e1929140
RR
209
210
211/* This macro is used to declare a "method", that is, a function pointer.
212 * We want to supply prototype parameters if the compiler can cope.
213 * Note that the arglist parameter must be parenthesized!
214 * Again, you can customize this if you need special linkage keywords.
215 */
216
217#ifdef HAVE_PROTOTYPES
218#define JMETHOD(type,methodname,arglist) type (*methodname) arglist
219#else
220#define JMETHOD(type,methodname,arglist) type (*methodname) ()
221#endif
222
223
224/* Here is the pseudo-keyword for declaring pointers that must be "far"
225 * on 80x86 machines. Most of the specialized coding for 80x86 is handled
226 * by just saying "FAR *" where such a pointer is needed. In a few places
227 * explicit coding is needed; see uses of the NEED_FAR_POINTERS symbol.
228 */
229
230#ifdef NEED_FAR_POINTERS
231#define FAR far
232#else
233#define FAR
234#endif
235
236
237/*
238 * On a few systems, type boolean and/or its values FALSE, TRUE may appear
239 * in standard header files. Or you may have conflicts with application-
240 * specific header files that you want to include together with these files.
241 * Defining HAVE_BOOLEAN before including jpeglib.h should make it work.
242 */
243
244#ifndef HAVE_BOOLEAN
245typedef int boolean;
246#endif
247#ifndef FALSE /* in case these macros already exist */
248#define FALSE 0 /* values of boolean */
249#endif
250#ifndef TRUE
251#define TRUE 1
252#endif
253
254
255/*
256 * The remaining options affect code selection within the JPEG library,
257 * but they don't need to be visible to most applications using the library.
258 * To minimize application namespace pollution, the symbols won't be
259 * defined unless JPEG_INTERNALS or JPEG_INTERNAL_OPTIONS has been defined.
260 */
261
262#ifdef JPEG_INTERNALS
263#define JPEG_INTERNAL_OPTIONS
264#endif
265
266#ifdef JPEG_INTERNAL_OPTIONS
267
268
269/*
270 * These defines indicate whether to include various optional functions.
271 * Undefining some of these symbols will produce a smaller but less capable
272 * library. Note that you can leave certain source files out of the
273 * compilation/linking process if you've #undef'd the corresponding symbols.
274 * (You may HAVE to do that if your compiler doesn't like null source files.)
275 */
276
277/* Arithmetic coding is unsupported for legal reasons. Complaints to IBM. */
278
279/* Capability options common to encoder and decoder: */
280
281#define DCT_ISLOW_SUPPORTED /* slow but accurate integer algorithm */
282#define DCT_IFAST_SUPPORTED /* faster, less accurate integer method */
283#define DCT_FLOAT_SUPPORTED /* floating-point: accurate, fast on fast HW */
284
285/* Encoder capability options: */
286
287#undef C_ARITH_CODING_SUPPORTED /* Arithmetic coding back end? */
288#define C_MULTISCAN_FILES_SUPPORTED /* Multiple-scan JPEG files? */
289#define C_PROGRESSIVE_SUPPORTED /* Progressive JPEG? (Requires MULTISCAN)*/
290#define ENTROPY_OPT_SUPPORTED /* Optimization of entropy coding parms? */
291/* Note: if you selected 12-bit data precision, it is dangerous to turn off
292 * ENTROPY_OPT_SUPPORTED. The standard Huffman tables are only good for 8-bit
293 * precision, so jchuff.c normally uses entropy optimization to compute
294 * usable tables for higher precision. If you don't want to do optimization,
295 * you'll have to supply different default Huffman tables.
296 * The exact same statements apply for progressive JPEG: the default tables
297 * don't work for progressive mode. (This may get fixed, however.)
298 */
299#define INPUT_SMOOTHING_SUPPORTED /* Input image smoothing option? */
300
301/* Decoder capability options: */
302
303#undef D_ARITH_CODING_SUPPORTED /* Arithmetic coding back end? */
304#define D_MULTISCAN_FILES_SUPPORTED /* Multiple-scan JPEG files? */
305#define D_PROGRESSIVE_SUPPORTED /* Progressive JPEG? (Requires MULTISCAN)*/
306#define SAVE_MARKERS_SUPPORTED /* jpeg_save_markers() needed? */
307#define BLOCK_SMOOTHING_SUPPORTED /* Block smoothing? (Progressive only) */
308#define IDCT_SCALING_SUPPORTED /* Output rescaling via IDCT? */
309#undef UPSAMPLE_SCALING_SUPPORTED /* Output rescaling at upsample stage? */
310#define UPSAMPLE_MERGING_SUPPORTED /* Fast path for sloppy upsampling? */
311#define QUANT_1PASS_SUPPORTED /* 1-pass color quantization? */
312#define QUANT_2PASS_SUPPORTED /* 2-pass color quantization? */
313
314/* more capability options later, no doubt */
315
316
317/*
318 * Ordering of RGB data in scanlines passed to or from the application.
319 * If your application wants to deal with data in the order B,G,R, just
320 * change these macros. You can also deal with formats such as R,G,B,X
321 * (one extra byte per pixel) by changing RGB_PIXELSIZE. Note that changing
322 * the offsets will also change the order in which colormap data is organized.
323 * RESTRICTIONS:
324 * 1. The sample applications cjpeg,djpeg do NOT support modified RGB formats.
325 * 2. These macros only affect RGB<=>YCbCr color conversion, so they are not
326 * useful if you are using JPEG color spaces other than YCbCr or grayscale.
327 * 3. The color quantizer modules will not behave desirably if RGB_PIXELSIZE
328 * is not 3 (they don't understand about dummy color components!). So you
329 * can't use color quantization if you change that value.
330 */
331
332#define RGB_RED 0 /* Offset of Red in an RGB scanline element */
333#define RGB_GREEN 1 /* Offset of Green */
334#define RGB_BLUE 2 /* Offset of Blue */
335#define RGB_PIXELSIZE 3 /* JSAMPLEs per RGB scanline element */
336
337
338/* Definitions for speed-related optimizations. */
339
340
341/* If your compiler supports inline functions, define INLINE
342 * as the inline keyword; otherwise define it as empty.
343 */
344
345#ifndef INLINE
346#ifdef __GNUC__ /* for instance, GNU C knows about inline */
347#define INLINE __inline__
348#endif
349#ifndef INLINE
350#define INLINE /* default is to define it as empty */
351#endif
352#endif
353
354
355/* On some machines (notably 68000 series) "int" is 32 bits, but multiplying
356 * two 16-bit shorts is faster than multiplying two ints. Define MULTIPLIER
357 * as short on such a machine. MULTIPLIER must be at least 16 bits wide.
358 */
359
360#ifndef MULTIPLIER
361#define MULTIPLIER int /* type for fastest integer multiply */
362#endif
363
364
365/* FAST_FLOAT should be either float or double, whichever is done faster
366 * by your compiler. (Note that this type is only used in the floating point
367 * DCT routines, so it only matters if you've defined DCT_FLOAT_SUPPORTED.)
368 * Typically, float is faster in ANSI C compilers, while double is faster in
369 * pre-ANSI compilers (because they insist on converting to double anyway).
370 * The code below therefore chooses float if we have ANSI-style prototypes.
371 */
372
373#ifndef FAST_FLOAT
374#ifdef HAVE_PROTOTYPES
375#define FAST_FLOAT float
376#else
377#define FAST_FLOAT double
378#endif
379#endif
380
381#endif /* JPEG_INTERNAL_OPTIONS */