BUG: Update libtiff's ITK module include paths

[blowekamp]

The update libtiff now has include that are specified as library properties and not full by ITK cmake variables.

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]

There is a separate issue in libtiff with "TIFFLIB_VERSION" not being correctly defined that is needed to get DCMTK to build.

[dzenanz]

I don't really understands what goes on here, and not enough time to dive in.

Can you describe more what is this supposed to address?

[dzenanz]

I mean, is there a compile error, configure error, what?

[blowekamp]

I mean, is there a compile error, configure error, what?

https://open.cdash.org/viewBuildError.php?buildid=10040501

After merge of #4961, there are some build issues when DCMTK in enabled that I am investigating.
It looks like there are some library properties that are not being forwarded to the DCMTK External project:
https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/ThirdParty/TIFF/src/itktiff/libtiff/CMakeLists.txt#L125

Should these target properties be replaced in ITK's 3P module CMake code, or the DCMTK configuration be updated to extract these target properties and forward to DCMTK configuration.

https://github.com/InsightSoftwareConsortium/ITK/blob/master/Modules/ThirdParty/DCMTK/CMakeLists.txt#L218

#4953 (comment)

[dzenanz]

Approving, under assumption that this fixes the issue.

[bradking]

This may be fine, but see #4953 (comment) for a more direct fix to that issue.