Jim: /Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil emits the same warnings as in Xcode.
/Applications/Xcode-beta.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil-classic emits no warnings. And I just filed bug #22643916. Steve > On Sep 9, 2015, at 6:19 PM, [email protected] wrote: > > Actually, you don't need to muck with the symlink. The dsymutil command line > is pretty simple, just copy it out of the build log window, and rerun it in > terminal with dsymutil->dsymutil-classic. > > Jim > >> On Sep 9, 2015, at 6:16 PM, [email protected] wrote: >> >> The tool that builds dSYM's was rewritten (moving it from a Apple internal >> tool to one hosted by the llvm project) between 6.x and 7.x (the new version >> is called llvm-dsymutil). The old dsymutil is still around in: >> >> /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/dsymutil-classic >> >> The dsymutil in that directory is a symlink to llvm-dsymutil. You might try >> flipping the symlink back to dsymutil-classic and see if you still get the >> error. If you don't then please file a bug about this, the new & old >> dsymutils should behave the same way. >> >> Jim >> >>> On Sep 9, 2015, at 4:07 PM, Steve Christensen <[email protected]> wrote: >>> >>> I'm finally getting around to building an existing app project with Xcode >>> 7. This particular project includes another project, as a dependency, that >>> builds a third-party static library, which is then linked into the app. >>> >>> With Xcode 6.4 (and earlier), the generate dSYM task has always completed >>> with no warnings. >>> >>> With Xcode 7.0b6, I get a bunch (146) of warnings, one for each of the >>> object files: >>> >>> warning: (i386) .../libFoo.a(someObjectFile.o) unable to open object >>> file: No such file or directory >>> ... >>> warning: (x86_64) .../libFoo.a(someObjectFile.o) unable to open object >>> file: No such file or directory >>> ... >>> >>> The static library project puts the resulting .a file into one directory >>> and all the .o files into another one, if that makes a difference. Is there >>> a new Xcode 7 target build setting that I missed or an older one that now >>> is used when searching for object files? >>> >>> Steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
