Compiling libjpeg

Question

Is there anyone who succeed to include libjpeg in some compiler? I tried everything: Dev C++, VS10, CodeBlocks, copy the headers and the lib by hand, add with the linker but nothing. Right now I am really confisued as there is not an official guide on how to compile it in any compiler. I would be really happy if someone could provide a tutorial on how the library can be compiled in any compiler. Thank you in advance.

Answer 1

To compile libjpeg 9 in Visual Studio 2012, here are the steps (after unzipping the archive file):

1. Download the file WIN32.MAK (for example, from http://www.bvbcode.com/code/f2kivdrh-395674-down), and place a copy in the root source code directory (possibly C:\jpeg-9, but it depends where you unzipped it). I will refer to this directory as %jpegsrc% from now on. Having this file is important; otherwise step 3 will produce an error.

2. In the Visual Studio command prompt, open to %jpegsrc%:

   cd %jpegsrc%

3. At the same command prompt, execute the following:

   NMAKE /f makefile.vc setup-v10

   This will create two Visual Studio 2010 solutions in %jpegsrc%: jpeg.sln and apps.sln.

4. Open each solution in Visual Studio 2012. Each one will prompt you to update all the projects to 2012 format. Click on “Update.” One time I did it, the prompt did not appear. In case that happens, right-click on the jpeg solution in the Solution Explorer, and choose “Update VC++ projects...,” which will produce the same prompt.

5. Save and build each solution as normal. (You have to build the jpeg.sln solution before apps.sln, since the latter depends on the former.)

Note: this process should work correctly in Visual Studio 2010, without the updating, but I have not tested it.

Update: This method still works in Visual Studio 2015 for libjpeg-9a.

Answer 2

Here is how I've built libjpeg using MinGW on Windows :

1. Get MinGW with MSYS

I've got a copy from http://sourceforge.net/projects/mingw/. Quoting from www.mingw.org :

MSYS is a collection of GNU utilities such as bash, make, gawk and grep to allow building of applications and programs which depend on traditionally UNIX tools to be present.

We will need it to run the configure script that comes with libjpeg sources.

2. Get libjpeg sources

From http://www.ijg.org/, take the Unix format package (the Windows one won't work with this procedure). I took the jpeg_8d version.

3. Prepare a building directory

I've made a temporary directory named tmp in D:\, but you could choose whatever suits your needs. The thing that matters is the name of paths in MSYS. As it brings some * Unixity * to Windows, paths cannot be used in their original form. In a nutshell:

C:\path\to\file becomes /c/path/to/file in MSYS land, an so D:\tmp becomes /d/tmp.

Decompress the libjpeg sources in D:\tmp, so you have a jpeg-8d directory in there.

Create a jpeg-build directory inside D:\tmp, it will hold the built library.

Now everything is ready for the build.

4. ./configure, make, make install

That is the mantra of building in Unix land. An option should be added to redirect the install process to D:\tmp\jpeg-build.

Run the following commands in an MSYS shell (also named MinGW shell in Windows start menu):

cd /d/tmp/jpeg-8d
./configure --prefix=/d/tmp/jpeg-build
make
make install

As an additional step, you can run make test for safety.

These commands will build both static and shared versions of libjpeg.

5. Take the goods, delete the temporaries

If everything runs fine, you can delete the D:\tmp\jpeg-8d directory, but keep the jpeg-build one. It contains:

• an include directory, containing libjpeg headers. You can move them to your compiler's headers directory.
• a lib directory, with .a file to pass to the linker. You can move them to your compiler's library directory.
• a bin directory, holding the libjpeg shared library libjpeg-8.dll and jpeg tools.
• a share directory, containing man pages for the jpeg tools.

You can now build your program and link it against libjpeg by indicating the right include and library paths.

You can find many details about the libjpeg building and installation process in install.txt inside the source package.

I hope this will be useful.

Answer 3

It is really simple to build jpeg.lib with VS10.

First, download the libjpeg source code in zip format. At the time I'm writing this you can find it here.

Then extract the contents of the zip file to your disk.

Then open a VS2010 command prompt shell (or call vcvarsall.bat on any command prompt window), cd to the jpeg source directory (jpeg-8d in the download referenced above) and type the following:

nmake -f makefile.win setup-v10

This will generate two VS2010 solutions, and a bunch of project files. The solutions are:

• jpeg.sln, which builds jpeg.lib
• apps.sln, which builds the sample applications.

Good luck!

Answer 4

If you don't happen to have Visual Studio 2010 installed, here is what works on Visual Studio 2017:

Basic / Common steps:

1. Download the latest version of libjpeg from: http://www.ijg.org/ (zip version) and extract it to a folder
2. Open the "Developer Command Prompt for VS2017"
3. Change directory (cd) to where you extracted the library source

VS 2017 Approach:

4. Include the Windows SDK v7.1A directory (required for Win32.Mak by nmake later on) by running: set INCLUDE=%INCLUDE%;c:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Include

5. Run nmake /f makefile.win setup-v15 (note the v15 for VS2017 here)

From here on follow what @AthanasiusOfAlex explained to upgrade the Visual Studio 2010 solution to the Visual Studio version you are running. If you want the Debug configuration, follow what @SteveEng explained.

Errors you might stumble across:

• If nmake fails and tells you it doesn't know how to make jconfig.h, manually rename the file jconfig.vc to jconfig.h
• If nmake fails and tells you Win32.Mak cannot be found, manually copy it from the SDK dir mentioned in step #4 to the libjpeg source directory. If you don't happen to have that SDK version installed, download the file from a trustworthy resource.
• If nmake fails and tells you it doesn't know how to make setup-v15, trial and error your way through starting with setup-v10, setup-v11, etc... These are VS versions and one of them should work as long as you have any VS version later than VS 2008 installed.

Hope this helps people going through similar pain with this.

Answer 5

If you want debug mode as well in MSVC. Follow AthanasiusOfAlex's method, build the release, then:

1. Right-click on the project and select properties at the very bottom
2. Click on configuration manager and on the active solution configuration drop-down select -new-
3. Set the name to debug and on the drop-down select copy configuration settings from release and click OK
4. Close the dialog, go to general settings and under Target Name add a d to the end so it looks like this: $(ProjectName)d
5. On Whole Program Optimization drop-down select: No Whole Program Optimization
6. Then click on the C/C++ under configuration properties on the left and on the Debug Information Format drop-down select C7 compatible (/Z7)
7. Under optimization select disabled and select NO for both Enable Fiber-Safe Optimizations and Whole Program Optimizations
8. Under preprocessor, preprocessor definitions, click on edit and use the following: WIN32 _DEBUG DEBUG _LIB _CRT_SECURE_NO_WARNINGS
9. Under code generation, under runtime library select Multi-threaded Debug DLL (/MDd)

Build and you're done!

Answer 6

I built libjpeg-turbo in Visual Studio 2022 cmd using following steps:

set PATH=D:\build\build_utils\nasm-2.16.01;%PATH%

mkdir build_jpeg

cd build_jpeg

cmake -G"NMake Makefiles" -DCMAKE_BUILD_TYPE=Release ..\libjpeg-libjpeg-turbo-2.1.0

nmake

All the exe, dll, and libs will be created in build_jpeg folder.

Answer 7

This is for VS2019 with version number 16.0

Consider the Visual Studio Version name correctly like this for creating the .sln file.

Product name Code name Version number

Visual Studio 2019 Dev16 16.0

Visual Studio 2017 Dev15 15.0

Visual Studio 2015 Dev14 14.0

Visual Studio 2013 Dev12 12.0