Xcode 3.2.2 Linker warnings
Xcode 3.2.2 Linker warnings
- Subject: Xcode 3.2.2 Linker warnings
- From: Christiaan Hofman <email@hidden>
- Date: Thu, 13 May 2010 11:44:38 +0200
Since installing Xcode 3.2.2 I am getting loads of linker warnings of the type:
Directory '/path/to/a/framework/search/path' following -F not found.
Indeed, the search path is in my framework search path and also does not exist. However, the problem is that the path MAY exist, and when it exists, it is necessary (otherwise the linker will throw hard errors, which is even worse.)
So is there a way to silence these warnings, which are less than helpful in my case?
To set the context, this happens with a cross-project. The search path is to the (possible) project-relative build location for the cross-project (a framework). When I leave out this search path, when with the default Xcode pref settings, the framework cannot be found (and linked), therefore the hard errors. However, WITH the framework search path in the build settings, the path may not exist when I use a common build location in the Xcode prefs, and I get these annoying warnings. I cannot force either Xcode settings, because it may not be my account (I'm talking about an open source project, that should be working out-of-the-box for anyone who likes to build it.)
So if anyone knows a better way to handle this situation, that could also work. But I have thought about that so many times, I seriously doubt there is a better way. Until Xcode is able to follow a cross-project's setting to figure out its build location.
Apple says that this works as expected. Seriously, getting warnings is expected?
Thanks,
Christiaan
_______________________________________________
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