Since adding a subproject seems to be broken, I have to go back to how I was doing this before, which led to issues with some source files finding the wrong header. This worked until the last day or two, and I can't figure out why, nor how to fix it. I tried making my target its own project, but can't get the dependencies right to build it.
My project "ControllerApp" has these targets: ControllerApp JXRLib Protobuf InternalLibrary ControllerApp ControllerApp Tests The first three targets build .a files that are linked by the ControllerApp. This was done to make it easier to control the build settings for those groups of files. Each of the targets has their header search paths set up as they need them to be. For JXRLib, which includes a bunch of things using angle brackets, the only search paths explicitly set is a recursive search path to its own source directory, plus the inherited compiler directory (/Xcode/.../usr/include). This has worked fine for over a year. Then I went and mucked with some of the other search paths in other targets, and now JXRLib is finding a "common.h" file inside Protobuf. This makes it break. It seems that one of the many .hmap files generated by Xcode is including something in protobuf, and I can't control the ordering here. What can I do? I don't really want to disable the use of .hmap, as that seems like a hack. But I don't want Xcode to include headers belonging to a different target in the project (sadly, Xcode doesn't let you specify which targets a header actually belongs to, so I mean this in a logical sense). -- Rick Mann [email protected] _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
