JDK cannot be opened after MacOS upgraded to 10.15.X (Catalina) - macos-catalina

After MacOS is upgraded to 10.15.X (Catalina), JDK cannot be opened. The message shows "JDK cannot be opened because the developer cannot be verified".

According to java.com:
Changes introduced with macOS 10.15 (Catalina) cause certain Java
applications to behave incorrectly. Therefore, we cannot certify any
JDK version on macOS 10.15 yet. However, as of now, you can install
and run non-notarized software on macOS 10.15 systems by modifying
your security preferences.
You can find detailed information about it here.

Related

Can not set android clang compilers for Qt Android on Ubuntu

I installed Qt Android 5.15.2 on Ubuntu but there is problem with the compilers. This is what I have set:
And here is what QtCreator detects as compilers:
The first error is displayed here in the Qt version tab:
and also in the Kit tab I see this errors no matter which compilers I set from the available:
Why I got this errors? Can please someone that has android kit on Ubuntu already set, tell me which compilers is using and which paths are for the compilers?
I will add more information for the current compilers or kits if needed.
The problem is that you are trying to use a x86 compiler for Android. You need to install the specific compiler from the Android SDK/NDK. So the good news is that you might be only missing one step (step 2 below)
I tried to install from the Ubuntu stock packages. That was impossible to get to work.
I was able to set it up in the following way:
Download the Qt online installer. Login and DO NOT choose individual packages, install Qt for desktop and Qt for mobile (check the last 3 options). This will install Qt 6 + QtCreator
Run QtCreator after everything finishes (+1.2Gb download). Go to Tools>Options>Devices>Android. Check that Java SDK is ok. On the Android section, choose "Set up Android". Accept all licenses.
This is what you should see in the end:

Weka will not open on MacOS

I have installed the latest version of Weka(3.9.3). I have also ensured that both Java and MacOS are up to date on my machine.
When I double-click the Weka icon to open it, it bounces for a few seconds and never opens.
I have downloaded Weka 3.8.3 to see if that makes any difference, but the same thing happened.
Any ideas on why this is happening?
I was facing a similar issue but it worked for me when I start weka on the command line.
Change directory into the weka-3-8-0 directory
cd /Applications/weka-3-8-0
invoke the jvm with the weka.jar file located in the above directory
java -jar weka.jar
We have identified the issue with the WEKA 3.8.3 and WEKA 3.9.3 applications for the Mac that, for many users, caused them to fail to start up via double-clicking.
On December 13, we replaced weka-3-8-3-oracle-jvm.dmg and weka-3-9-3-oracle-jvm.dmg on SourceForge with a new .dmg compatible with older versions of OS X, based on the HFS+ file system. Unfortunately, this new “release" included a pre-17 December 2018 version of the Amazon Corretto JVM 1.8.0_192 instead of the Oracle Java VM we had used before. Unfortunately, that particular version of Amazon’s Corretto had a bug on Macs:
"The libfontmanager in Corretto is linked to the libfreetype in X11 and breaks when X11 is not installed."
See https://docs.aws.amazon.com/corretto/latest/corretto-8-ug/change-log.html.
We never noticed this problem and could not reproduce it because if, like us, you had XQuartz installed, or the libfreetype.dylib library was installed on your Mac via Homebrew, the WEKA application still worked in spite of this bug.
We have reproduced the problematic behaviour by removing XQuartz and Homebrew on one of our Macs. And, indeed, the WEKA macOS application no longer started when the bird was double-clicked.
We have just made new “releases” of the WEKA 3.8.3 .dmg and the WEKA 3.9.3 for the Mac that use the latest version of Corretto 8 (8.212.04.2). You can find these .dmg files at
https://sourceforge.net/projects/weka/files/weka-3-8/3.8.3/
and
https://sourceforge.net/projects/weka/files/weka-3-9/3.9.3/
respectively.
They are called
weka-3-8-3-corretto-jvm.dmg
and
weka-3-9-3-corretto-jvm.dmg
respectively.
We have also replaced the links for the Mac applications on the main WEKA downloads page at
https://www.cs.waikato.ac.nz/ml/weka/downloading.html

Current Cygwin version is not supported by Clion, how to install an earlier version of it?

I am trying to get my Clion 1.1.1 to work with Cygwin. I've installed Cygwin using its setup-x86_64.exe installer. but when I set Cygwin path in Clion's toolchains dialog, it says:
Environment: Cygwin; current version is 2.2.1; supported version range is 1.7.32-2.0.x
On the Cygwin website there is a snapshots page, in which packages are sorted by date (not version) and in faq page it says:
If you are looking for the version number for the whole Cygwin release, there is none. Each package in the Cygwin release has its own version.
So, if there is no version number for whole Cygwin release, what is Clion complaining about?
and if there is, how can I install an earlier version?
afaik, you'll either need an older installer (and some luck on the repos) or someone's older package directory and installer. All recent installers only go back one release which won't be enough to get you back in line with Clion's requirement.
Might also be worth reaching out to Clion and asking them when support for the recent versions is coming out.

"Parse issue: Unknown type name" error after upgrading XCode

After I upgraded my Mac OS X to Mountain Lion (all the way from Snow Leopard) and XCode 5 (all the way from XCode 3.2) I can no longer build a C++ project that I used to build in XCode successfully. I get loads of errors now all saying "Parse issue: Unknown type name *" for different objects. I tried an older version of XCode (4.6) and set the SDK to Mac OS X 10.7. This problem was solved but not using the latest version of XCode caused other problems.
To be specific, the errors (at least the first ones) seem to be related to Carbon graphic library. I don't know if that matters. I know that Carbon is somehow outdated but an official release of the application I'm extending runs on Mac OS 10.8 so I wonder why I can't build the code on 10.8.
What can be the cause of this error? The code is big and is not written by me so changing it is not an option. I really need to build it on XCode 5 or else I should downgrade my OS!
Several things that have been long deprecated in Carbon were finally removed in the Mac OS X 10.7 SDK.
You will need the Mac OS X 10.6 SDK to build your project. Apple stopped automatically including older SDKs with newer versions of Xcode but you can download older Xcode versions (from Apple's Developer site) and one of them...maybe Xcode 4.3 or so...will have the 10.6 SDK.
In order to use an older SDK with a newer Xcode, you must install it manually. The correct location is:
/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/
Also note, any upgrade to Xcode (such as an update downloaded from the App Store) will obliterate your manually-installed SDKs. I recommend archiving the ones you need somewhere else so you can replace them as needed.

How to fix problem with version mismatch of iPhone 4.3.4 and IOS SDK

I upgraded my iPhone to 4.3.4 (8K2) and I can no longer build my app.
In the organizer, I get the following error:
The version of iOS on “Jeff Bonta’s iPhone” does not match any of the versions of iOS supported for development with this installation of the iOS SDK. Please restore the device to a version of the OS listed below, or update to the latest version of the iOS SDK; which is available here.
OS Installed on Jeff Bonta’s iPhone
4.3.4 (8K2)
Xcode Supported iOS Versions
4.3.4 (8K2)
4.3.3 (8J2)
4.3.2 (8H7)
4.3.1 (8G4)
So, it acknowledges that I have 4.3.4 installed on my iPhone and it says that Xcode supports 4.3.4, but it also says that the version on the iPhone does not match any of the versions supported for development with this SDK. Very confusing.
Before I rebooted my iPhone, I got errors in the debugger console:
iphone unable to load symbol file:
Other users have had this problem with version 4.2.1 and resolved it by:
Deleting the folder /Developer/Platforms/iPhoneOS.platform/DeviceSupport/4.2.1/ and restarting Xcode.
I could not get this to work because I could not delete the folder .../4.3.4 (8K2). I figured out how to delete this folder, but not until after I rebooted my iPhone.
Any suggestions? I am completely stuck.
I had a similar issue, here was my work process.
Close XCode
Disconnect iPhone
Delete 4.2 - to the latest version folders (as
shown in the other post - If you cant do it through the GUI, go in through terminal and sudo delete it.)
Now I went to install Xcode again, but I use Lion now and it said "update xcode" when I went to install.
Install the new updates and open Xcode.
Plug in the iPhone and open Organiser (if it doesnt do it automatically)
Wait a minute
before it recognises the iPhone, it should then ask you to port the
files across.
Click on the project file in Xcode, and then set the
version to 4.3.4 (or 4.3.5 if you updated) manually, as its grayed out and doesn't recognise the device until you do.
Clean the project and then build.
Let me know how you get on :)
I have both Xcode 3.2 and Xcode 4 installed. 3.2 gave me the same error on an iOS5 iPad. I deleted the folder with 'sudo rm -rf /Developer/blah/balh/' and then opened Xcode 4 with the iPad connected, Xcode 4 did some magic and a message 'Clean Manager succeed' appeared on the status bar. Closed 4, opened 3.2 and voila! There was my device ready again.
Hope this helps.