Public headers prevents making archive for distributions for projects using GPUImage

[AndrewSosna]

After headers were made public xcode produces Generic Xcode Archive instead of iOS Archive for apps, so neither AdHoc nor AppStore build can't be produced.

According to suggestion by comonitos:
http://stackoverflow.com/questions/9407712/there-is-no-share-button-in-xcode-4-3-organizer
headers needs to be moved to Project, not to public.
Maybe I'm wrong, but I moved headers to Project section now and it fixed problem.

[rivera-ernesto]

I don't have this issue. Do you think maybe "Skip install" is not set to YES for the GPUImage static library?

http://flakasoft.com/developer-tips/xcode-4-bug-solution-for-archiving-build-with-static-library/
http://stackoverflow.com/questions/5206536/archiving-project-in-xcode-incorrectly-creates-multi-application-bundle

Public headers work just fine for all the static libraries and static frameworks I use.

[AndrewSosna]

Yes, setting to Skip Install or manually moving headers to Project helps. But GPUImage is connected as Submodule as described here "Start by dragging the GPUImage.xcodeproj file into your application's Xcode project to embed the framework in your project.", changing GPUImage code means dirty state for submodule etc.
Seems like it's not only for me: #883

[rivera-ernesto]

Any static library or framework should skip install. Setting it t YES for GPUImage wouldn't be dirty.

[petsound]

This hit me as well. I tried every instruction and guess, and my app continued to compile as a Generic Xcode Archive with GPUImage commits after headers were made public. Since I was on a deadline to ship, I reverted to the 0.1.0 tag commit, which enabled me to build a normal archive.

[howanghk]

Setting Skip Install to YES didn't help.
In the GPUImage project, "Skip Install" is already set to YES. However, people are having issues.

According to the discussions on the Apple Developer Forums, in the 56th reply:

Ah FINALLY after a day of misery I find this thread. I have the same thing, a static library which has headers in the 'public' section, as it should, they are supposed to be part of the build product. With SKIP_INSTALL set to YES on the library, the actual library itself is not put in the archive (good) but the headers still are (bad) which breaks the archive. That seems like a bug to me, if you are skipping install, the headers must also be skipped. I would expect them to go into the UninstalledProducts directory which is where the not-being-installed library is and where the application which needs the headers could find them when it builds.

The only workaround I've found is to mark all the headers as 'project' so they don't get exported. But that's rather useless too, you want them exported. If you do that then you have to point any projects using the library directly into the library source tree (ie ../../MyLibA/MyLibA) so it can see the 'private' headers. That then starts to remove the whole point of having workspaces which bring things together.

And in the same thread, the 35th reply suggest that using a Xcode workspace with Skip Install solve the issue.

However, if you follow the official Adding the framework to your iOS project instructions in the GPUImage README.md, you will probably encounter the problem.

Therefore, I'd strongly suggest moving the headers back to the 'Project' section. Which won't harm and solve the Xcode archiving issue for everyone.

[BradLarson]

Yes, this was clearly a mistake. I'm moving all the headers back to "project" per your pull request.

[powellmark]

This issue appears to have returned, somewhere between Aug 20th and now.

[AndrewSosna]

I confirm. Here is another issue opened for it: #1173

[BradLarson]

Yeah, sorry, I noticed that soon after I accepted pull request #1164, but hadn't had the time to bring in a fix to undo all that. I should have checked that pull request more thoroughly than I did. I believe this is fixed now.