What is happening to NCurses and OS X 10.6? - macos

Apparently libncurses...dylib is broken OS X 10.6.3 relative to Mutt, and perhaps other applications, that use ncurses, although it works in 10.6 (as I can attest) and reportedly it works in 10.6.2.
Does anyone know if this is a bug or a feature in the view of Apple? If a feature, is there a workaround for people who want to upgrade 10.6..., but also want to use, for example, Mutt?
Thanks

As your post is pretty sparse in details, I guess you're talking about the bug in ncurses that breaks the way arrows works? (And may quit programs when you try to use the arrows, as a side effect)
I described it here: http://www.uponmyshoulder.com/blog/2010/os-x-10-6-3-broke-ncurses/
If we're talking about the same thing, I honestly think this is a bug. It doesn't match the documentation for ncurses, and actually makes no sense.
I submitted a bug report more than two weeks ago, without any answer from Apple so far.
A workaround (as suggested by Jonathan Groll) is to copy /usr/lib/libncurses.5.4.dylib and /usr/lib/libncurses.5.dylib from a 10.6.2 system. I don't really know what to think about such a libraries switch, as it might trigger other problems, but it does indeed fix this bug.

I've been told by Apple that my bug (ID #7812788) is a known issue currently being investigated by engineering, and has been filled as a duplicate of bug #7812932.
I'll keep you updated. :)

Related

Macruby on OS X Mavericks

I'm running OS X Mavericks and installed MacRuby last week in order to make a simple app in it. Anything I try to run in Xcode (even Hello World app or a downloaded example), I always get "Build Failed" and really similar errors to this:
I found in some forums that th Garbage Collection is really deprecated etc. but I could't find any solution. Therefore I would be very glad if someone has a solution for this.
And no, I can't just work in Objective-C since it's far too complicated for me and apps I'd make :)
Thank you!
MacRuby isn't currently compatible with 10.9, not just because of the garbage collector, but due to changes in the Objective-C runtime, LLVM, and Xcode. There is a thread (titled "Mavericks and Macruby") going on right now on the macruby-devel mailing list about these issues. Joshua Ballanco's message especially sheds a lot of light on what it would take to keep MacRuby going.
You can still use the garbage collector by setting GCC_ENABLE_OBJC_GC = supported in Xcode; but as I said, it won't make MacRuby actually usable (yet).
I suggest people interested in cocoa in ruby help out refining the
cocoa gem instead of hoping for any progress on macruby which is
abandoned by its creators for commercial interests. The cocoa gem
is quite useful already, but need to mature a bit in some cases.
https://github.com/patrickhno/cocoa
DISCLAIMER: Yes I am the author.

NSSplitView issues with 10.7 and 10.8

i'm experiencing some issues with AutoLayout. Building for 10.8 with Xcode 4.6.2 none of the constraints i setup work for OSX 10.7. Are there any known issues around this?
Thanks!
I got this problem too, so I wrote a custom split view based on constraints. See my repo for code. https://github.com/silvansky/TwinPanelView
I personally gave up trying to use auto layout with split views. The manual layout works the best, in my experience, and is actually not much more complicated at all.
In particular, take a look at this answer: https://stackoverflow.com/a/843870/2308693
It's brilliant, and it gives you full control of everything (so I agree fully with the first comment on that answer).

How to write to Mac OSX preference files with mono C#

Ii am looking for a guide and information to specifically reading from and writing to Mac OS 10.6, 10.7, and 10.8 preference files using preferably C# Mono. However I am by far and large not picky and can pick up any other language to do the same thing.
Yes this is probably a duplicate question, I just haven't had the time to research it myself. I am not "just wanting the answer handed to me" because honestly that is not going to teach me anything in the long run. Thank you for your help and suggestions ^_^
Edit: BTW, working 8-10 hour days makes it difficult to do much of anything else. I have done some searching on and off and while I have found sparse materials on coding preferences for Mac in the Mac docs and a couple tuts here and there, there still is not much in the way of Mono driven preferences specifically. I will be checking out the answer with MonoMac, thanks for the reply.
Is there an API in the Mac OS SDK to do this?
If yes, chances are that this API is wrapped by MonoMac, and then you can just use that.

further Linking to libcrypto for Leopard

Using XCode 3.2.5, I have recently changed my Base SDK from 10.5 to 10.6 (Deployment SDK is still 10.5) and have run into the same thing as mentioned in this thread:
Linking to libcrypto for Leopard?
So the correct libcrypto image is not found when loading the application under Leopard. (Used by Aquatic Prime).
My question is - is this really still the right solution 17 months later? It seems like there has been several XCode releases and OS updates since then, and previous posters have said they have filed bug reports with Apple, I'm just finding it hard to believe that a bug this big still exists. Also, I haven't found any mention of this problem in the Apple Developer Forums which is hard to believe too. It makes me think that I've set something up wrong or other people would still be running into this problem as well.
I have no problem implementing the solution outlined in the previous thread (haven't tried it yet though), I just want to make sure that I'm solving the right problem.

Is PackageMaker considered the standard for Mac OS X software installation? Or is there something else out there?

I've put together my very first package with PackageMaker (for a system service), but I am not happy about several faults:
Frequent crashes while applying target permissions to my source files
Package source files are not automatically or easily refreshed
File filter does not work
Is there something else out there more capable of this task? Free is not a requirement.
Yes it is, and yes it's buggy. Apple uses the command line version pretty much exclusively so the GUI tends to have the feeling that it's been slapped together by a summer intern and never tested.
PackageMaker is the standard, for things that need an installer (many regular applications just use a DMG, often with a background image telling the user to copy the bundle to /Applications - eg Firefox does this)
MindVision VISE is a commercial solution you can look at, used by some people, but personally I think the look & feel of the resulting installers is subtly wrong (and slightly retro) - that's a subjective viewpoint of course.
Package Maker works pretty well for many people - though documentation is rather scant; are you sure the problems you're experiencing aren't fixable?
There (now) is a great free alternative to PackageMaker with the simple name "Packages":
http://s.sudre.free.fr/Software/Packages/about.html
It's really easy to use, very stable and mature and even open source (in case you need to hack anything). Plus: it has a well written documentation!
I had the same problem until I added #!/bin/sh at the top of the script. Apparently PackageMaker needs it; I wish the log was a bit more clear about it.
IHIH, Oren
Since Mac OS X 10.6 Snow Leopard it is recommended to use pkgbuild and productbuild instead of PackageMaker.

Resources