> On 15 Apr 2016, at 16:15, Steve Mills <sjmi...@mac.com> wrote: > > On Apr 15, 2016, at 10:07 AM, Dave <d...@looktowindward.com> wrote: > >> Hi, >> >> This is so annoying, I’ve been searching for info on this, but all I can >> find is for older versions of XCode. Apparently one way of doing it was to >> use “SourceTrees” but it looks like this has been removed from XCode 7. >> >> The other info is to set “Framework Search Paths” but that doesn’t work >> either. I think I’ve tried every combo of setting header paths and nothing >> seems to get it to point to the right files. >> >> If anyone has any ideas on this please let me know. > > > Since we can't see your project, we can only throw out ideas that you might > have or might not have tried. I take it these headers are in a folder of > their own, since you mentioned using <xxx/yyy.h>. If so, are you adding the > *parent* folder of the xxx folder to the search paths or the actual xxx > folder? Try both, but I would expect the former to be the correct way. > If you can't get it to work, why not add the headers to a new .framework. I > think you said they're normally in a framework, but for this project they're > not. So, put them into some other special framework whose sole purpose is to > vend headers. I'm not sure if the source (if there is source) can simply be > added to your target in this case. Not sure why you can't use a framework for > this project.
I think I’ve found the problem. Normally, the App uses the .framework files and they are either embedded in the app or they are referenced in /Library/Frameworks, however, for the Test Project, I’m actually including my own version of the source code which mirrors the API of the third party framework. In the original workspace, these two projects are sub-projects of the main app and this seems to work ok. I then copied the folder containing the .workspace file and removed a few unwanted projects from the copy. When I look in the copied workspace, the dependancy on the stand-in projects has gone missing. If I manually compile the stand-in projects then it works. I’ve reset the dependancy now and it works again. My mistake was in thinking that adding the sub-project instead of the framework used a different set of header paths. Thanks for the help. All the Best Dave _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
