Home/ Questions/Q 8997361
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-15T23:52:45+00:00

Trying to ready metadata (e.g kCGImagePropertyExifBodySerialNumber or kCGImagePropertyExifLensModel ) from images using ImageIO framework.

  • 0

Trying to ready metadata (e.g kCGImagePropertyExifBodySerialNumber or kCGImagePropertyExifLensModel) from images using ImageIO framework.

Unfortunately during the compilation linker has a trouble: 

Undefined symbols for architecture x86_64:
"_kCGImagePropertyExifBodySerialNumber", referenced from:
      -[AppDelegate applicationDidFinishLaunching:] in AppDelegate.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

ImageIO/CGImageProperties.h is of corurse imported, and ImageIO.framework is included on the list “Linked Frameworks and Libraries” in target configuration.

It happends only when I’m trying to use kCGImagePropertyExifBodySerialNumber or kCGImagePropertyExifLensModel. It the same project kCGImagePropertyExifFocalLength, kCGImagePropertyExifExposureTime are used without any problems

Any ideas ?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Those constants seem to not be defined in the SDK versions of the ImageIO framework. You can check this yourself with the following command:

    nm /Volumes/Applications/Developer\ Tools/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.7.sdk/System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.framework/imageio | grep -F kCGImagePropertyExifBodySerialNumber

    (Edit the path to Xcode as appropriate.)

    I’m on a Lion machine at the moment, and the system version of the same framework does have it:

    % nm /System/Library/Frameworks/ApplicationServices.framework/Frameworks/ImageIO.framework/imageio  | grep -F kCGImagePropertyExifBodySerialNumber
00000000000e4898 s _kCGImagePropertyExifBodySerialNumber

    So, I suggest filing a bug and then, as a workaround, unsetting SDKROOT (“Base SDK”) in your project’s build settings. With no SDK set, it should use the frameworks and headers of the system you’re building on.

    The downside of that workaround is that if you’re using anything introduced on Mountain Lion, you won’t be able to build on Lion.

    • 0