diff options
Diffstat (limited to 'jpeg/install.txt')
| -rw-r--r-- | jpeg/install.txt | 148 |
1 files changed, 72 insertions, 76 deletions
diff --git a/jpeg/install.txt b/jpeg/install.txt index 64205134a..9670a0444 100644 --- a/jpeg/install.txt +++ b/jpeg/install.txt @@ -1,6 +1,6 @@ INSTALLATION INSTRUCTIONS for the Independent JPEG Group's JPEG software -Copyright (C) 1991-2021, Thomas G. Lane, Guido Vollbeding. +Copyright (C) 1991-2023, Thomas G. Lane, Guido Vollbeding. This file is part of the Independent JPEG Group's software. For conditions of distribution and use, see the accompanying README file. @@ -142,7 +142,8 @@ Makefile jconfig file System and/or compiler makefile.manx jconfig.manx Amiga, Manx Aztec C makefile.sas jconfig.sas Amiga, SAS C makeproj.mac jconfig.mac Apple Macintosh, Metrowerks CodeWarrior -mak*jpeg.st jconfig.st Atari ST/STE/TT, Pure C or Turbo C +makefile.xc jconfig.xc Apple Mac, Xcode 15 +mak*jpeg.st jconfig.st Atari ST/Mega/STE/TT/Falcon, Pure C or Turbo C makefile.bcc jconfig.bcc MS-DOS or OS/2, Borland C makefile.dj jconfig.dj MS-DOS, DJGPP (Delorie's port of GNU C) makefile.mc6 jconfig.mc6 MS-DOS, Microsoft C (16-bit only) @@ -150,12 +151,15 @@ makefile.wat jconfig.wat MS-DOS, OS/2, or Windows NT, Watcom C makefile.vc jconfig.vc Windows, MS Visual C++ makefile.vs jconfig.vc Windows, MS Visual C++ 6 Developer Studio make*.vc6 -makefile.vs jconfig.vc Windows, Visual Studio 2019 Version 16 +makefile.vs jconfig.vc Windows, Visual Studio 2019-2022 version 16-17 make*.v16 -makefile.vs jconfig.vc Windows, Visual Studio 2022 Version 17 -make*.v16 -make*.v17 -makefile.b32 jconfig.vc Windows, Borland C++ 32-bit (bcc32) +makefile.b32 jconfig.vc Windows, C++Builder/RAD Studio 10.4-11 +mak*jpeg.bcb +makefile.b32 jconfig.vc Windows, Embarcadero C++ for Win32 (bcc32) +makefile.c32 jconfig.vc Windows, Embarcadero C++ for Win32 (bcc32c) +makefile.d32 +makefile.x32 jconfig.vc Windows, Embarcadero C++ for Win32 (bcc32x) +makefile.b64 jconfig.vc Windows, Embarcadero C++ for Win64 (bcc64) makefile.mms jconfig.vms Digital VMS, with MMS software makefile.vms jconfig.vms Digital VMS, without MMS software @@ -545,8 +549,8 @@ In general, it's worth trying the maximum optimization level of your compiler, and experimenting with any optional optimizations such as loop unrolling. (Unfortunately, far too many compilers have optimizer bugs ... be prepared to back off if the code fails self-test.) If you do any experimentation along -these lines, please report the optimal settings to jpeg-info@jpegclub.org so -we can mention them in future releases. Be sure to specify your machine and +these lines, please report the optimal settings to jpeg-info@ijg.org so we +can mention them in future releases. Be sure to specify your machine and compiler version. @@ -554,8 +558,8 @@ HINTS FOR SPECIFIC SYSTEMS ========================== We welcome reports on changes needed for systems not mentioned here. Submit -'em to jpeg-info@jpegclub.org. Also, if configure or ckconfig.c is wrong -about how to configure the JPEG software for your system, please let us know. +'em to jpeg-info@ijg.org. Also, if configure or ckconfig.c is wrong about +how to configure the JPEG software for your system, please let us know. Acorn RISC OS: @@ -593,7 +597,7 @@ manager, with temporary files being created on the device named by "JPEGTMP:". -Atari ST/STE/TT: +Atari ST/Mega/STE/TT/Falcon: Copy the project files makcjpeg.st, makdjpeg.st, maktjpeg.st, and makljpeg.st to cjpeg.prj, djpeg.prj, jpegtran.prj, and libjpeg.prj respectively. The @@ -1045,8 +1049,8 @@ To use: (Note that the renaming is critical!) Alternatively you can use nmake /f makefile.vs setupcopy-vc6 - This will create renamed copies of the files, which allows to repeat - the setup later. + This will create renamed copies of the files, + which allows to repeat the setup later. 2. Open the workspace file jpeg.dsw, build the library project. (If you are using Developer Studio more recent than 6.0, you'll probably get a message saying that the project files are being updated.) @@ -1057,108 +1061,100 @@ To use: appropriate location on your path. -Microsoft Windows, Visual Studio 2019 Version 16: +Microsoft Windows, Microsoft Visual Studio 2019-2022 version 16-17: We include makefiles that should work as project files in Visual Studio -2019 Version 16 or later. There is a library makefile that builds the -IJG library as a static Win32/x64/ARM/ARM64 library, and application -makefiles that build the sample applications as Win32/x64/ARM/ARM64 -console applications. (Even if you only want the library, we recommend -building the applications so that you can run the self-test.) +2019-2022 version 16-17 or later. There is a library makefile that +builds the IJG library as a static Win32/x64/ARM/ARM64/ARM64EC library, +and application makefiles that build the sample applications as +Win32/x64/ARM/ARM64/ARM64EC console applications. (Even if you +only want the library, we recommend building the applications +so that you can run the self-test.) To use: 1. Ensure you’ve checked the item "Desktop development with C++" in the Workloads tab of Visual Studio Installer. - Open the Developer Command Prompt for VS 2019, change to the source - directory and execute the command line + Open the Developer Command Prompt for VS 2019-2022, change to the + source directory and execute the command line nmake /f makefile.vs setup-v16 This will move jconfig.vc to jconfig.h and makefiles to project files. (Note that the renaming is critical!) Alternatively you can use nmake /f makefile.vs setupcopy-v16 - This will create renamed copies of the files, which allows to repeat - the setup later. + This will create renamed copies of the files, + which allows to repeat the setup later. 2. Open the solution file jpeg.sln, build the library project. a) If you are using Visual Studio more recent than - 2019 Version 16, you'll probably get a message + 2022 version 17, you'll possibly get a message saying that the project files are being updated. - b) If necessary, open the project properties and - adapt the Windows Target Platform Version in - the Configuration Properties, General section; - we support the latest version at the time of release. + b) If necessary, open the project properties and adapt the + Windows Target Platform Version (or Windows SDK Version) + in the Configuration Properties, General section. c) If you get a warning saying that a platform cannot be found, you can either * forgo the platform and ignore the warning, or * remove the platform in the Configuration Manager, or - * install the corresponding platform Buildtools in + * install the corresponding platform build tools in Visual Studio Installer (Workloads tab Optional components or Individual components tab). d) If you want to build x64 code, change the platform setting from Win32 to x64. You can build Win32 and x64 versions side by side. - e) If you want to build ARM/ARM64 code, change the platform setting - to ARM/ARM64. Ensure you've installed the ARM/ARM64-Buildtools - in Visual Studio Installer (Workloads tab Optional components - or Individual components tab). - You can build Win32/x64/ARM/ARM64 versions side by side. + e) If you want to build ARM/ARM64/ARM64EC code, change the platform + setting to ARM/ARM64/ARM64EC. Ensure you’ve installed the + ARM/ARM64/ARM64EC build tools in Visual Studio Installer + (Workloads tab Optional components or Individual components tab). + You can build Win32/x64/ARM/ARM64/ARM64EC versions side by side. 3. Open the solution file apps.sln, build the application projects. 4. To perform the self-test, execute the command line nmake /f makefile.vs test-32 for the Win32 build, or on a 64-bit system nmake /f makefile.vs test-64 for the x64 build. + Note: test options for ARM code will be added + as soon as Windows on ARM reference devices are available. + To date there are no Windows on ARM reference devices available. 5. Move the application .exe files from the Release folder to an appropriate location on your path. -Microsoft Windows, Visual Studio 2022 Version 17: +Microsoft Windows, Embarcadero C++Builder/RAD Studio 10.4-11: -We include makefiles that should work as project files in Visual Studio -2022 Version 17 or later. There is a library makefile that builds the -IJG library as a static Win32/x64/ARM/ARM64 library, and application -makefiles that build the sample applications as Win32/x64/ARM/ARM64 -console applications. (Even if you only want the library, we recommend -building the applications so that you can run the self-test.) +We include makefiles that should work as project files in C++Builder/RAD +Studio 10.4-11 or later. There is a library makefile that builds the +IJG library as a static Win32/Win64 library, and application makefiles +that build the sample applications as Win32/Win64 console applications. +(Even if you only want the library, we recommend building the +applications so that you can run the self-test.) To use: -1. Ensure you’ve checked the item "Desktop development with C++" in the - Workloads tab of Visual Studio Installer. - Open the Developer Command Prompt for VS 2022, change to the source - directory and execute the command line - nmake /f makefile.vs setup-v17 +1. Open the RAD Studio Command Prompt (or the standard Windows Command + Prompt, since the environment is set system-wide during RAD Studio + installation), change to the source directory and execute the command + line + make -fmakefile.b32 setup-cb This will move jconfig.vc to jconfig.h and makefiles to project files. (Note that the renaming is critical!) Alternatively you can use - nmake /f makefile.vs setupcopy-v17 - This will create renamed copies of the files, which allows to repeat - the setup later. -2. Open the solution file jpeg.sln, build the library project. - a) If you are using Visual Studio more recent than - 2022 Version 17, you'll probably get a message - saying that the project files are being updated. - b) If necessary, open the project properties and - adapt the Windows Target Platform Version in - the Configuration Properties, General section; - we support the latest version at the time of release. - c) If you get a warning saying that a platform cannot be found, - you can either - * forgo the platform and ignore the warning, or - * remove the platform in the Configuration Manager, or - * install the corresponding platform Buildtools in - Visual Studio Installer (Workloads tab Optional components - or Individual components tab). - d) If you want to build x64 code, change the platform setting from - Win32 to x64. You can build Win32 and x64 versions side by side. - e) If you want to build ARM/ARM64 code, change the platform setting - to ARM/ARM64. Ensure you've installed the ARM/ARM64-Buildtools - in Visual Studio Installer (Workloads tab Optional components - or Individual components tab). - You can build Win32/x64/ARM/ARM64 versions side by side. -3. Open the solution file apps.sln, build the application projects. + make -fmakefile.b32 setupcopy-cb + This will create renamed copies of the files, + which allows to repeat the setup later. + (You can use one of the other makefiles .c32, + .d32, .x32, or .b64 instead of .b32.) +2. Open the project file jpeg.cbproj, build the library project. + a) By default, the classic Borland compiler (bcc32) is used for + the Win32 build. To enable the Clang-based compiler for a + specific project, select Project > Options > C++ Compiler + and deselect the Use classic Borland compiler option. + b) If you want to build Win64 code, change the platform setting + from Windows 32 Bit to Windows 64 Bit. + You can build Win32 and Win64 versions side by side. +3. Open the project group file apps.groupproj, + build the application projects. 4. To perform the self-test, execute the command line - nmake /f makefile.vs test-32 + make -fmakefile.b32 test-32 for the Win32 build, or on a 64-bit system - nmake /f makefile.vs test-64 - for the x64 build. + make -fmakefile.b32 test-64 + for the Win64 build. 5. Move the application .exe files from the Release folder to an appropriate location on your path. |