title: Linker error building Adobe DNG SDK on MacOS 11
body: <p>I am working on a project that uses Adobe's <a href="https://helpx.adobe.com/camera-raw/digital-negative.html#resources" rel="nofollow noreferrer">DNG SDK 1.6 library</a>, and it is supposed to work on Windows and MacOS.</p>
  <p>The library has instructions on how to build it for both platforms, but I had to figure out an error that came up on Windows with Visual Studio. I am not very experienced with big C++ projects so it was not trivial but I got it working. Most of my own code will be done in C# .Net Core, calling the native libraries using a wrapper class with P/Invoke.</p>
  <p>Now for Mac that's a different story, I have a MacOS 11 VM, installed Xcode 12.5.1 and followed the steps provided, as expected, it does not work. Bare in mind this is my first time touching Xcode and MacOS.</p>
  <p>The project I am trying to build is <code>dng_validate</code>, and it depends on two libraries built by these projects: <code>XMPFiles64</code> and <code>XMPCore64</code>.</p>
  <p>The library projects build without any hiccups, each one of them creating a &quot;.a&quot; file in the folder: <code>dng_sdk_1_6/xmp/toolkit/public/libraries/macintosh/intel_64_libcpp/Debug</code>, they are named <code>libXMPFilesStaticDebug.a</code> and <code>libXMPCoreStaticDebug.a</code> respectively.</p>
  <p>When I try to build the <code>dng_validate</code> project, I get the following error:</p>
  <p><code>Library not found for -lXMPFilesStaticDebug</code></p>
  <p>Because of the the error starting with an &quot;l&quot; instead of &quot;lib&quot;, under both libraries project settings, I changed the &quot;Executable Prefix&quot; setting to &quot;l&quot; instead of &quot;lib&quot;. Rebuilt both of them and made sure the file names changed as expected. But the error persists when trying to build the main project.</p>
  <p>Under <code>dng_validate</code>'s project settings, there is a setting called &quot;Library Search Paths&quot; and it does point to the proper aforementioned folder using a relative path. I even changed it to an absolute path to see if that would make it work.</p>
  <p>I am really lost here, does anyone have an idea of what might be causing it?</p>