> On Feb 18, 2016, at 11:37 AM, Alex Zavatone <z...@mac.com> wrote: > > In the new app's Build Settings, we had to set up the Other Linker Flags to > point to the proper directories where the linked libs were built.
You’re not just changing the Library Search Paths setting? > Since I'm using the default Xcode Build Location settings of Unique (in a > unique subfolder of Xcode's Derived Data location), this meant that the build > directory for the .a files were nested deep down in some derived data folder > with a folder name like > "MyProduct-jdhksjdhvdjkcbkjcbdsvkdsvkdsjhdkjfhdsfjkdhsf" and of course each > one was different for each of the .a files I was building. That shouldn’t matter if you’re using the build variables like $(CONFIGURATION_BUILD_DIR). —Jens
_______________________________________________ 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
