* Peter O'Gorman wrote on Sat, Nov 10, 2007 at 10:08:13PM CET: > Ralf Wildenhues wrote: > > > > What about separated compilation and linking? Do the directories get > > created upon > > cc -g -c foo.c > > cc -g -o foo foo.o > > No, only when output is created directly from a source file (or when the > user runs dsymutil). The compiler calls dsymutil in the case where it is > going to delete the temporary object file (and with it the debugging > information). > > > say, these four examples: > > > > cc -g -o objsub/bar.o src/sub/foo.c
(there was a '-c' missing here) > > cc -g -o bin/foo sub/baz.o > > ar cru sub/libfoo.a sub2/bar.o sub3/baz.o > > cc [shlib_options] -o sub/foo.dylib bar/obj.o > > In these cases the foo.dSYM directory structure is not created, out of > curiosity, I tried: > cc -g -o objsub/foo src/sub/foo.c > and foo.dSYM was created in the output dir (objsub/foo.dSYM). OK. > The barf that is output during configure is mostly harmless, but is > annoying. We just need to change the tests that do compilation without > any intermediate objects to either use intermediate objects, or rm -rf > conftest.* afterwards. What happens if there is a conftest.dSYM file or directory lying around from an earlier test. Does that impact the test, so that we would also need to remove the directory beforehand? Thanks, Ralf
