Friday, June 27. 2008Great Post on Cocoa Development on Theocacao
I just ran across this great post titled Thinking Like a Cocoa Programmer over at theocacao.com. Give it a read!
Monday, June 2. 2008It's been a while...
So it's been a while since I've posted anything on here. I haven't disappeared. Over the past few weeks I've been going through Aaron Hillegass' 3rd edition of Cocoa Programming for Mac OS X. If you haven't picked up this book yet and have any interest in getting started in Mac development, go buy this book right now.
In my first attempts at learning Cocoa, I was trying to use the 2nd edition of the book while using Xcode 3 on Leopard. Needless to say, this didn't work out so well. That's when I started working on the GLSCollections framework just so I could get some more experience on the inner workings of Objective-C while waiting for the 3rd edition of Aaron's book to come out. (btw: this project isn't gone now, but I have put it on the side for a little bit. I'll probably restart it from scratch, though). Anyhow, I've gotten through the 3rd edition and am now working on a full fledged Cocoa application. My wife wanted a little cookbook application for her new Macbook, so I'm taking the opportunity to write one for her. It uses CoreData, will incorporate a "Cover Flow" type view for browsing through pictures of recipes, and I'm also looking into incorporating document sharing via Google Docs (but that feature hasn't even been started yet). The basics are about 50% done right now. I've got the main interface done. Now I'm just working out all of the little details. Let me know if you're interested in seeing a nowhere-near-complete preview version!
Sunday, April 27. 2008Debugging Frameworks Unit Tests
Chris Hanson has recently updated his posts on debugging OCUnit test cases, because it's not as straight forward as you'd think. Especially when trying to debug unit tests in a framework. I'm not getting any unit tests failing on the GLSCollections framework right now, but I am getting this:
/Developer/Tools/RunUnitTests:314: error: Test rig '/Developer/Tools/otest' exited abnormally with code 139 (it may have crashed). So Chris' posts may really help out in this case! Also searching around I've found this. I now know that it's a memory error causing this little error in otest. Now I just have to figure out what exactly I'm doing wrong. --update - 5/17/2008 -- It seems that I'm getting quite a few hits from people looking for help debugging OCUnit Unit Tests. Here's what to do to enable the debugging of unit tests: First add a custom executable to the project. Go to the Projects menu and select Add Custom Executable. Set the file name to otest and set /Developer/Tools/otest as the path to the executable. Next, switch to the Arguments tab of the info pane. and add two arguments: -SenTest Self and MyBundleOfTests.octest where MyBundleOfTests is the name of your test bundle. Next add two environment variables: DYLD_FRAMEWORK_PATH and DYLD_LIBRARY_PATH and set them to $(BUILT_PRODUCTS_DIR). We're done with the info pane now so we can close it. Go back to the Project menu and set otest as the active executable. Finally set some breakpoints and Debug your executable. Just remember not to do a build and run otherwise it will fail from the failed unit tests. Thanks again to Chris Hanson for figuring all of this out.
|
QuicksearchCategoriesSyndicate This BlogPowered by |
