Apple's Unix Porting Guide
hysterion writes "Just came across the nice Unix Porting Guide (pdf) posted by Apple earlier this month. Topics include NetInfo, using Project Builder with gnumake, autoconf, XFree86, Tcl/Tk, Qt ... it is a bit short on scripting languages, and they speak as if KDE were already ported, but other than that I found it an informative read." They also didn't mention fink, and they put "Unix" in all caps. However, they were honest about the shell scripting limitations of AppleScript, although they didn't mention that AppleScript -- especially via osascript -- is pretty buggy in Mac OS X right now (this is my annoyance of the week, so allow me to indulge myself).
It is...
The operating system is UNIX, not Unix, though admittedly at this point it's more of a paradigm than an OS.
Is your browser retarded?
I'm not a developer, but this appears to have answered a great many questions for those developers teetering on the edge of Mac OS X development. My primary questions were answered pretty well from this document.
The nice thing about this document is how it tacitly implies that writing an OS X app can be done in such a way that it can be deployed just about anywhere with practically any imaging model and with many new or common IDEs. OS X, from a programmer's perspective, must seem extremely flexible.
Vos teneo officium eram periculosus ut vos recipero is.
Here's a link on porting Java apps to Mac OS X, eg, menu bar issues, tweaks that don't break cross-platform compatibility but help the Mac experience. Pretty good.
I saw no references to eggs in that post.
Good luck compiling all that "linux code" on XP...jackass...
Good luck compiling all that "linux code" on XP...jackass...
It's too bad some people don't have a sense of humor, can't laugh at themselves - I found the parent post to be sarcastically funny - it's obviously not a true story - and it's actually a pretty good troll....
I've seen better attempts at trolling made by kindergarteners calling one another "poopy pants" in an attempt to get a rise out of someone.
You forgot to mention the ADB caps lock key issue!
This is from Fink's FAQ:
Q2.3: What is your relation with Apple?
A: Apple is aware of Fink and has given us some support as part of their Open Source relations efforts. In the summer and fall of 2001, they provided us with pre-release seeds of new Mac OS X versions in the hope that Fink packages can be adapted in time for the release. Quote: "Hopefully it underscores the commitment that many suspect we're not willing to provide. We'll get better at the open source game over time." Thanks Apple!
I had no idea that this had occured. It's exciting!
I'm given to wonder, however, why someone with a full OS X installation would wish to use KDE. Perhaps there are a dozen reasons I can't think off off-hand, but the real prize would be to run KDE on top of Darwin! Is this possible yet?
Darwin core + good GUI = another no-cost operating system on the loose. It would no doubt have far lower system requirements than OS X, too. The idea has me drooling already.
You like your Macintosh better than me, don't you Dave? Dave? Can you hear me Dave?
is what they need. If you run a task that takes ~5-10 minutes to complete (update prebindings) your applescript will stall for that long of time. Trying to "backround" it by putting a & at the end doesnt help ether, still waits for the prossess to finnish. I'd be really nice if i could have a little applescript studio application work interactvly with huge perl programs i've already written.
:) bfc@mac.com
BTW: if anyone knows how to do this feel free to tell me
Good luck compiling all that "linux code" on XP...jackass...
Actually open source code usually compiles and runs well under WinNT. Very little open source code is linux specific.
OSAscript is pretty darned cool, but it's been my annoyance of the week as well. Been playing with it the past couple of days to write a nice-looking iTunes remote for our office jukebox -- controlled via a browser, not the shell (doing it from the shell is cake, even on remote machines.)
As Pudge mentioned, it's VERY buggy though. A few things I've noticed: