osx-mountain-lion

What to do about Carbon functions that are deprecated in MacOS/X 10.8.x?

回眸只為那壹抹淺笑 提交于 2019-12-04 07:31:07
I have a C++ codebase that has been around for a while (10+ years) and it compiles and runs fine, but I notice that when I compile it under OS/X 10.8.x (Mountain Lion), the compiler emits deprecation warnings about some of the Carbon functions it calls: ../system/SetupSystem.cpp:575:44: warning: 'UpTime' is deprecated: first deprecated in OS X 10.8 [-Wdeprecated-declarations] ../system/SetupSystem.cpp:575:22: warning: 'AbsoluteToNanoseconds' is deprecated: first deprecated in OS X 10.8 [-Wdeprecated-declarations] ../system/SystemInfo.cpp:249:25: warning: 'MPProcessors' is deprecated: first

How to sign Java applet with Apple Developer ID

戏子无情 提交于 2019-12-04 05:14:08
问题 I have java applet signed with thwate certificate and need to sign it with Apple Developer ID. As is well-known, Mac OS X 10.8 requires Java applications to be signed with Apple Developer ID. It causes some problems with running Java applets, Gatekeeper says that "The digital signature could not be verified". There are the same issues OS X 10.8 Gatekeeper and Java applets and Sign java applet so that it works on OS X 10.8 Mountain Lion and Windows I also found this in Oracle's Mac FAQ: http:/

Increase rlimit Mac OSX 10.8

大兔子大兔子 提交于 2019-12-04 04:46:21
I'm learning MongoDB and when I start the mongo shell a wild warning message appeared. It says: How do i change the "soft rlimits". I'm using Mac OSX 10.8.2 Tnx in advance What you are searching for is launchctl limit maxfiles . To change it you need to run command launchctl limit maxfiles 1024 2048 for example. To permanently change those values you need to create /etc/launchctl.conf and set there values you need (see here for details) or add command mentioned above to your ~/.bash_profile. Or you can create script which will set limit and then launch mongo If you run mongo as a service, you

Java ScriptEngineManager no longer works with Mountain Lion's AppleScript

為{幸葍}努か 提交于 2019-12-04 02:56:36
Ever since I upgraded to Mountain Lion, I can't run my AppleScript code through the Java ScriptEngineManager. The sample code found on Apple's page ( link ) returns null for the engine object. public static void main(String[] args) throws Throwable { String script = "say \"Hello from Java\""; ScriptEngineManager mgr = new ScriptEngineManager(); ScriptEngine engine = mgr.getEngineByName("AppleScript"); engine.eval(script); } Anybody know of any workarounds? Alban I got it working by adding a file named "javax.script.ScriptEngineFactory" in the folder "META-INF/services" of my jar as ytw

Prevent iCloud window from opening on OSX 10.8 app launch

烈酒焚心 提交于 2019-12-04 02:34:38
I have written an OSX app that uses iCloud document storage. Whenever I open it in Mountain Lion (not on Lion), an iCloud window opens that looks like the following: Is there a way to prevent this from happening on launch? Updates: 1) applicationShouldOpenUntitledFile: is not getting called (yes, I'm sure I'm listening in my delegate. 2) If I force quit the app, the next time it opens, I don't get the dialog. But, if I go through the normal Quit process, it does appear. Update 2 (also added as an answer, to help people that may stumble across this question in the future): The

Mac Code Signing: Bypass the Keychain Access private key prompt from Terminal

蓝咒 提交于 2019-12-04 01:46:37
I'm working on an app in Mac OS X Mountain Lion that needs to access the private key of some of my certificates within the Keychain Access. Since this app is going to run on a server, I need to avoid the pop up dialog that requires the user to allow the app to access the private key: I know that by clicking "Always Allow" the dialog won't popup anymore for that private key, the problem is that I will be working with different keys. Thanks in advance, Mikywan. The only way I found to solve this is by setting up the Private Key in the Keychain Access to "Allow all applications to access this

GCC-4.2 error on Mac OS-X Mountain Lion, unable to install some packages with pip / virtualenv

非 Y 不嫁゛ 提交于 2019-12-04 01:40:12
I'm seeing a very annoying bug that I don't really know how to deal with. It seems to be pretty common, and I've tried nearly every solution that I could find to no avail. I'm trying to install libraries using pip. This problem was encountered with gevent, with psycopg2, and with greenlet. The issue seems to be that my computer can't find a particular C compiler that should come up with XCode 4: gcc-4.2. Here's an example (though attempts were made in a virtualenv as well). Last login: Sun Jul 29 23:35:54 on ttys000 *******s-MacBook-Pro:~ ******$ pip install gevent Downloading/unpacking gevent

The digital signature is not trusted. Java will not allow any access to this application

南楼画角 提交于 2019-12-03 22:43:54
I have a Java Web Start application, which I've tested on Windows 7, Linux and Mac OS X 10.7 (works fine on all). On Mac OS X 10.8 Mountain Lion the following error occurs, with no option to choose "Allow". The error looks like this: Does anyone know of a workaround for this? Nick Just found a solution: Go into System prefs -> security and privacy, and check the box that allows applications to be downloaded from anywhere (you might have to click the lock to make changes to this) This is because of a new feature in Mountain Lion known as ' Gatekeeper '. Following is a brief description: Choose

Cross Compiling libogg for iOS

吃可爱长大的小学妹 提交于 2019-12-03 21:37:10
I've been trying to cross compile libogg for armv6, armv6 and i386 using the iOS 5.1 SDK in Mountain Lion. Libogg uses autoconf, and I've been having pretty similar issues with a few other libraries as well. I picked up a neat little cross-compiling script from here . I had to update it a bit to find the location of the SDK's. GLOBAL_OUTDIR="`pwd`/dependencies" mkdir -p $GLOBAL_OUTDIR/include $GLOBAL_OUTDIR/lib OUTDIR="./outdir" OGG_LIB="`pwd`/libogg-1.3.0" IOS_BASE_SDK="5.1" IOS_DEPLOY_TGT="3.2" setenv_all() { # Add internal libs export CFLAGS="$CFLAGS -I$GLOBAL_OUTDIR/include -L$GLOBAL

Where to put SQLite database to keep it from being over-ridden during update on OS X?

心不动则不痛 提交于 2019-12-03 20:59:58
I'm developing my first OS X application which will be distributed through Mac App Store. The app makes use of an sqlite database which I am currently keeping on the same location as the rest of app file dependencies. I'm using Qt Framework to develop the application. Keeping within the boundaries of App Store rules; Where can I locate the database file for it not to be overridden during app updates? How should I structure the .app folder and all the dependencies? Thank you. Your question implies that you are writing to the sqlite database, which is a bad idea given the application will be