Don't know about Xcode, it is a pre-requisite but I'm pretty sure that the Xcode development environment itself and any configuration are totally ignored by Freepascal + Lazarus. I believe Freepascal makes use of the linker, debug symbols etc that come with Xcode and that's it. (for IOS development you're using XCode in the chain given the deployment restrictions)
What I do know for certain is that using Lazarus on OSX, I had no problem at all using libs packaged inside the bundle.
Due to using Lazarus as my IDE and not having any such problems, I've not looked into how these paths are defined during the compilation process.
It is almost certainly the case that you're looking to set Freepascal options and not Xcode options - Freepascal is the compiler and I can't think of any good reason why it would read Xcode configurations over defining its own. In an ideal world Xcode wouldn't be needed at all - They'd be working to be free of the dependency, not get further in bed with it.
So look into Freepascal and OSX platform specifics - It'll be some compiler parameter or other and don't expect Xcode to have any knowledge of Freepascal in order to pass the parameter. I may be wrong of course but given you're doing it by the book in Xcode and it's still not working? I'm probably right.
If XCode can support third party compilers it'll have functionality to pass parameters, set environment variables etc which you can make use of - perhaps even the "Runtime search paths" as a variable you can pass as the relevant option to the compiler.
Reply With Quote
Bookmarks