Xcode on Arcanelab Blog

Conforming to Objective C protocols in Swift When conforming to an Objective C…

Fri, 05 May 2017 10:28:00 +0200

Conforming to Objective C protocols in Swift

When conforming to an Objective C protocol in Swift, make sure that the Swift class also inherits from NSObject.

How To Use Git Source Control with Xcode 8

Mon, 17 Apr 2017 17:34:00 +0200

jverkoey/iOS-Framework

Sat, 11 Feb 2017 18:57:00 +0100

A Selection of Swift iOS Libraries https://github.com/Alamofire/Alamofire…

Mon, 24 Oct 2016 13:56:00 +0200

A Selection of Swift iOS Libraries

https://github.com/Alamofire/Alamofire
https://github.com/Alamofire/AlamofireImage
https://github.com/naoty/Timepiece
https://github.com/radex/SwiftyUserDefaults
https://github.com/pkluz/PKHUD
https://github.com/krzyzanowskim/CryptoSwift
https://github.com/robb/Cartography
https://github.com/SwiftyJSON/SwiftyJSON
https://github.com/duemunk/Async

Using xcconfig files for your XCode Project

Mon, 24 Oct 2016 13:27:00 +0200

Xcode's Plugin Interface : Build Settings

Thu, 12 May 2016 15:54:00 +0200

Linking an OSX external bundle with a .dylib library

Thu, 12 May 2016 13:53:00 +0200

Solarized - Precision colors for machines and people

Tue, 20 Dec 2011 19:40:00 +0100

iPhone OpenGL Speed Tip – Turn Off Thumb Instructions

Tue, 20 Dec 2011 19:03:00 +0100

Porting Color Themes to Xcode 4

Sun, 03 Jul 2011 19:13:00 +0200

Making openframeworks v0.062 work with Xcode 3.2.5 Recently I wanted to do some…

Thu, 17 Mar 2011 15:38:00 +0100

Making openframeworks v0.062 work with Xcode 3.2.5

Recently I wanted to do some creative coding with openframeworks on iOS and OS X, but the installation of the library didn’t go flawlessly. Here’s a short summary how to get version 0.062 to work with Xcode 3.2.5 on Mac OS X 10.6.6:

download the openframeworks package from the official website: http://www.openframeworks.cc/download (direct link to file)
extract it to an arbitrary location
to install the xcode templates, follow the instructions in PATH_TO_OF_DIR/xcode templates/readme.txt. (The “dragging method” didn’t work for me, though, so I had to do the “manual” install.)
at this point we need to compile the openframeworks library, so open PATH_TO_OF_DIR/libs/openFrameworksCompiled/project/osx/openFrameworksLib.xcodeproj
when I try to compile the library with the default settings, I get 111367 (no kidding!) errors, so after some experiments I figured the following projects settings need to be set (open the project settings and go to the “build” tab):
- for Architectures set “32-bit Universal”
- for Base SDK set “Mac OS X 10.5”
- (optional, don’t do this if you’d like to support PPC-based Macs) for Build Active Architecture Only set TRUE (check)
Now the library compiled for me without any errors. You can compile both “Debug” and “Release” versions.
now you can go ahead and create an openframeworks project in Xcode by selecting “openFrameworks” in the User Templates section and select “Mac OS X empty example” in the right panel. It is very important where you save your project: it must be located in PATH_TO_OF_DIR/apps/ARBITRARY_DIR/PROJECTNAME. For me, for example: /Users/myusername/Programming/of_preRelease_v0062_osxSL_FAT/apps/Projects/NameOfMyCoolOFProject/. If you fail to place the project at the right deepness in the directory tree, the relative paths in the project setting won’t resolve correctly, thus your project won’t compile.
still we are not ready, because the default project settings are somewhat outdated, so go to your project settings and change the “Base SDK” to an existing one, 10.5 could be a good choice. (It might be a good idea to change the template project settings so that you wouldn’t have to do this every time you create a new project.)
at this point the project will finally compile, but there is a warning remaining: “Warning: The Copy Files build phase contains this target’s Info.plist file ‘openFrameworks-Info.plist’.” To overcome this, just go and click on the “Targets” section, and in the list view find the entry named “openFrameworks-Info.plist” and delete it.

Now your project should compile without any warnings or errors. Yay, congratulations!

Mac OS X Debugging Magic

Sat, 09 Oct 2010 13:59:00 +0200

how to debug EXC_BAD_ACCESS on iPhone

Sat, 09 Oct 2010 13:57:00 +0200

Great guide for memory-debugging in Instruments

Thu, 30 Sep 2010 23:34:00 +0200

A fantastic collection of Xcode tips & tricks

Tue, 14 Sep 2010 01:07:00 +0200

Quick Look source code preview & syntax highlighting on Mac Without much rambling, a…

Tue, 07 Sep 2010 14:15:00 +0200

Quick Look source code preview & syntax highlighting on Mac

Without much rambling, a solution for the problem presented in the title: http://code.google.com/p/qlcolorcode/

To change the color style (theme), use the following command:

defaults write org.n8gray.QLColorCode hlTheme [theme name]

Where [theme name] can be:

acid, bipolar, blacknblue, bright, contrast, darkblue, darkness, desert, easter, emacs, golden, greenlcd, ide-anjuta, ide-codewarrior, ide-devcpp, ide-eclipse, ide-kdev, ide-msvcpp, ide-xcode, kwrite, lucretia, matlab, moe, navy, nedit, neon, night, orion, pablo, peachpuff, print, rand01, seashell, slateGreen, the, typical, vampire, vim-dark, vim, whitengrey, zellner