Databases
StackOverflow2013
Postsdbo
POCan't link static library in XCode 4 in workspace
Body
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POCan't link static library in XCode 4 in workspace
    text
    copied!<p>So, I'm working on a project and can't get my XCode 4 workspace to behave. I have the main application as one project in the workspace. I then add the static library project into the workspace. It seems like everything is working okay. I can import files from the other project. It builds, but when I run it, I get this:</p> <pre><code>dyld: Symbol not found: _OBJC_CLASS_$_iGBC Referenced from: /var/mobile/Applications/CD00CC83-28E4-4467-96C0-0D1777E21FDA/GBA4iOS.app/GBA4iOS Expected in: flat namespace in /var/mobile/Applications/CD00CC83-28E4-4467-96C0-0D1777E21FDA/GBA4iOS.app/GBA4iOS </code></pre> <p>And crashes. It appears that although Xcode believes the library has been linked, and it builds and runs, the app doesn't <em>actually</em> have the library. But in the derived data folder, it looks like everything that should be there... is there.</p> <p><img src="https://i.stack.imgur.com/PG3dq.png" alt="Image"></p> <p>I'm going insane with XCode and all it's nuances in settings. Are there sanity checks I can go through to ensure this is working properly? What else can I do?</p> <p><strong>Edit:</strong> Project settings are valid, and I've already linked the libraries. <img src="https://i.stack.imgur.com/p9ONT.png" alt="Libraries"></p> <p><strong>Edit 2:</strong> My workspace is setup so the libraries are also in the workspace: <img src="https://i.stack.imgur.com/cWvsY.png" alt="Workspace"></p> <p>I have removed the lib.a file from the main project and removed it from the Build Phase section, and added it back numerous times. There is no "copy library into destination folder" option when adding it in this way, so I can't do that.</p>
 

Querying!

 
Guidance
An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload