error LNK2019: unresolved external symbol ijlInit referenced in function "public: __cdecl CAVJPEGEncoderIJLV1_5::CAVJPEGEncoderIJLV1_5(void)" (??0CAVJPEGEncoderIJLV1_5@@QEAA@XZ)
error LNK2019: unresolved external symbol ijlFree referenced in function "public: virtual __cdecl CAVJPEGEncoderIJLV1_5::~CAVJPEGEncoderIJLV1_5(void)" (??1CAVJPEGEncoderIJLV1_5@@UEAA@XZ)
I would recommend you to migrate to our new Unified Image Codec interface, where we provide threaded JPEG (including lossless and 12-bit lossy modes, missed in IJL), JPEG2000 and PNG codecs support. Additional advantage of UIC is cross-platform support (Windows, Linux, Mac OS) on IA32, Intel64, Itanium and Intel Atom processors.
The reason someone may still be using ijl is that is was small, easy to use, and reliable. The reason someone may not want to switch to IPP is that it is none of these things. Intel would do the world a great favor by making a 64-bit IJL DLL available. People would probably even pay for it!
Thanks a lot for your feedback about the IJL. As the original develop project was stoped many year ago, It may hard to maintain/update the IJL from us. But just let you know, it is possible for you to make a 64-bit IJL dll by yourselves. if you have the "source code" of ILJ from early IPP version ipp-samples/image-codecs/jpeg-ijl.