Header files from Static Libraries vs. Project->Archive
Header files from Static Libraries vs. Project->Archive
- Subject: Header files from Static Libraries vs. Project->Archive
- From: easco <email@hidden>
- Date: Fri, 11 Mar 2011 21:00:11 +0000 (GMT)
I'm working on an iOS application project which came from Xcode 3. I have moved to Xcode 4 and rearranged the project to remove the explicit project dependencies. At the moment, I am able to "build and run" my application in the simulator on devices etc...
In my workspace I have a number of projects that build static libraries Those static libraries also declare public headers and those headers are used by the application code.
When I try and use Project->Archive in Xcode 4, the project dependencies build my static library targets and put the header files into the build directory, but the application is unable to locate those headers so building the application target fails.
Looking in the build directory it appears that Xcode is building the static library project in one directory then setting up a symbolic link to the library file in another directory and is attempting to build the application from that second directory. Because of the symbolic link, the library's binary file is available to the application, but it appears the headers have been left behind.
How should I set up a static library target for iOS development that will ensure the header files are made available to the clients that use the static library when trying to "archive" the application for distribution?
Scott
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden