Lines Matching full: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.
123 * Configure will set up the makefile so that "make install" will install files
139 Configuring the software using one of the supplied jconfig and makefile files
143 files:
179 You may also want to look at the canned jconfig files, if there is one for a
197 project files (or whatever you do use) to compile all the source files and
198 link them into executable files cjpeg, djpeg, jpegtran, rdjpgcom, and wrjpgcom.
199 See the file lists in any of the makefiles to find out which files go into
202 lists identify which source files are actually needed for compression,
236 memory; data is swapped out to temporary files as necessary. However, the
245 * jmemname.c This version creates named temporary files. For anything
249 NEED_SIGNAL_CATCHER in jconfig.h to make sure the temp files
260 programs. The supplied makefiles and jconfig files for
303 If you have trouble with missing system include files or inclusion of the
328 (The first- and second-generation .jpg files aren't identical since JPEG is
329 lossy.) If you can generate duplicates of the testimg* files then you
336 and cjpeg by hand and compare the output files to testimg* with whatever
337 binary file comparison tool you have. The files should be bit-for-bit
375 copying the executable files (cjpeg, djpeg, jpegtran, rdjpgcom, and wrjpgcom)
387 to see where configure thought the files should go. You may need to edit
392 programs besides ours, then you need to put the four include files
395 (extension may vary depending on system) wherever library files go.
413 We distribute the software with support for RLE image files (Utah Raster
419 containing the URT .h files (typically the "include"
438 files are for 8-bit data.
442 Note that a 12-bit version will not read 8-bit JPEG files, nor vice versa;
449 binary-format PPM and PGM files. Binary-format PPM/PGM files which have a
454 read files of any maxval regardless of the BITS_IN_JSAMPLE setting; incoming
479 decoder support for all valid JPEG files, to ensure that you can read anyone's
512 in that mode. (Note: some of the distributed compiler-specific jconfig files
523 by djpeg's -fast switch. Don't forget to update the documentation files
557 After renaming the files according to Acorn conventions, take a copy of
576 and rename the test files.
584 The supplied config files are set up to use jmemname.c as the memory
585 manager, with temporary files being created on the device named by
591 Copy the project files makcjpeg.st, makdjpeg.st, maktjpeg.st, and makljpeg.st
593 project files should work as-is with Pure C. For Turbo C, change library
601 compiler option "-8" to the project files and replace pcfltlib.lib with
606 pcfltlib.lib from the project files.
611 We haven't bothered to include project files for rdjpgcom and wrjpgcom.
612 Those source files should just be compiled by themselves; they don't
616 space used by temporary files created with "tmpfile()" not to be freed after
620 close temp files before exiting. But if you use the JPEG library with your
658 The supplied user-interface files (cjpeg.c, djpeg.c, etc) are set up to
678 implementation of jpeg_mem_available(). It also creates temporary files that
708 project files for the library and the testbed applications, then build the
710 hack, which saves us from trying to maintain CodeWarrior project files as part
721 You'll have to prepare project files for the programs; we don't include any
722 in the distribution since they are not text files. Use the file lists in
724 libraries in a separate segment. You may need to divide the JPEG files into
756 model. (The supplied makefiles and jconfig files for Borland and Microsoft C
762 don't have a suitable assembler, you can get pre-assembled object files for
764 distributions of the IJG source code often include these object files.)
783 Most MS-DOS compilers treat stdin/stdout as text files, so you must use
789 to explicitly named files... the "make test" procedures in the supplied
809 Be sure to convert all the source files to DOS text format (CR/LF newlines).
811 source files, sometimes it will give bogus compile errors.
853 Some Windows system include files define typedef boolean as "unsigned char".
856 include files. But if you use the JPEG library in your own program, and some
857 of your program's files import one definition of boolean while some import the
1001 files; see below.)
1005 all the *.c files to *.cpp (and adjusting the makefile to match). This
1012 We include makefiles that should work as project files in DevStudio 4.2 or
1021 2. Click on the .mak files to construct project workspaces.
1025 4. Move the application .exe files from `app`\Release to an
1060 error points to the last block of the files, it is most likely bogus and may
1061 be safely ignored. It seems to be because the files are Stream_LF and
1062 Backup/Compare has difficulty with the (presumably) null padded files.
