Re: Xcode uses the wrong version of lib because of hidden search paths?
Re: Xcode uses the wrong version of lib because of hidden search paths?
- Subject: Re: Xcode uses the wrong version of lib because of hidden search paths?
- From: Christiaan Hofman <email@hidden>
- Date: Tue, 24 Aug 2010 23:23:49 +0200
On Aug 24, 2010, at 23:01, G S wrote:
>> Or you can just use different LIBRARY_SEARCH_PATHS build settings.
>
> Well, that sounded like a good idea, but unfortunately it doesn't work
> because you still have to explicitly add the libs to the project. At
> that point, Xcode invisibly adds their parent directories to the
> library search paths and causes the error.
>
Perhaps you should declare them relative in the Get Info window? Using relative paths (for instance SDK relative for system provided libraries and frameworks) is now the default, as was explained on June 2 on this list.
Or why can't these absolute paths not be the right ones for the target?
> The only way to fix the project (as far as I can tell) is to open it
> in a text editor and delete the paths that Xcode added, since they
> don't get cleaned up even if you remove the libs using the GUI.
>
This is strange. In my projects I don't even have these. And I've never edited the project manually. Though it may be because I have no links to custom libraries.
> So it looks like giving the libs different names is the only
> workaround, and this means I still have to manually add and remove
> them from the project every time I want to switch between simulator
> and device (or write a pre-build script that'll swap the libs for me).
Perhaps another way to link to another version is to use the -link_file argument, though that only works for linking and not for compiling.
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