Top of trunk doesn't build

[Dave Riggle]

I did a fresh checkout and build. Here are the errors I got.

Ld "build/Sparkle.build/Release (GC dual-mode; 10.5-only)/relaunch tool.build/Objects-normal/ppc/relaunch" normal ppc
cd /Users/dave/Downloads/Sparkle
setenv MACOSX_DEPLOYMENT_TARGET 10.4
/Developer/usr/bin/gcc-4.2 -arch ppc -isysroot /Developer/SDKs/MacOSX10.5.sdk "-L/Users/dave/Downloads/Sparkle/build/Release (GC dual-mode; 10.5-only)" "-F/Users/dave/Downloads/Sparkle/build/Release (GC dual-mode; 10.5-only)" -filelist "/Users/dave/Downloads/Sparkle/build/Sparkle.build/Release (GC dual-mode; 10.5-only)/relaunch tool.build/Objects-normal/ppc/relaunch.LinkFileList" -mmacosx-version-min=10.4 -dead_strip -framework AppKit -o "/Users/dave/Downloads/Sparkle/build/Sparkle.build/Release (GC dual-mode; 10.5-only)/relaunch tool.build/Objects-normal/ppc/relaunch"

ld: warning: directory '/Users/dave/Downloads/Sparkle/build/Release (GC dual-mode; 10.5-only)' following -L not found
ld: warning: directory '/Users/dave/Downloads/Sparkle/build/Release (GC dual-mode; 10.5-only)' following -F not found

[Andy Matuschak (andymatuschak)]

I can't reproduce this. What version of Xcode are you using? Did you get ToT from Github?

[Hofman (cmhofman)]

First of all, these are not errors but warnings. They say that ld cannot find a directory in the framework and library search path (which is automatically added by Xcode). Since Xcode 3.2.2 the linker warns for this, even if this is not necessarily a problem, and you cannot turn it off (I consider this a bug, as it sometimes is unavoidable). I can reproduce this the first time I build after removing the build directory (note that Clean does not do this, you have to do that manually). Apparently the linker checks this before the build directory is created (at least for the "relaunch tool" target, for the Sparkle target it's probably created earlier for the Copy phases). That should of course not happen, but it's an Xcode bug: they should either not warn about something that happens in normal usage, or make sure the directory is created early enough. And worse, Xcode does not offer any way to avoid these useless warnings.