Xcode 14 will no longer support building for targets older than 10.13 #282

Closed
opened 2022-06-22 18:48:05 -04:00 by nevack · 7 comments
nevack commented 2022-06-22 18:48:05 -04:00 (Migrated from github.com)

Topic.
https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes

Known Issues:

  • Xcode 14 supports building applications that target macOS 10.13, iOS 11, tvOS 11, watchOS 4, and later. Xcode incorrectly shows some unsupported deployment targets in the project editor. (93995391)
    ** Deprecations:**
  • Building for deployment to OS releases older than macOS 10.13, iOS 11, tvOS 11, and watchOS 4 is no longer supported. (92834476)

As of Xcode 14 Beta 2 this versions are not shown and Cog's project target is shown as Default, probably because main Project has target 10.12.
Also warnings are emitted on build, as subprojects have their target in range from 10.8 to 10.12.

@kode54 Christopher, what do you think about it? Do you plan to raise minimum target to 10.13 any time soon?
At least 10.13 is supported on 12-year old Macs.

Topic. https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes > **Known Issues:** > * Xcode 14 supports building applications that target macOS 10.13, iOS 11, tvOS 11, watchOS 4, and later. Xcode incorrectly shows some unsupported deployment targets in the project editor. (93995391) > ** Deprecations:** > * Building for deployment to OS releases older than macOS 10.13, iOS 11, tvOS 11, and watchOS 4 is no longer supported. (92834476) As of Xcode 14 Beta 2 this versions are not shown and Cog's project target is shown as `Default`, probably because main Project has target 10.12. Also warnings are emitted on build, as subprojects have their target in range from 10.8 to 10.12. @kode54 Christopher, what do you think about it? Do you plan to raise minimum target to 10.13 any time soon? At least 10.13 is supported on 12-year old Macs.
kode54 commented 2022-06-22 18:57:37 -04:00 (Migrated from github.com)

I will drop 10.12. But the projects can't be raised if I don't control them. The Ogg and Vorbis and Opus projects are all pretty much verbatim from upstream, but I guess I can increment the copies I have locally.

I will drop 10.12. But the projects can't be raised if I don't control them. The Ogg and Vorbis and Opus projects are all pretty much verbatim from upstream, but I guess I can increment the copies I have locally.
kode54 commented 2022-06-22 18:58:04 -04:00 (Migrated from github.com)

Let's not forget that 13.4 and newer have that toolbar bug. Has it been confirmed fixed by 14 beta 2?

Let's not forget that 13.4 and newer have that toolbar bug. Has it been confirmed fixed by 14 beta 2?
nevack commented 2022-06-22 19:12:54 -04:00 (Migrated from github.com)

Let's not forget that 13.4 and newer have that toolbar bug. Has it been confirmed fixed by 14 beta 2?

Does it require on older OS?
I have 12.5 and 13.0 right now to test it.

> Let's not forget that 13.4 and newer have that toolbar bug. Has it been confirmed fixed by 14 beta 2? Does it require on older OS? I have 12.5 and 13.0 right now to test it.
kode54 commented 2022-06-22 20:01:33 -04:00 (Migrated from github.com)

It happens on 10.13 - 10.15, at least. Maybe even 12.4. The issue was that the toolbar did not allow customization after the default options had been dragged into it.

It happens on 10.13 - 10.15, at least. Maybe even 12.4. The issue was that the toolbar did not allow customization after the default options had been dragged into it.
nevack commented 2022-06-22 20:11:16 -04:00 (Migrated from github.com)

It happens on 10.13 - 10.15, at least. Maybe even 12.4. The issue was that the toolbar did not allow customization after the default options had been dragged into it.

No issues with that for me.

> It happens on 10.13 - 10.15, at least. Maybe even 12.4. The issue was that the toolbar did not allow customization after the default options had been dragged into it. No issues with that for me.
kode54 commented 2022-06-22 20:12:54 -04:00 (Migrated from github.com)

Then we can go forward with bumping the requirements to macOS 10.13 or newer. Also, there are several places in the app that check for @available(macOS 10.13, *), one of which is a minimum point release of 10.13, but the rest are KeyedArchiver replacements that require 10.13.0, and can safely eliminate that conditional fallback.

Then we can go forward with bumping the requirements to macOS 10.13 or newer. Also, there are several places in the app that check for `@available(macOS 10.13, *)`, one of which is a minimum point release of 10.13, but the rest are KeyedArchiver replacements that require 10.13.0, and can safely eliminate that conditional fallback.
kddlb commented 2022-06-24 12:59:25 -04:00 (Migrated from github.com)

Closed as per 2c2a058126.

Closed as per 2c2a0581266c7fdca9358fcc3659209ebc7a9abc.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: chris/Cog#282
No description provided.