Lines Matching full:makefile
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
69 * Makefile: controls the compilation process.
71 substitute for a Makefile. jconfig.h is needed in any environment.)
77 files to jconfig.h and Makefile.
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
145 Makefile jconfig file System and/or compiler
147 makefile.manx jconfig.manx Amiga, Manx Aztec C
148 makefile.sas jconfig.sas Amiga, SAS C
151 makefile.bcc jconfig.bcc MS-DOS or OS/2, Borland C
152 makefile.dj jconfig.dj MS-DOS, DJGPP (Delorie's port of GNU C)
153 makefile.mc6 jconfig.mc6 MS-DOS, Microsoft C (16-bit only)
154 makefile.wat jconfig.wat MS-DOS, OS/2, or Windows NT, Watcom C
155 makefile.vc jconfig.vc Windows NT/95, MS Visual C++
157 makefile.mms jconfig.vms Digital VMS, with MMS software
158 makefile.vms jconfig.vms Digital VMS, without MMS software
160 Copy the proper jconfig file to jconfig.h and the makefile to Makefile (or
161 whatever your system uses as the standard makefile name). For more info see
177 print out some advice about which makefile to use.
182 Second, select a makefile and copy it to Makefile (or whatever your system
183 uses as the standard makefile name). The most generic makefiles we provide
185 makefile.ansi: if your C compiler supports function prototypes
186 makefile.unix: if not.
191 Look over the selected Makefile and adjust options as needed. In particular
204 just compiles everything and links it all together; makefile.vms is an example
267 makefile to equal the corresponding object file name (for example, jmemansi.o
279 DEFAULT_MAX_MEM to jconfig.h, or by adding a -D switch to the Makefile).
335 If you're using a makefile that doesn't provide the test option, run djpeg
382 If you generated a Makefile with the "configure" script, you can just say
388 the Makefile, particularly if your system's conventions for man page
396 If you generated a Makefile with "configure", it will do what it thinks
418 2. Add a -I option to CFLAGS in the Makefile for the directory
421 3. Add -L... -lrle to LDLIBS in the Makefile, where ... specifies
558 makefile.ansi, change all occurrences of 'libjpeg.a' to 'libjpeg.o' and
574 Run the makefile using !AMU not !Make. If you want to use the 'clean' and
575 'test' makefile entries then you will have to fiddle with the syntax a bit
644 (or -Ae if you prefer). If configuring by hand, use makefile.ansi and add
645 "-Aa" to the CFLAGS line in the makefile.
648 delivered with a minimum HP-UX system, then you must use makefile.unix
653 use makefile.unix, or run configure without the CC option.
761 your makefile assembles that file and includes it in the library. If you
822 makefile.mc6 works with Microsoft C, DOS Visual C++, etc. It should only
829 Note that this makefile assumes that the working copy of itself is called
830 "makefile". If you want to call it something else, say "makefile.mak",
831 be sure to adjust the dependency line that reads "$(RFILE) : makefile".
832 Otherwise the make will fail because it doesn't know how to create "makefile".
968 NEED_FAR_POINTERS and MAX_ALLOC_CHUNK). Beware that makefile.bcc will need
999 model. makefile.vc is intended for command-line use. (If you are using
1005 all the *.c files to *.cpp (and adjusting the makefile to match). This
1013 later. There is a library makefile that builds the IJG library as a static
1014 Win32 library, and an application makefile that builds the sample applications
1028 NMAKE /f makefile.vc test
1035 makefile.bcc.
1040 On some SGI systems, you may need to set "AR2= ar -ts" in the Makefile.
