This is the library that complains about problems opening the temporary files, throwing code error: -10.

The application uses Intel MKL Pardiso OCC, which creates the temporary files inside of Documents/AppName/temp/.

The application has been deployed using macdeployqt of Qt Creator.I give some further details in case somebody thinks the problem is not how I am opening the app, but the app itself. I am mainly interested in knowing the difference between double clicking in finder, the command open and directly executing the executable using.If not, what problem could cause a different behaviour between those options? Do I need to add something to my ist file? Youll need to reference the java app in the JDK home and use the -jar file.jar option. You may need to run it from the command line. Along with dumping Java, Apple disconnected their helper apps that would launch a jar on double-click. Is there any difference regarding file permissions between using the open command, double clicking in finder and using the. Is the java executable in your Java home folder set to open the jar files. application.app/Contents/MacOS/executable it works perfectly. However, when I open it using the command. Change the directory containing the downloaded file (used /tmp as the example): cd /tmp b. Use the following Terminal command line: a. When I execute this application double clicking in finder, or from console using the command open -a application.app, the application complains because it cannot open the temporary files. Extract the package you downloaded, double click the executable file, and then follow the step-by-step instructions in the Installation Wizard to install Foxit Reader on your computer. The folder containing the temporary files is: ~/Documents/AppName/temp/. I have created a bundle application that uses temp files inside of a folder, a third party library takes care of creating temp files, using them and remove them.

Mac executable file on double click