Upgrade xmpsdk source to Adobe's current version
|Status:||Closed||Start date:||27 Dec 2013|
|Assignee:||Robin Mills||% Done:|
|Category:||xmp||Estimated time:||50.00 hours|
Issue#940 is concerned with compiler warnings. Most of them come from xmpsdk/src. I've fixed the warnings, however perhaps it is time to refresh this part of the code base.
#1 Updated by Andreas Huggel almost 5 years ago
We have subtle changes in our version of the XMP-SDK which make an upgrade a difficult project.
I recall a discussion with someone from Adobe in an XMP forum when I tried to get them to change XMP-SDK a bit but was not able to get them interested. That was related to the per-object namespace registry. It is possible that my understanding of XMP at that time was not complete. Unfortunately, that has not improved in the meantime..
#2 Updated by Robin Mills over 4 years ago
- Assignee changed from Robin Mills to Andreas Huggel
Andreas volunteered to take on this challenge in 2015.
There is a topic on the forum concerning IPTC checksum/digest. Phil (Harvey) has made a very helpful comment about this. And I think we should investigate if something needs to done about this checksum when we update the XMP support.
#8 Updated by Robin Mills over 2 years ago
Yup. I've started to look at that on August 6.
575 rmills@rmillsmbp:~/gnu/xmpsdk/XMP-Toolkit-SDK-CC201607 $ ls -alt samples/target/macintosh/intel_64/Release/ReadingXMP -rwxr-xr-x+ 1 rmills staff 103668 6 Aug 16:35 samples/target/macintosh/intel_64/Release/ReadingXMP 576 rmills@rmillsmbp:~/gnu/xmpsdk/XMP-Toolkit-SDK-CC201607 $Andreas has said something like "everything concerning XMPsdk is a big pain in the butt". I prefer to tackle difficult stuff early in a project and leave smaller matters to the end. So this is likely to get attention during Fall 2016.