Lines Matching refs:files
27 (better do "make -n install" first to see if the makefile will put the files
38 using one of the supplied jconfig and makefile files
54 files to the local standard text file format (for example, if you are on
56 such conversion to all the files EXCEPT those whose names begin with "test".
57 The test files contain binary data; if you change them in any way then the
67 To configure the IJG code for your system, you need to create two files:
70 (On a non-Unix machine, you may create "project files" or some other
73 We provide three different ways to generate these files:
75 * We provide sample jconfig files and makefiles for popular machines;
77 files to jconfig.h and Makefile.
78 * If all else fails, read the instructions below and make your own files.
86 and let the configure script construct appropriate configuration files.
118 * Configure will set up the makefile so that "make install" will install files
134 Configuring the software using one of the supplied jconfig and makefile files
138 files:
176 You may also want to look at the canned jconfig files, if there is one for a
194 project files (or whatever you do use) to compile all the source files and
195 link them into executable files cjpeg, djpeg, jpegtran, rdjpgcom, and wrjpgcom.
196 See the file lists in any of the makefiles to find out which files go into
199 lists identify which source files are actually needed for compression,
233 memory; data is swapped out to temporary files as necessary. However, the
242 * jmemname.c This version creates named temporary files. For anything
246 NEED_SIGNAL_CATCHER in jconfig.h to make sure the temp files
257 programs. The supplied makefiles and jconfig files for
300 If you have trouble with missing system include files or inclusion of the
325 (The first- and second-generation .jpg files aren't identical since the
327 of the testimg* files then you probably have working programs.
333 and cjpeg by hand and compare the output files to testimg* with whatever
334 binary file comparison tool you have. The files should be bit-for-bit
372 copying the executable files (cjpeg, djpeg, jpegtran, rdjpgcom, and wrjpgcom)
384 to see where configure thought the files should go. You may need to edit
389 programs besides ours, then you need to put the four include files
392 (extension may vary depending on system) wherever library files go.
410 We distribute the software with support for RLE image files (Utah Raster
416 containing the URT .h files (typically the "include"
436 files are for 8-bit data.
447 text-format or binary-format PPM and PGM files. Binary-format PPM/PGM files
452 read files of any maxval regardless of the BITS_IN_JSAMPLE setting; incoming
480 decoder support for all valid JPEG files, to ensure that you can read anyone's
513 in that mode. (Note: some of the distributed compiler-specific jconfig files
524 by djpeg's -fast switch. Don't forget to update the documentation files
558 After renaming the files according to Acorn conventions, take a copy of
577 and rename the test files.
585 The supplied config files are set up to use jmemname.c as the memory
586 manager, with temporary files being created on the device named by
592 Copy the project files makcjpeg.st, makdjpeg.st, maktjpeg.st, and makljpeg.st
594 project files should work as-is with Pure C. For Turbo C, change library
602 compiler option "-8" to the project files and replace pcfltlib.lib with
607 pcfltlib.lib from the project files.
612 We haven't bothered to include project files for rdjpgcom and wrjpgcom.
613 Those source files should just be compiled by themselves; they don't
618 space used by temporary files created with "tmpfile()" not to be freed after
622 close temp files before exiting. But if you use the JPEG library with your
660 The supplied user-interface files (cjpeg.c, djpeg.c, etc) are set up to
680 implementation of jpeg_mem_available(). It also creates temporary files that
710 project files for the library and the testbed applications, then build the
712 hack, which saves us from trying to maintain CodeWarrior project files as part
723 You'll have to prepare project files for the programs; we don't include any
724 in the distribution since they are not text files. Use the file lists in
726 libraries in a separate segment. You may need to divide the JPEG files into
758 model. (The supplied makefiles and jconfig files for Borland and Microsoft C
764 don't have a suitable assembler, you can get pre-assembled object files for
766 distributions of the IJG source code often include these object files.)
785 Most MS-DOS compilers treat stdin/stdout as text files, so you must use
791 to explicitly named files... the "make test" procedures in the supplied
811 Be sure to convert all the source files to DOS text format (CR/LF newlines).
813 source files, sometimes it will give bogus compile errors.
855 Some Windows system include files define typedef boolean as "unsigned char".
858 include files. But if you use the JPEG library in your own program, and some
859 of your program's files import one definition of boolean while some import the
1010 files; see below.)
1015 all the *.c files to *.cpp (and adjusting the makefile to match).
1022 We include makefiles that should work as project files in DevStudio 6.0 or
1032 This will move jconfig.vc to jconfig.h and makefiles to project files.
1036 get a message saying that the project files are being updated.)
1040 5. Move the application .exe files from `app`\Release to an
1046 We include makefiles that should work as project files in Visual Studio
1057 This will move jconfig.vc to jconfig.h and makefiles to project files.
1061 probably get a message saying that the project files are being updated.)
1065 5. Move the application .exe files from `app`\Release to an
1104 error points to the last block of the files, it is most likely bogus and may
1105 be safely ignored. It seems to be because the files are Stream_LF and
1106 Backup/Compare has difficulty with the (presumably) null padded files.