WIP: Hacking to get GDCM to work with libjpeg-turbo

[blowekamp]

Must work to still be done, but looks likes a plausible path forward.

PR Checklist

• [ ] No API changes were made (or the changes have been approved)
• [ ] No major design changes were made (or the changes have been approved)
• [ ] Added test (or behavior not changed)
• [ ] Updated API documentation (or API not changed)
• [ ] Added license to new files (if any)
• [ ] Added Python wrapping to new files (if any) as described in ITK Software Guide Section 9.5
• [ ] Added ITK examples for all new major features (if any)

Refer to the ITK Software Guide for further development details if necessary.

[blowekamp]

@seanm

[seanm]

Neat. So you're hacking here in ITK then I guess you'd make in PR in GDCM itself eventually?

[blowekamp]

Neat. So you're hacking here in ITK then I guess you'd make in PR in GDCM itself eventually?

I don't think I will have time to follow through with this to GDCM. Consider this just a proof of concept that switching to libjpeg-turbo should work. I'm not sure if it would be best to have GDCM support this external option for this, or if the internal jpeg library should be updated/changed. @malaterre