<!doctype html public "-//W3C//DTD W3 HTML//EN">
<html><head><style type="text/css"><!--
blockquote, dl, ul, ol, li { padding-top: 0 ; padding-bottom: 0 }
--></style><title>Re: [Biococoa-dev]
BCFoundation-Tests</title></head><body>
<div>At 6:27 PM +0100 2/26/05, Alexander Griekspoor wrote:</div>
<blockquote type="cite" cite>
<blockquote type="cite" cite>
<blockquote type="cite" cite>So are we now dropping 10.2.8 support?
Maybe only the test framework can be 10.3 and the rest
10.2.8?</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
I knew this was going to be confusing!<br>
The way I understand it is that only 'native targets' can be set to a
different deployement OS X target. Hence my question about upgrading
the legacy targets to native targets. I want to wait for Alex's input
before upgrading because this is a no-return process, and I want to
make sure this is the way he was thinking of doing it for Foundation
(10.2) and AppKit (10.3).</blockquote>
</blockquote>
<blockquote type="cite" cite><br>
Sorry guys, little time today. My experience is that converting the
target to a native XCode format does prevent you from opening the file
in Project Builder (no problem for me). The nice thing is that it
STILL allows you to build against the 10.2.8 SDK, so no we won't move
to 10.3 only for the foundation..... Go ahead Charles, it should be no
problem. (yes, indeed the target icon will change in an
application/framework instead of the red-circle. I'll comment on the
other emails later tonight... Great work on the sequence classes
guys!<br>
Cheers,<br>
Alex<br>
</blockquote>
<blockquote type="cite" cite>Ps. unfortunately it seems that the
target SDK can only be set for the complete XCode file (using get info
on the project icon), we can leave it at 10.2.8 for the moment, we'll
see what the future brings. Converting to a native target has nothing
to do with this though, so forms no problem.</blockquote>
<div><br></div>
<div>The problem is the OCUnit needs the Mac OS X deployment target in
the build settings to be set to X.3, otherwise I get the compiler
message:</div>
<div><font face="Courier" size="+1"
color="#000000">`-fobjc-exceptions' ignored because
MACOSX_DEPLOYMENT_TARGET is "10.2"</font></div>
<div>It works fine for now, but may not behave properly if a method
throws an exception.</div>
<div><br></div>
<div>Now, there is one thing I don't understand very well the
differences between the two following settings:</div>
<div>* Cross-Develop using Target SDK in the project General
settings</div>
<div>* Mac OS X deployment target in the build settings of individual
targets</div>
<div><br></div>
<div>Maybe the first is only for the headers used by the compiler and
the headers, and the second is for the linking.</div>
<div><br></div>
<div>In fact, the way it is setup now, the SDK may not even be taken
into account, according to Apple's documentation, because we are using
a non-native target. This is the warning that you should be able to
see on this file on your computer (Apple's doc):</div>
<div
>file:///Developer/Applications/Xcode.app/Contents/Resources/English.<span
></span>lproj/Xcode_Help/Building/chapter_6_section_10.html</div>
<div><br></div>
<div>So, we think we are using the 10.2.8 SDK but we are probably not
if our machines are on 10.3!! So updating to a native target seems in
fact necessary if we want to use the 10.2.8 SDK.</div>
<div><br></div>
<div>Anyway, if we want to have different targets compatible with
different OS X versions, we have to find a way to do it. It seems the
prefix header is where the action is. I will try to read more about
this.</div>
<div><br></div>
<div>charles</div>
<div><br></div>
<x-sigsep><pre>--
</pre></x-sigsep>
<div>Help science go fast forward:<br>
http://cmgm.stanford.edu/~cparnot/xgrid-stanford/<br>
<br>
Charles Parnot<br>
charles.parnot@stanford.edu<br>
<br>
Room B157 in Beckman Center<br>
279, Campus Drive<br>
Stanford University<br>
Stanford, CA 94305 (USA)<br>
<br>
Tel +1 650 725 7754<br>
Fax +1 650 725 8021</div>
</body>
</html>