Is macOS Mojave not supported anymore? #88419

New Issue

Kuzey · 2021-05-20T05:20:18+02:00

Kuzey commented

2021-05-20 05:20:18 +02:00

System Information
Operating system: mac OS Mojave 10.14.6 (18G9028)
Graphics card:

Blender Version
blender-2.93.0-beta(May19th build)
blender-3.0.0-alpha (May19th build)
blender-3.0.0-alpha (May20th build)

I haven't tried blender-2.83.15-stable release but I'm thinking it'll be the same.

Short description of error

It looks like macOS Mojave is not supported all of a sudden in the latest builds, I can't launch the program anymore.

Exact steps for others to reproduce the error
Based on the default startup or an attached .blend file (as simple as possible).

**System Information** Operating system: mac OS Mojave 10.14.6 (18G9028) Graphics card: **Blender Version** blender-2.93.0-beta(May19th build) blender-3.0.0-alpha (May19th build) blender-3.0.0-alpha (May20th build) I haven't tried blender-2.83.15-stable release but I'm thinking it'll be the same. **Short description of error** It looks like macOS Mojave is not supported all of a sudden in the latest builds, I can't launch the program anymore. ![blenbend.jpg](https://archive.blender.org/developer/F10128757/blenbend.jpg) **Exact steps for others to reproduce the error** Based on the default startup or an attached .blend file (as simple as possible).

Kuzey commented

2021-05-20 05:20:18 +02:00

Added subscriber: @kuzey

blender-admin commented

2021-05-20 05:20:18 +02:00

#88677 was marked as duplicate of this issue

blender-admin commented

2021-05-20 05:20:18 +02:00

#88444 was marked as duplicate of this issue

Óscar commented

2021-05-20 05:56:31 +02:00

Added subscriber: @Oxer-1

Óscar commented

2021-05-20 05:56:31 +02:00

With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported.
The Requirements page shows this:

With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported. The Requirements page shows this: ![Requeriments.jpg](https://archive.blender.org/developer/F10128786/Requeriments.jpg)

NRH_BEATS commented

2021-05-20 06:11:16 +02:00

Added subscriber: @NRH_BEATS

NRH_BEATS commented

2021-05-20 06:11:16 +02:00

MacOS? No, thanks.
Yestersday Microsoft released new Win10 21H1 build.
Today i did a clean install, and all works super nice.

MacOS? No, thanks. Yestersday Microsoft released new Win10 21H1 build. Today i did a clean install, and all works super nice.

Anton Raves commented

2021-05-20 06:50:15 +02:00

Added subscriber: @Memento

Kuzey commented

2021-05-20 07:00:54 +02:00

In #88419#1163214, @Oxer-1 wrote:
With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported.
The Requirements page shows this:

Everything was fine up until this week and I remember Pablo Vazquez saying on Blender Today, Apple was responsible for the ARM version. I'm thinking maybe the Apple coders or even Blender coders, fixed/changed something small and it broke compatibility with older OS's?? Hope they fix it soon :)

> In #88419#1163214, @Oxer-1 wrote: > With the last 2.83.14 on macOS High Sierra 10.13.6 happens the same, not supported. > The Requirements page shows this: > > ![Requeriments.jpg](https://archive.blender.org/developer/F10128786/Requeriments.jpg) Everything was fine up until this week and I remember Pablo Vazquez saying on Blender Today, Apple was responsible for the ARM version. I'm thinking maybe the Apple coders or even Blender coders, fixed/changed something small and it broke compatibility with older OS's?? Hope they fix it soon :)

Kuzey commented

2021-05-20 07:55:00 +02:00

I just noticed the download file names are different...were these complied on a different system or with a new process?

Why is Darwin in the file names?

Anyway, hope it helps

I just noticed the download file names are different...were these complied on a different system or with a new process? Why is Darwin in the file names? Anyway, hope it helps ![blend6.jpg](https://archive.blender.org/developer/F10129042/blend6.jpg)

Ankit Meel commented

2021-05-20 09:17:31 +02:00

Added subscriber: @ankitm

Ankit Meel commented

2021-05-20 09:17:31 +02:00

Changed status from 'Needs Triage' to: 'Confirmed'

Ankit Meel commented

2021-05-20 09:17:31 +02:00

Looks like a bug in platform_apple_xcode.cmake so confirming instead of redirecting to devtalk. CMAKE_OSX_DEPLOYMENT_TARGET is set to builder's OS version and is not corrected to be OSX_MIN_DEPLOYMENT_TARGET.

Is macOS Mojave not supported anymore?

It is supported, requirements have not changed. Will be fixed soon.

I just noticed the download file names are different...were these complied on a different system or with a new process?

Yes, the builder was improved.

Looks like a bug in `platform_apple_xcode.cmake` so confirming instead of redirecting to devtalk. `CMAKE_OSX_DEPLOYMENT_TARGET` is set to builder's OS version and is not corrected to be `OSX_MIN_DEPLOYMENT_TARGET`. >Is macOS Mojave not supported anymore? It is supported, requirements have not changed. Will be fixed soon. > I just noticed the download file names are different...were these complied on a different system or with a new process? Yes, the builder was improved.

James Monteath commented

2021-05-20 09:53:42 +02:00

Added subscribers: @sebbas, @ponderz

James Monteath commented

2021-05-20 09:53:42 +02:00

The legacy and new workers are on Catalina 15.13.7.

As a developer, it might make sense to use that value as current OS. @sebbas would need to confirm this.
As a build worker, via the build pipeline, we might want to configure the specific minimum for the released version and override OSX_MIN_DEPLOYMENT_TARGET.
Otherwise, this change will need to be merged to all supported branches, including experimental and then rebuild.

I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again.

The legacy and new workers are on Catalina 15.13.7. As a developer, it might make sense to use that value as current OS. @sebbas would need to confirm this. As a build worker, via the build pipeline, we might want to configure the specific minimum for the released version and override OSX_MIN_DEPLOYMENT_TARGET. Otherwise, this change will need to be merged to all supported branches, including experimental and then rebuild. I would prefer to override `CMAKE_OSX_DEPLOYMENT_TARGET` via new build pipeline that will apply the value across all branches in case this changes again.

James Monteath commented

2021-05-20 10:14:03 +02:00

Here is the generated Info.plist file.
Not sure if that value is used.

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-*Apple*DTD PLIST 1.0*EN" "http:*www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>LSMinimumSystemVersion</key>
	<string>10.9.0</string>
	<key>CFBundleDocumentTypes</key>
	<array>
		<dict>
			<key>CFBundleTypeExtensions</key>
			<array>
				<string>blend</string>
			</array>
			<key>CFBundleTypeIconFile</key>
			<string>blender file icon.icns</string>
			<key>CFBundleTypeName</key>
			<string>Blender File</string>
			<key>CFBundleTypeOSTypes</key>
			<array>
				<string>BLND</string>
			</array>
			<key>CFBundleTypeRole</key>
			<string>Editor</string>
			<key>LSIsAppleDefaultForType</key>
			<true/>
		</dict>
	</array>
	<key>CFBundleExecutable</key>
	<string>Blender</string>
	<key>CFBundleGetInfoString</key>
	<string>2.83.15 2021-05-19, Blender Foundation</string>
	<key>CFBundleIconFile</key>
	<string>blender icon.icns</string>
	<key>CFBundleIdentifier</key>
	<string>org.blenderfoundation.blender</string>
	<key>CFBundleInfoDictionaryVersion</key>
	<string>6.0</string>
	<key>CFBundleName</key>
	<string>Blender</string>
	<key>CFBundlePackageType</key>
	<string>APPL</string>
	<key>CFBundleShortVersionString</key>
	<string>2.83.15</string>
	<key>CFBundleSignature</key>
	<string>????</string>
	<key>CFBundleVersion</key>
	<string>2.83.15 2021-05-19</string>
	<key>NSPrincipalClass</key>
	<string>NSApplication</string>
	<key>NSHighResolutionCapable</key>
	<true/>
</dict>
</plist>

Here is the generated `Info.plist` file. Not sure if that value is used. ``` <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-*Apple*DTD PLIST 1.0*EN" "http:*www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <dict> <key>LSMinimumSystemVersion</key> <string>10.9.0</string> <key>CFBundleDocumentTypes</key> <array> <dict> <key>CFBundleTypeExtensions</key> <array> <string>blend</string> </array> <key>CFBundleTypeIconFile</key> <string>blender file icon.icns</string> <key>CFBundleTypeName</key> <string>Blender File</string> <key>CFBundleTypeOSTypes</key> <array> <string>BLND</string> </array> <key>CFBundleTypeRole</key> <string>Editor</string> <key>LSIsAppleDefaultForType</key> <true/> </dict> </array> <key>CFBundleExecutable</key> <string>Blender</string> <key>CFBundleGetInfoString</key> <string>2.83.15 2021-05-19, Blender Foundation</string> <key>CFBundleIconFile</key> <string>blender icon.icns</string> <key>CFBundleIdentifier</key> <string>org.blenderfoundation.blender</string> <key>CFBundleInfoDictionaryVersion</key> <string>6.0</string> <key>CFBundleName</key> <string>Blender</string> <key>CFBundlePackageType</key> <string>APPL</string> <key>CFBundleShortVersionString</key> <string>2.83.15</string> <key>CFBundleSignature</key> <string>????</string> <key>CFBundleVersion</key> <string>2.83.15 2021-05-19</string> <key>NSPrincipalClass</key> <string>NSApplication</string> <key>NSHighResolutionCapable</key> <true/> </dict> </plist> ```

Ankit Meel commented

2021-05-20 10:29:44 +02:00

As a developer, it might make sense to use that value as current OS. @Sebastián Barschkis (sebbas) would need to confirm this.

std::filesystem (at least partially) std::optional::value(see 9734a78bc8) etc are not available for macOS 10.13, they were added in 10.15 and 10.14 respectively. If this suggestion of leaving CMAKE_OSX_DEPLOYMENT_TARGET to current macOS is implemented, someone on a newer OS version will commit code using std::filesystem and break builds for older OSes. Correct CMAKE_OSX_DEPLOYMENT_TARGET and thus correct -mmacosx-version-min=${CMAKE_OSX_DEPLOYMENT_TARGET}") ensures that such errors are caught at build time on that developer's system.

Also, overriding CMAKE_OSX_DEPLOYMENT_TARGET on the builder is a patchwork and increased workload when the code is fully capable of fixing it.

Ideal fix would be to do something like D10838: WIP attempt to set CMAKE_OSX_SYSROOT before project call: setting CMAKE_OSX_DEPLOYMENT_TARGET, CMAKE_OSX_SYSROOT etc before project call. But less than ideal, fixing it at https://developer.blender.org/diffusion/B/browse/master/build_files/cmake/platform/platform_apple_xcode.cmake$178-185 is also fine by me (fwiw).

> As a developer, it might make sense to use that value as current OS. @Sebastián Barschkis (sebbas) would need to confirm this. `std::filesystem` (at least partially) `std::optional::value`(see 9734a78bc8) etc are not available for macOS 10.13, they were added in 10.15 and 10.14 respectively. If this suggestion of leaving `CMAKE_OSX_DEPLOYMENT_TARGET` to current macOS is implemented, someone on a newer OS version will commit code using `std::filesystem` and break builds for older OSes. Correct `CMAKE_OSX_DEPLOYMENT_TARGET` and thus correct ` -mmacosx-version-min=${CMAKE_OSX_DEPLOYMENT_TARGET}")` ensures that such errors are caught at build time on that developer's system. Also, overriding `CMAKE_OSX_DEPLOYMENT_TARGET` on the builder is a patchwork and increased workload when the code is fully capable of fixing it. Ideal fix would be to do something like [D10838: WIP attempt to set CMAKE_OSX_SYSROOT before project call](https://archive.blender.org/developer/D10838): setting `CMAKE_OSX_DEPLOYMENT_TARGET`, `CMAKE_OSX_SYSROOT` etc before `project` call. But less than ideal, fixing it at https://developer.blender.org/diffusion/B/browse/master/build_files/cmake/platform/platform_apple_xcode.cmake$178-185 is also fine by me (fwiw).

Ankit Meel commented

2021-05-20 10:32:19 +02:00

I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again.

Oh for older releases which are still being built on the builder, this sounds good. But best to ask an admin or the LTS manager about that.

> I would prefer to override CMAKE_OSX_DEPLOYMENT_TARGET via new build pipeline that will apply the value across all branches in case this changes again. Oh for older releases which are still being built on the builder, this sounds good. But best to ask an admin or the LTS manager about that.

James Monteath commented

2021-05-20 10:38:38 +02:00

Yes, I am proposing a change to override cmake option to set the MIN onto the supported version release branch and would only apply when running with buildbot.
We could also ensure the cmake file is correct on all branches instead.

However, still not sure how this would be a problem in 2.83.14 though, as I don't think that file changed there.

Yes, I am proposing a change to override cmake option to set the MIN onto the supported version release branch and would only apply when running with buildbot. We could also ensure the cmake file is correct on all branches instead. However, still not sure how this would be a problem in 2.83.14 though, as I don't think that file changed there.

blender-admin commented

2021-05-20 18:25:58 +02:00

This issue was referenced by 2e7d3ad7b5

This issue was referenced by 2e7d3ad7b51bbc05cdcbbc3c055f961f3a2c28a8

Ankit Meel commented

2021-05-20 18:27:32 +02:00

Changed status from 'Confirmed' to: 'Resolved'

Ankit Meel closed this issue

2021-05-20 18:27:32 +02:00

Ankit Meel self-assigned this 2021-05-20 18:27:32 +02:00

blender-admin commented

2021-05-20 19:08:57 +02:00

This issue was referenced by 704f56d68f

This issue was referenced by 704f56d68f3ed83e6350f182fcf9aa45a19ded41

Óscar commented

2021-05-21 04:07:45 +02:00

When will 2.83.15, 2.93 Beta & 3.00 Alpha versions available to download with support for macOS 10.13+?

Ankit Meel commented

2021-05-21 06:46:55 +02:00

@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. 2.83 will be updated in a day. Ping us if it doesn't.

Philipp Oeser commented

2021-05-21 14:32:39 +02:00

Added subscribers: @BlenderBruno, @lichtwerk

Óscar commented

2021-05-24 17:47:44 +02:00

In #88419#1163720, @ankitm wrote:
@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

The 2.83.15 LTS is not updated yet.

> In #88419#1163720, @ankitm wrote: > @Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. > 2.83 will be updated in a day. Ping us if it doesn't. The 2.83.15 LTS is not updated yet.

Ankit Meel commented

2021-05-24 17:50:18 +02:00

In #88419#1165112, @Oxer-1 wrote:

In #88419#1163720, @ankitm wrote:
@Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now.
2.83 will be updated in a day. Ping us if it doesn't.

The 2.83.15 LTS is not updated yet.

The fix is in 2.83.16 #77348 (Blender LTS: Maintenance Task 2.83)

> In #88419#1165112, @Oxer-1 wrote: >> In #88419#1163720, @ankitm wrote: >> @Oxer-1 2.93, 3.0 arm and intel versions have been updated as of now. >> 2.83 will be updated in a day. Ping us if it doesn't. > > The 2.83.15 LTS is not updated yet. The fix is in 2.83.16 #77348 (Blender LTS: Maintenance Task 2.83)

Óscar commented

2021-05-25 19:38:24 +02:00

Thanks for the info!!

Evan Wilson commented

2021-05-30 03:32:01 +02:00

Added subscriber: @angadmishra

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Is macOS Mojave not supported anymore? #88419