Rat-Hole Mac OS
What Does a Rat Hole Look Like. Typical Rat Burrow. The first distinct sign of a rat hole is the size of the entrance. The entrance will be roughly 2-4 inches in diameter and smooth and compacted from the rodents going in and out of the burrow. You’ll also notice fresh dirt just out of the entrance in a fan-shape created when the rodents. Next, the depth of the hole: the rat holes in the lawn are roughly 3 feet in length and 18 inches in depth. Some rat holes are deeper as rodents might try to burrow through the foundation of the building. Since I usually work on a Mac, I can't use WireShark. Enough detail and the web can direct them as far down the rat hole as they need to go. Security due to its being open source as well. The first distinct sign of a rat hole is the size of the entrance. The entrance will be roughly 2-4 inches in diameter and smooth and compacted from the rodents going in and out of the burrow. You’ll also notice fresh dirt just out of the entrance in a fan-shape created when the rodents excavate dirt from the hole. For a Limited Time - Discount of 50%. PDF Security Pro Edition is fantastic utility to add, remove or modify password security of PDF documents in batch. In addition, It allows to batch modify metadata information of PDF documents. PDF Security Pro is an easy to use utility to encrypt.
Having used a hackintosh (Surface Pro) as a secondary machine to my Mac, I don't recommend it for everyone.* You won't be able to update to the latest patches without possibly breaking the build. There's a possibly you need to re-hack your device every year. Xcode is tied directly to Mac OS X builds. For example, you can't download 8.1 unless your own Sierra right now.
* WiFi / Bluetooth didn't work for my particular hackintosh, but it'll be better for others.
* Graphics were a bit buggy (again not a problem depending on the device).
* Login would fritz out on occasion so I'd have to boot into safe mode to fix it. Could be my particular device, but random problems are common with hackintoshs.
* When it worked it was amazing, touchscreen worked as well.
* iMessage / FaceTime will not work unless you hack it and provide it your Mac's serial number. Do this at your own risk. This could essentially break iMessage on your original mac. I think I ended up emailing them or something to get it looked into / fixed.
* App Store has some issues as well as lot of things are tied into the serial number of the Mac.
* If you enjoy fiddling and hacking on things, I'd recommend this. It was a good learning experience for me and I don't regret it, but I wouldn't want to do it again. I ended up having to modify some kernel files to get some things working. Basically a lot of tinkering from one patch to another.
Having done it once, I wouldn't go the hackintosh route again. While I enjoyed the process, the amount of time I spent to get it work wasn't worth it for me. If price was an issue, it's definitely a good route.
Tonight I have 2 hours free. It’s time to pull together the various snippets of info and manual tasks I’ve been following to build my app that runs on Mac OS X and Windows desktops and engineer a script I can just run each time.
The tools: first javafxpackager. https://docs.oracle.com/javafx/2/deployment/packager.htm
I’ve used this partially to build the windows executable but am using manually built ant script for Mac OS and manually signing everything in the bundle messy. Let’s sort that first.
Mac OS X
My compile / edit / test cycle is in Eclipse, and when I’m happy I export a runnable jar with the required Apache libs embedded, so my starting point for packaging is the jar. Might be nice one day to have a task in Eclipse that just does the packaging, anyway no distractions tonight.
I’m using jdk 7 still on the Mac and javafxpackager is nowhere to be found. First hurdle. The hunt begins, firstly Oracle tell me it’s included in the version of the jdk I’m running, 7.0.6. Aha it’s been renamed javapackager – nope that’s not there either. Sod it, let’s update to the latest jdk 7 – not ready to go to 8 yet. Hmm, still no packager. Pokes about a bit and sees in /Library/Java/JavaVirtualMachines there’s a few versions of the sdk now including 7u71, the most recent. Checks it out and the 7u6 I think I’m running and lo and behold there’s javafxpackager in both. OK so where is Mac OS X picking the SDK up from, or more importantly where _should_ it be picking it up from.
And voila more learnings! Short answer is ensure JAVA_HOME is set preferably using /usr/libexec/java_home to choose. Now javac reports it’s using the jdk I just installed. OK but still no javafxpackager in the default path. Henceforth it shall be known as $JAVA_HOME/bin/javafxpackager ….
Rat-hole Mac Os Catalina
Back to the job in hand, how do I go from a runnable jar to a signed .app with an embedded jre and a suitably signed installer pkg? javafxpackager -deploy appears to be the way, or it’s equivalent using ant, which might be more extensible and usable going forward. $JAVA_HOME/lib/ant-javafx.jar is your friend at this point. 30 minutes reading and researching later I think the 2 hours tonight isn’t going to be enough …..
Prototyping using the command line, the following generated a usable .app
javafxpackager -deploy -srcfiles ./DrumScoreEditor-Community-1.00.jar -outdir ./outdir -outfile DrumScoreEditor -native image -appclass org.whiteware.DrumScoreEditor -name Drum Score Editor
Rat-hole Mac Os X
Seemed to strip out the Quicktime libraries that Apple reject your app store submission for, but can’t find a way to get it to sign everything for me yet, nor produce a .pkg (signed or otherwise). Using -native installer produced a well put together dmg with a typical ‘drag to /Applications’ image – nice but doesn’t help for the app store.
Rat-hole Mac Os Catalina
More when I have another 2 hours …..