tainly be great to know for sure. And where exactly it would
> fail spectacularly (if it did), meaning on the development machine or on a
> user's machine running an unsupported-by-Xcode system. We didn't notice that
> change and released an update to our app which
g an unsupported-by-Xcode system. We didn't notice that change and released an
update to our app which targets 10.11 as deployment target.
Regards
Markus
--
__
Markus Spoettl
___
Cocoa-dev mailing list (Coco
gar Jha wrote:
>>
>> I believe Xcode 14 has the old macOS bits (with the new iOS SDK). Try 14.1?
>>
>>> On Oct 28, 2022, at 03:51, Eyal Redler via Cocoa-dev
>>> wrote:
>>>
>>> I read somewhere (can't recall where) that xcode 14 will n
somewhere (can't recall where) that xcode 14 will not support
>> deployment target < macOS 10.13.
>> I was bracing myself for having to somehow develop my app on two machines
>> for a while or ditching my pre 10.13 users but after installing xcode 14 on
>&g
I believe Xcode 14 has the old macOS bits (with the new iOS SDK). Try 14.1?
> On Oct 28, 2022, at 03:51, Eyal Redler via Cocoa-dev
> wrote:
>
> I read somewhere (can't recall where) that xcode 14 will not support
> deployment target < macOS 10.13.
> I was bracing my
I read somewhere (can't recall where) that xcode 14 will not support deployment
target < macOS 10.13.
I was bracing myself for having to somehow develop my app on two machines for a
while or ditching my pre 10.13 users but after installing xcode 14 on my new M1
machine I found out th
-rags
> On Dec 1, 2014, at 12:06 PM, Quincey Morris
> wrote:
>
> — Use a third-party tool such as Deploymate.
What a great tool!
Purchased it last night and easily identified 6 APIs in two projects that were
not supported on 10.5.
Thanks all!
- rags
> On Dec 1, 2014, at 12:16 PM, Milen Dzhumerov wrote:
>
> you don’t actually need to run the old Xcode, you only need the SDK itself
Ok, this seems like the easiest approach. Thanks.
-rags
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Ple
On Dec 1, 2014, at 10:33 , Raglan T. Tiger wrote:
>
> I see no warnings about using APIs not supported in 10.5.
>
> My program crashes on 10.5.8 ... I do not haveth report from the customer as
> yet.
>
> Is there an efficient way to isolate APIs not supported ?
There’s no direct way to do thi
I set my deployment target to be 10.5.
I see no warnings about using APIs not supported in 10.5.
My program crashes on 10.5.8 ... I do not haveth report from the customer as
yet.
Is there an efficient way to isolate APIs not supported ?
-rags
> values are going to kill me one of these days.
Deployment Target is the earliest OS on which you want to run.
Base SDK is the latest OS from which you want to use API.
You should generally leave Base SDK set to “Latest” and avoid Current. Current
means “use the headers and libraries and framewor
On Feb 10, 2013, at 7:09 PM, Jerry Krinock wrote:
> In an .app project, the Build Setting named Deployment Target in Xcode gets
> compiled into the product's Info.plist as LSMinimumSystemVersion, and this is
> the minimum Mac OS X version in which the product will laun
On 2013 Feb 10, at 21:12, Charles Srstka wrote:
> What you're looking for is the LC_VERSION_MIN_MACOSX (or
> LC_VERSION_MIN_IPHONEOS) load command, inside the Mach-O file. You can look
> at a Mach-O file's load commands by using otool -l.
Thank you, Charles. I was able to confirm the problem
On Feb 10, 2013, at 9:09 PM, Jerry Krinock wrote:
> In an .app project, the Build Setting named Deployment Target in Xcode gets
> compiled into the product's Info.plist as LSMinimumSystemVersion, and this is
> the minimum Mac OS X version in which the product will launch.
>
In an .app project, the Build Setting named Deployment Target in Xcode gets
compiled into the product's Info.plist as LSMinimumSystemVersion, and this is
the minimum Mac OS X version in which the product will launch.
In a .plugin project, there is also a Deployment Target in Xcode, but I
Presuming that the firstgen iPod touch has iOS 3.x on it, it is probably
crashing here:
> self.window.rootViewController = self.tabBarController;
Since rootViewController was introduced to UIWindow in iOS 4.0. Pre-iOS 4.0
you need to use (from what I recall):
[self.window addSubview:self.tabBarC
Hello, all ...
I'm working on an app that has to work on first-gen iPod touch devices. I set
the deployment target to 3.1 and made sure armv6 was specified such that my app
now at least launches on said firstgen iPod touch. However, it hangs before
showing the tab bar or first view contr
On Thu, 10 Nov 2011 07:43:01 -0800, Matt Neuburg said:
>On Tue, 08 Nov 2011 21:59:59 +0530, Sasikumar JP said:
>>Is it possible to set the iPad minimum deployment target as iOS 5 and iPhone
>>deployment target as ios 4.2
>
>I don't think so. Most apps that I'm fam
On Tue, 08 Nov 2011 21:59:59 +0530, Sasikumar JP said:
>Is it possible to set the iPad minimum deployment target as iOS 5 and iPhone
>deployment target as ios 4.2
I don't think so. Most apps that I'm familiar with, if they have issues like
this, simply have two different a
Hi,
I have a iPhone application in the app store. This version is supporting
from iOS 4.2 release. I am planning to add a support for iPad as an universal
application. Is it possible to set the iPad minimum deployment target as iOS 5
and iPhone deployment target as ios 4.2. If this
Thanks for that link Kyle, from that reference it appears that it is not
possible to weak link classes in MacOS X, so the only way to use my subclasses
of CAShapeLayer would be to move them all to a separate bundle and only load
that bundle when running on 10.6.
Something I wondered about was
On Tue, Jan 11, 2011 at 10:40 AM, Wim Lewis wrote:
> You might be able to weakly link the class, in which case dyld will not
> complain but messages to CAShapeLayer will return nil. I don't remember on
> which OS revs it became possible to weak link a class, though. (Weak linking
> C symbols ha
On 10 Jan 2011, at 11:42 PM, Kenneth Baxter wrote:
> Hi, I have a project I'm working on which needs to run on 10.5 and 10.6. I
> have various things enabled or disabled using:
>
> if (floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_5) ...
>
> but I also have some places in my code where
Hi, I have a project I'm working on which needs to run on 10.5 and 10.6. I have
various things enabled or disabled using:
if (floor(NSAppKitVersionNumber) > NSAppKitVersionNumber10_5) ...
but I also have some places in my code where I want to use a CAShapeLayer
subclass in 10.6 and an alternat
, 2009, at 6:34 PM, Lorenzo Thurman wrote:
I have a program which needs to run under 10.4, but I used a
method that
is only defined for 10.5. No biggie, it was easy enough to
replace it
with something that works for 10.4. The problem is that I didn't
find
this out until I ran the app
t I used a method that
>> is only defined for 10.5. No biggie, it was easy enough to replace it
>> with something that works for 10.4. The problem is that I didn't find
>> this out until I ran the app under 10.4. My apps deployment target is
>> set to 10.4, and the base S
works for 10.4. The problem is that I didn't find
this out until I ran the app under 10.4. My apps deployment target is
set to 10.4, and the base SDK is set for 10.5. My question is:
If I inadvertently use a 10.5 only method, is there a way for me to be
warned at compile time? I know I can u
I have a program which needs to run under 10.4, but I used a method that
is only defined for 10.5. No biggie, it was easy enough to replace it
with something that works for 10.4. The problem is that I didn't find
this out until I ran the app under 10.4. My apps deployment target is
set to
28 matches
Mail list logo
