Cool that you tried a rebuild. I never got a chance to, but I'm not sure how current that Flurry code is anyway. I think the calumr/flurry project needs to be updated completely for Xcode 10.2 and 10.14. I'll give it a go to see what I get. However, I'm not sure what that will tell us about OpenGL incompatibilities.
So I re-built Flurry from source code (calumr github version) with a moderate amount of "modernization" in Xcode 10.2 and it runs on a normal supported machine against the 10.14.4 SDK. So at least that's a start.
I installed it as Flurry+:
One thing for sure, this version of Flurry is different than the stock Mojave one's for a while. Take a look at the preferences options in the code:
The Mojave "stock" versions of this screensaver are not as configurable - much simpler. So the code base is not only old but different. 10.14.4 version of Flurry says 10.8 while this code is internally Flurry 1.4 (may not mean anything). Was HS Flurry like this? This may actually be a independent attempt to re-create Apple's Flurry - don't know - but it works just as well (even more customizable)
This was a quick and dirty trial to get an Xcode project that builds and runs. So tons of warnings and OpenGL deprecation notices. Also the preferences pane above is not yet functional, in fact if selected the saver crashes (blank screen - but removing it from ~/Library/ScreenSavers is sufficient to restore the preferences pane) Work in progress...
Anywho, the objective is to have code that builds so we can test on unsupported machines with various versions of OpenGLs or other "accelerators" (just in case Apple breaks more of our stuff )
I will post the project on a github repository @Spiramira when I'm done, so all can play with it. It still needs a lot of modernization and cleaning of old Objective-C code and macOS sdks just to bring it up to today's standards.
[doublepost=1555114414][/doublepost]
So I re-built Flurry from source code (calumr github version) with a moderate amount of "modernization" in Xcode 10.2 and it runs on a normal supported machine against the 10.14.4 SDK. So at least that's a start.
One thing for sure, this version of Flurry is different than the stock Mojave one's for a while. Take a look at the preferences options in the code:
View attachment 831848
The Mojave "stock" versions of this screensaver are not as configurable - much simpler. So the code base is not only old but different. 10.14.4 version of Flurry says 10.8 while this code is internally Flurry 1.4 (may not mean anything). Was HS Flurry like this? This may actually be a independent attempt to re-create Apple's Flurry - don't know - but it works just as well (even more customizable)
This was a quick and dirty trial to get an Xcode project that builds and runs. So tons of warnings and OpenGL deprecation notices. Also the preferences pane above is not yet functional, in fact if selected the saver crashes (blank screen - but removing it from ~/Library/ScreenSavers is sufficient to restore the preferences pane) Work in progress...
Anywho, the objective is to have code that builds so we can test on unsupported machines with various versions of OpenGLs or other "accelerators" (just in case Apple breaks more of our stuff )
I will post the project on a github repository @Spiramira when I'm done, so all can play with it. It still needs a lot of modernization and cleaning of old Objective-C code and macOS sdks just to bring it up to today's standards.
[doublepost=1555114414][/doublepost]
That's a wild utility. Does it work?
So I re-built Flurry from source code (calumr github version) with a moderate amount of "modernization" in Xcode 10.2 and it runs on a normal supported machine against the 10.14.4 SDK. So at least that's a start.
One thing for sure, this version of Flurry is different than the stock Mojave one's for a while. Take a look at the preferences options in the code:
View attachment 831848
The Mojave "stock" versions of this screensaver are not as configurable - much simpler. So the code base is not only old but different. 10.14.4 version of Flurry says 10.8 while this code is internally Flurry 1.4 (may not mean anything). Was HS Flurry like this? This may actually be a independent attempt to re-create Apple's Flurry - don't know - but it works just as well (even more customizable)
This was a quick and dirty trial to get an Xcode project that builds and runs. So tons of warnings and OpenGL deprecation notices. Also the preferences pane above is not yet functional, in fact if selected the saver crashes (blank screen - but removing it from ~/Library/ScreenSavers is sufficient to restore the preferences pane) Work in progress...
Anywho, the objective is to have code that builds so we can test on unsupported machines with various versions of OpenGLs or other "accelerators" (just in case Apple breaks more of our stuff )
I will post the project on a github repository @Spiramira when I'm done, so all can play with it. It still needs a lot of modernization and cleaning of old Objective-C code and macOS sdks just to bring it up to today's standards.
[doublepost=1555114414][/doublepost]
That's a wild utility. Does it work?
Great work! I notice you removed the "Flurry_Prefix.pch" (I also had error compiling build with it) and perhaps you removed also Appkit and Foundation in "other frameworks". Do you have kept the OpenGL framework reference or removed? Because I guess it could work even without them.
I guess the main required are Cocoa and Screensaver frameworks.
Could you try directly from Xcode from top menu "edit" and "convert" the project to objective-c ARC ?
Does it still build succeeded ?
Great work! I notice you removed the "Flurry_Prefix.pch" (I also had error compiling build with it) and perhaps you removed also Appkit and Foundation in "other frameworks". Do you have kept the OpenGL framework reference or removed? Because I guess it could work even without them.
I guess the main required are Cocoa and Screensaver frameworks.
Could you try directly from Xcode from top menu "edit" and "convert" the project to objective-c ARC ?
Does it still build succeeded ?
- create new Xcode 10.2 screensaver project
- disable ARC (since this is an old project) in build setting (Apple Clang - Language - Objective-C)
- import code (without precompile header now - even though it helps with compile speed)
- Add frameworks Cocoa, ScreenSaver, OpenGL
- Add resources (even though the preferences pane is currently broken) converting nibs and converting plist strings to UTF16
- rename the product name to Flurry+ (so it doesn't conflict with existing version of course)
You end up with tons of warnings (mainly deprecated methods etc...) but it builds and runs in Preferences as a legitimate screen saver.
I kept OpenGL , since I have yet to see any non-GL based rendering in this code. If Flurry works in non-GL-accelerated mode on .5b2 and beyond, then Apple's codebase must be different. In fact they may be Metal based now. It's worth checking the .5+ screensavers link tables to see what frameworks and libs are actually linked in. I haven't done so yet.
It's really up to you and if you feel like going back to .3 if it fails. I did because mine auto updated and yacked on the patch version. Make sure you have a fresh Mojave Patch tool v1.3. AND a secondary USB with .3 on it so you can go back if you need to. Go to Dosdude's page and read the latest.
Good luck!
One more thing...
Test booting to your USBs, before you commit to the upgrade. Sometimes you'll get the NO (circle with a line through it) if the USB wasn't prepared correctly or there was a "glitch" with the creation. My lessons learned and what I've read.
Ohh my!!! I think this is what happens to me, the creation of the usb went well, but never tested before trying the update... So right now I'm screwed, until i figure out how to create another usb...
Ohh my!!! I think this is what happens to me, the creation of the usb went well, but never tested before trying the update... So right now I'm screwed, until i figure out how to create another usb...
It happened to me too and I had to borrow one of my student's Mac to make a new one. Since, I have added a Mojave VM to my wife's Windows box for a backup Mac.
I've been playing with 10.14.5 DP2, and while I haven't made any significant progress, I noticed one really weird thing: My MacBook7,1's keyboard and touchpad now work without any USB patches, which hasn't been the case since High Sierra. Anybody else find this?
I've been playing with 10.14.5 DP2, and while I haven't made any significant progress, I noticed one really weird thing: My MacBook7,1's keyboard and touchpad now work without any USB patches, which hasn't been the case since High Sierra. Anybody else find this? Or am I crazy?
I upgraded to 10.14.4 in my MacPro 3,1 with Metal graphics card and it works well. AFAIK the problem only exists with unsupported graphic cards. If you have a supported GTX 680 or 770 or similar, you should be good to go
I have a GTX 770 installed so I went ahead and upgraded. Downloading 10.14.4 on my Mac Pro 3,1 running 10.14.3 kept crashing the installer after the download so I downloaded 10.14.4 on a MacBook Pro laptop running Mojave natively.
So far, my Mac Pro 3,1 is working fine after the full install to 10.14.4.
Will running 10.14.4 on a 5.1 Mini without the Siri fix, no Chess, and no Flurry cause any other issues to happen? SO far I am running without them, not a big deal, Type to Siri still works, and I never open Chess or use Flurry anyway.
MacPro3,1
MacPro4,1
iMac8,1
iMac9,1
iMac10,x
iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
MacBookPro4,1
MacBookPro5,x
MacBookPro6,x
MacBookPro7,1
MacBookPro8,x
Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT)/8800M(GT), 9400M/9600M(GT), 320M/330M)
Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)
Minor Issues
Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).
Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
Trackpad multi-finger gestures on both machines not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
Major Issues
AMD Radeon HD 5xxx/6xxx series GPU acceleration"]
Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series video card. Mojave will be almost unusable without graphics acceleration. This includes the 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these machines, you'll need to disable the AMD video card (This will work on MacBook Pro 8,2 and 8,3 systems ONLY. You CANNOT disable the AMD GPU in an iMac.) Weird colors will also be produced when running Mojave with one of these video cards installed/enabled. To disable the AMD GPU on a 2011 MacBook Pro 8,2 or 8,3, follow the guide found here.
When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-compatible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.
Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.
Current Issues by Hardware
Minor Issues
Graphics anomalies:
All machines
Built-in iSight camera:
All machines, hit or miss
Trackpad:
MacBook5,2 and MacBook 4,1
Major Issues
AMD GPU acceleration:
All machines with a Radeon HD 5xxx or 6xxx series GPUs (these systems will be almost unusable when running Mojave. More details are located in the Current Issues section above.)
App Store Crashing:
All machines with Radeon HD 4xxx series GPUs
AMD GPU support:
MacPro3,1
Installation:
To install on your machine, you can download and run the macOS Mojave Patcher application, which will let you download a copy of the latest installer app from Apple and create a bootable installer drive for use on unsupported Macs. It contains all the patches necessary to achieve the hardware support listed above. The installation guide can be found here and an installation guide video here.
Alternative Installation:
More advanced users may consider using @0403979's macOS Patcher Tool, which is a command line-based tool that provides the same hardware support as @dosdude1's Mojave Patcher Tool, while also adding support for MacBook4,1 systems. To install Mojave using this patch, just follow the instructions on the guide found here.
APFS ROM Patcher: Warning: This tool could irreversibly brick your EFI chip. Please exercise caution with machines that have multiple EEPROM definitions. Relevant information can be found here and here. The APFS ROM patcher can be found here. Use the password apfs to decrypt the ZIP.
2019/01/24 - 2019/03/18 10.14.4 DP1 - DP6, PB1 - PB6 - do not install
Warning: These updates may prevent booting.
Please read this post before updating and exercise caution when doing so.
2019/01/24 10.14.4DP1, 2019/01/28 PB1, build 18E174f - donot install
2019/02/04 10.14.4 DP2, 2019/02/05 PB2, build 18E184e - do not install
2019/02/18 10.14.4 DP3, 2019/02/19 PB3, build 18E194d - do not install
2019/03/04 10.14.4 DP4, 2019/03/04 PB4, build 18E205e - do not install
2019/03/11 10.14.4 DP5, 2019/03/11 PB5, build 18E215a - do not install
2019/03/18 10.14.4 DP6, 2019/03/18 PB6, build 18E220a - do not install
Warning: These updates may prevent booting. No graphics acceleration (OpenGL on non-Metal cards) so far.
Please read this post before updating and exercise caution when doing so.
2019/03/2810.14.5DP1, build18F96h - donot install
2019/04/08 10.14.5DP2, build18F108f - donot install
Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.
MacPro3,1
MacPro4,1
iMac8,1
iMac9,1
iMac10,x
iMac11,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
iMac12,x (systems with AMD Radeon HD 5xxx and 6xxx series GPUs will be almost unusable when running Mojave. More details are located in the Current Issues section below.)
MacBookPro4,1
MacBookPro5,x
MacBookPro6,x
MacBookPro7,1
MacBookPro8,x
Pre-Metal AMD video cards (Radeon HD 6xxx series and older without acceleration, Radeon HD 4xxx series and older with acceleration.)
Pre-Metal Nvidia video cards (GeForce 5xx series and older, i.e. 8600M(GT)/8800M(GT), 9400M/9600M(GT), 320M/330M)
Pre-Metal Intel video cards (Intel HD Graphics 3000 and Intel HD Graphics Arrandale)
Minor Issues
Currently, pre-metal video cards used in Mojave will produce a weird darkish grey Menu Bar and Finder sidebar when using the light theme. In the dark theme, these anomalies are not present, while other, less obvious anomalies are present (window corners may not render properly, bottom part of dock menus may have artifacts). A workaround for graphics anomalies in light mode is to enable Reduce Transparency in System Preferences > Accessibility > Display (this might create additional side effects beside the obvious loss of transparency as some systems with pre-metal AMD graphics render the dock in dark gray).
Currently, built-in iSight cameras do not work correctly on some machines. It seems to be hit or miss, but when installing, expect your iSight camera to be non-functional.
Trackpad multi-finger gestures on both machines not supported in Mojave. While the trackpad works and is fully usable, Mojave detects it as just a standard mouse, preventing you from changing some trackpad-oriented settings.
Major Issues
AMD Radeon HD 5xxx/6xxx series GPU acceleration"]
Currently, it is not possible to get full graphics acceleration when running Mojave on a system with a Radeon HD 5xxx or 6xxx series video card. Mojave will be almost unusable without graphics acceleration. This includes the 15" and 17" MacBook Pro systems (MacBookPro8,2 and 8,3). If you want to enable GPU acceleration on these machines, you'll need to disable the AMD video card (This will work on MacBook Pro 8,2 and 8,3 systems ONLY. You CANNOT disable the AMD GPU in an iMac.) Weird colors will also be produced when running Mojave with one of these video cards installed/enabled. To disable the AMD GPU on a 2011 MacBook Pro 8,2 or 8,3, follow the guide found here.
When running Mojave, you CANNOT use a newer AMD video card EVEN IF it is a Metal-compatible card and is supported in Mojave. The newer AMD drivers used in Mojave require the SSE4.2 instruction set, which the MacPro3,1 does not support. There is no way around this at this time. Your only GPU upgrade options for MacPro3,1 systems are Nvidia cards, which work perfectly fine.
Some users have reported crashing upon opening the App Store. This is caused by App Store videos and can be worked around by disabling video autoplay and not viewing App Store videos. This is not a fix, this is a workaround. Safari may also experience crashes with certain kinds of embedded videos.
Current Issues by Hardware
Minor Issues
Graphics anomalies:
All machines
Built-in iSight camera:
All machines, hit or miss
Trackpad:
MacBook5,2 and MacBook 4,1
Major Issues
AMD GPU acceleration:
All machines with a Radeon HD 5xxx or 6xxx series GPUs (these systems will be almost unusable when running Mojave. More details are located in the Current Issues section above.)
App Store Crashing:
All machines with Radeon HD 4xxx series GPUs
AMD GPU support:
MacPro3,1
Installation:
To install on your machine, you can download and run the macOS Mojave Patcher application, which will let you download a copy of the latest installer app from Apple and create a bootable installer drive for use on unsupported Macs. It contains all the patches necessary to achieve the hardware support listed above. The installation guide can be found here and an installation guide video here.
Alternative Installation:
More advanced users may consider using @0403979's macOS Patcher Tool, which is a command line-based tool that provides the same hardware support as @dosdude1's Mojave Patcher Tool, while also adding support for MacBook4,1 systems. To install Mojave using this patch, just follow the instructions on the guide found here.
APFS ROM Patcher: Warning: This tool could irreversibly brick your EFI chip. Please exercise caution with machines that have multiple EEPROM definitions. Relevant information can be found here and here. The APFS ROM patcher can be found here. Use the password apfs to decrypt the ZIP.
2019/01/24 - 2019/03/18 10.14.4 DP1 - DP6, PB1 - PB6 - do not install
Warning: These updates may prevent booting.
Please read this post before updating and exercise caution when doing so.
2019/01/24 10.14.4DP1, 2019/01/28 PB1, build 18E174f - donot install
2019/02/04 10.14.4 DP2, 2019/02/05 PB2, build 18E184e - do not install
2019/02/18 10.14.4 DP3, 2019/02/19 PB3, build 18E194d - do not install
2019/03/04 10.14.4 DP4, 2019/03/04 PB4, build 18E205e - do not install
2019/03/11 10.14.4 DP5, 2019/03/11 PB5, build 18E215a - do not install
2019/03/18 10.14.4 DP6, 2019/03/18 PB6, build 18E220a - do not install
Warning: These updates may prevent booting. No graphics acceleration (OpenGL on non-Metal cards) so far.
Please read this post before updating and exercise caution when doing so.
2019/03/2810.14.5DP1, build18F96h - donot install
2019/04/08 10.14.5DP2, build18F108f - donot install
Moderator Note:
Please do not ask for, or provide help getting developers profile information to access unauthorised beta software on MacRumors. If you are not a developer, sign up to the Apple Beta Software Program to get the official public beta releases.
Hi,
I am new to forum. I am not sure if I am posting at correct place. I have installed mac os Mojave on unsupported mac mini. The question : Should I get updates from apple? I have 10.14.3 and I know that there is new version released in March 10.14.4 which is not showing when I am trying to update my mac. it says all updates are installed. please let me know.
Great work! I notice you removed the "Flurry_Prefix.pch" (I also had error compiling build with it) and perhaps you removed also Appkit and Foundation in "other frameworks". Do you have kept the OpenGL framework reference or removed? Because I guess it could work even without them.
I guess the main required are Cocoa and Screensaver frameworks.
Could you try directly from Xcode from top menu "edit" and "convert" the project to objective-c ARC ?
Does it still build succeeded ?
I am not sure if my experience helps but when I replaced Cocoa and Screensaver frameworks from High Sierra, it completely broke the Desktop & Screen Saver preference pane in 10.14.4. I think Screensaver framework from High Sierra is definitely not compatible. Cocoa framework seems to be ok.
tried to install mojave using tool 1.3.0 on my macbook pro 13” mid-2010 (i believe it is 7,1), but neither of my numerous attempts succeeded - i keep seeing prohibitory sign every time i try to boot into mojave after installation or upgrade finishes.
what i tried:
- do in-place upgrade of 10.13.6 to (i believe) 10.14.4 on extended journaled drive
- do fresh install of 10.14.4 erasing existing drive (but keeping it extended journaled)
- doing the same two after converting the drive to apfs (also took some time to figure out how to do this as time machine restore process was turning my newly created apfs into extended journaled i was taking backup from)
- i even tried to in install fresh high sierra and in-place upgrade it
all attempts end up with prohibitory sign.
how to diagnose this? any chance to figure out why it does not want to boot into mojave?
only hardware difference i have is 16gb memory and crucial 500gb ssd - any chance this is giving me trouble?
@the.burn rightly, when the installation is complete,
mac OS reboot, at this moment keep your finger on the "ALT" key and restart again on the installation USB key to launch "macOS Post Install":
- select the mac model on which you installed Mojave (patches for your mac will be selected automatically)
-select the volume on which you performed the installation of Mojave
-click "patch"
-when the patches are installed click "Reboot" WARNING: if you have made an upgrade of an already installed version (for example from 10.14.3 to 10.14.4) you must IMPERATIVELY select "Force Cache rebuild" before click "Reboot"
can someone please clarify if there is any difference between the APFS Patch which is installed as part of the post install patching vs the APFS ROM patch program - are they the same thing or does the ROM patcher do something different/extra?
I am running 10.14.4 with an APFS disk on a MacBook Pro 5,5 and it boots ok, but I get the scrolling messages each time the system restarts - does the ROM patcher get rid of these?
can someone please clarify if there is any difference between the APFS Patch which is installed as part of the post install patching vs the APFS ROM patch program - are they the same thing or does the ROM patcher do something different/extra?
I am running 10.14.4 with an APFS disk on a MacBook Pro 5,5 and it boots ok, but I get the scrolling messages each time the system restarts - does the ROM patcher get rid of these?
Thanks avz,
Seems like I just live with the scrolling. Not sure that I want to chance bricking the system just yet. It is a mid 2009 MacBook Pro with 8Gb and a 256Gb SSD so it runs Mojave reasonably well for a 10-year-old system, but the graphics is NVIDIA GeForce 9400M so not worth the risk of wrecking it given the repeated warnings in the video.
- create new Xcode 10.2 screensaver project
- disable ARC (since this is an old project) in build setting (Apple Clang - Language - Objective-C)
- import code (without precompile header now - even though it helps with compile speed)
- Add frameworks Cocoa, ScreenSaver, OpenGL
- Add resources (even though the preferences pane is currently broken) converting nibs and converting plist strings to UTF16
- rename the product name to Flurry+ (so it doesn't conflict with existing version of course)
You end up with tons of warnings (mainly deprecated methods etc...) but it builds and runs in Preferences as a legitimate screen saver.
I kept OpenGL , since I have yet to see any non-GL based rendering in this code. If Flurry works in non-GL-accelerated mode on .5b2 and beyond, then Apple's codebase must be different. In fact they may be Metal based now. It's worth checking the .5+ screensavers link tables to see what frameworks and libs are actually linked in. I haven't done so yet.
Yes, Flurry works in non-GL-accelerated mode on .5b2 and beyond, just software render mode or CoreImage (I guess).
I've already tried as invited by Xcode to convert the .nib to UTF16 and to update the headermaps to the current coding, but same result one error only.
I do have in Xcode preferences the "Continue building after errors" checked of course.
I still get this one only error resulting in Build failed.
Code:
ld: warning: ignoring file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks//ScreenSaver.framework/ScreenSaver, missing required architecture x86_64 in file /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.5.sdk/System/Library/Frameworks//ScreenSaver.framework/ScreenSaver (2 slices)
Undefined symbols for architecture x86_64:
"_OBJC_CLASS_$_ScreenSaverDefaults", referenced from:
objc-class-ref in FlurryView.o
objc-class-ref in PresetManager.o
"_OBJC_CLASS_$_ScreenSaverView", referenced from:
_OBJC_CLASS_$_FlurryView in FlurryView.o
"_OBJC_METACLASS_$_ScreenSaverView", referenced from:
_OBJC_METACLASS_$_FlurryView in FlurryView.o
"_objc_msgSendSuper2", referenced from:
-[FlurryView initWithFrame:isPreview:] in FlurryView.o
-[FlurryView dealloc] in FlurryView.o
-[FlurryView setFrameSize:] in FlurryView.o
-[FlurryView startAnimation] in FlurryView.o
-[FlurryView stopAnimation] in FlurryView.o
-[MonitorCell dealloc] in FlurryView.o
-[MonitorCell initWithIndex:] in FlurryView.o
...
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Tried to add from "Build Settings" the "Other Linker Flags" -v but still get almost the same build error.
I've thought that maybe Appkit and Foundation could be required to make the preference pane to work.
I got also the same error if I keep the pre-header Flurry_Prefix.
I have to say that I am using Xcode 10.1 from HighSierra 10.13.6 , so deployment target is 10.13 but noticed the source code is good to use until 10.8 or even 10.7 .
edit:
I was using the wrong SDKROOT ? Apparently not. Can't figure it out.
Thanks avz,
Seems like I just live with the scrolling. Not sure that I want to chance bricking the system just yet. It is a mid 2009 MacBook Pro with 8Gb and a 256Gb SSD so it runs Mojave reasonably well for a 10-year-old system, but the graphics is NVIDIA GeForce 9400M so not worth the risk of wrecking it given the repeated warnings in the video.
This is exactly what it comes down to. The risk may outweigh the benefits. If you don't plan to have many bootable APFS partitions on your machine, your benefit is purely aesthetics. At the same time not tampering with your original BOOT ROM might also help maintain the resale value of the machine.
I guess that tool is for hack***osh and expressly for Intel Graphics, consider that the other forum has "fixed" Nvidia Tesla following the @ASentientBot guide.
Anyway even if IntelHD Graphics in OpenGL mode worked without any binary patch in Mojave, from .5 beta2 they have the exact same behavior of binary patched Nvidia Tesla.
I've tested IntelHD Arrandale and IntelHD3000, same noOpenGLaccel behavior of Nvidia 320M .
)
