Re: [Libjpeg-turbo-devel] problem when using jmorecfg.h and windows.h

[DRC <dco...@us...>]

On 4/18/14 3:53 AM, Vincent Torri wrote:
> indeed, if CMake is the preferred solution to build libjpeg-turbo on
> Windows, then it might be the problem. I can provide autotool stuff to
> fix that, if you tell me what is needed.

I'm actually surprised that our code built at all with autotools and 
MinGW, and I'd be even more surprised if it actually ran.  Maybe it 
works under MSYS, but it definitely doesn't work when cross-compiling 
using MinGW on Linux.  The resulting DLL contains bogus dependency 
information and won't execute.

Autotools and MinGW has never been a supported configuration for 
libjpeg-turbo.  I don't understand why you can't use CMake to build our 
code.  It doesn't require you to use CMake to build your application-- 
just the JPEG library.

There's a lot more to getting autotools to work with Windows builds, and 
even if we could get it working, that configuration would never be 
tested, so it would be prone to breakage.  The larger issue is-- if 
users expect it to work, then I'm expected to support it, and I'm not in 
a good position to do so.  I definitely do not want some other project's 
build instructions for our code to include something that isn't supported.

I am open to being convinced otherwise, if you have a compelling 
arguments that demonstrates why autotools is necessary in some cases.  I 
would still not be willing to officially document or support it, but if 
you absolutely do need to use autotools, then I'd be willing to check in 
an unsupported patch to jconfig.h.in, if that is sufficient to fix this 
issue.