When to use workspaces in Xcode? Why not just add the xcodeproj file to your existing project?

I do not quite understand when to use the workspace.

Here is what I have done so far โ†’ When I need to use the static library of another project, I drag and drop the .xcodeproj file from finder into the Xcode navigator of my new project, link the libraries, add user paths and get started. I also add relevant target dependencies.

Why is it better to use a workspace? Should I use a workspace? I tried to understand the apple documentation, but it seems to me that I get everything I need without explicitly creating a workspace.

+4
source share
1 answer

Here, what I have found so far simplifies the use of static libraries. If you add the path to the static library xcodeproj file in the source tree and specify the path in the header paths in the build settings, and also set the "Search for search routes" to "YES". Then you are tuned. All you have to do is link to the static library in the build phase. Work on code completion.

+2
source

Source: https://habr.com/ru/post/1403019/


All Articles