<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On 24 mars 08, at 14:20, Steve Kalkwarf wrote:<br class="Apple-interchange-newline"><blockquote type="cite"><blockquote type="cite"><blockquote type="cite"><span class="Apple-style-span" style="-webkit-text-stroke-width: -1; ">OK. If targeting 10.4, would this also run on 10.5?</span></blockquote></blockquote><br>Yes, the SDK version reflects the available APIs for the build, <br>not a minimum system version. You could also target 10.5, and it <br>would run on 10.4.<br><br>If you look at NSApplication.h, you'll see:<br><br>#if MAC_OS_X_VERSION_MAX_ALLOWED >= MAC_OS_X_VERSION_10_5<br><br>It's this macro (and other ones like it) that honor the SDK version.</blockquote><div><br></div><div>Thank you, this is clear no.</div><br><blockquote type="cite"><blockquote type="cite"><blockquote type="cite">Second, if this were my project, I'd change the architecture<br></blockquote></blockquote><blockquote type="cite"><blockquote type="cite">settings to $(NATIVE_ARCH) for development and "i386 ppc" for deployment.<br></blockquote></blockquote><blockquote type="cite"><br></blockquote><blockquote type="cite">OK, the only issue is that the caml code is not compiled <br></blockquote><blockquote type="cite">universally. So to build a UB I need to compile it on several machines.<br></blockquote><br>I would have assumed that the build was universal. There's a technote:<br><br><<a href="http://developer.apple.com/opensource/buildingopensourceuniversal.html">http://developer.apple.com/opensource/buildingopensourceuniversal.html</a>><br><br>that explains how to make a traditional makefile-type project <br>build universally.</blockquote><div><br></div>Thank you very much for the link, it's very interesting.<br><div><br></div><div>Unfortunately, I don't know how to produce ocaml ppc binaries on an intel machine. (I think there was a post about how to cross-compile using ocaml, but I'd need to dig it out.)</div><br><blockquote type="cite"><blockquote type="cite">My question was: why does calling xcodebuild with the variable <br></blockquote><blockquote type="cite">OCAMLLIBDIR set work? It must be configured somewhere in the <br></blockquote><blockquote type="cite">project (to add this variable to the list of header paths) but <br></blockquote><blockquote type="cite">searching yielded nothing.<br></blockquote><br>Ah. Because several of the makefiles used that environment <br>variable to prefix some paths. For example, the top level <br>Makefile, likes 243:244<br><br><blockquote type="cite">tools/%: tools/%.ml<br></blockquote><blockquote type="cite">ocamlc -o tools/$* -I $(OCAMLLIBDIR)/labltk labltk.cma tools/$*.ml</blockquote></blockquote><div><br></div><div>Ah, I see. What confused me is that the Makefile does not appear in Xcode, and inspecting the Target does not seem to reveal anything. Do you have links to the interaction between Xcode and Makefiles?</div></div><br><div>Thanks again, it was very helpful.</div><div><br></div><div>Alan</div></body></html>