Aleksi Sapon

We're also having this issue with a few different Windows builds. It started failing without any changes on our side. We're also using vcpkg. From what I can tell this...

Have you tried updating the dependencies? This might still compile without needing changes if there are no breaking changes.

Can you also try compiling with LDC?

I got it to compile as 32 bit on Windows 8.1, but I can't get it to link, DMD's OPTLINK gives me an "Error 16: index range"

Building in release mode using DMD on OS X also has broken linking, here's the error: ``` Undefined symbols for architecture x86_64: "_D3std9exception138__T12errnoEnforceTbVAyaa52_2f7573722f6c6f63616c2f43656c6c61722f646d642f322e3036362e312f696e636c7564652f64322f7374642f737464696f2e64Vmi717Z12errnoEnforceFNfbLAyaZb", referenced from: _D3std5stdio4File14__T7rawReadTvZ7rawReadMFAvZAv in gbaid.o ld: symbol(s)...

I have successfully built it on 64bit Ubuntu in release mode, but the environment I'm using is headless, so I can't do a full test (no video or audio output)....

Yes please release a new version! If the library has been changed to "live at head" versioning, please let us know so I can update vcpkg to the new scheme.

For anyone else having this issue: add `--cmake-build-args="-DPXR_ENABLE_PRECOMPILED_HEADERS=OFF"` to your build command line to workaround it.

> I think the most recent suggestion was to add a new metadata item called `exif-data-json` which would just be a simple dump of the parsed exif as a chunk...

Clangd at the very least doesn't understand or respect that link, and I consider the gold standard of code analysis tools.