https://duan.ca/tag/objective-c/ <p>Xcode is slow. Enough said. What's worse, sometimes I find myself relying too much on auto-completion with Cocoa Touch, a blessing and a curse!</p> <p>So I searched for an alternative workflow in command line. The result was rather confusing: there are posts about using <code>xctool</code> or <code>xcodebuild</code> to build Xcode targets, using <code>ios-sim</code>, <code>simctl</code> or <code>instruments</code> to manage and manage or launch simulators. Most of the information is out of date.</p> <p>Eventually though, I was able to piece together an answer for my needs. That is, given an iOS project set up with Xcode 6, I want to</p> <ol> <li>build a target.</li> <li>launch a iOS simulator.</li> <li>install the built .app bundle to the launched simulator.</li> <li>run the installed app.</li> <li>uninstall the app from the simulator.</li> </ol> <p>All in command line, with Xcode <em>closed</em>.</p> <p>Before we proceed to the steps, you need to gather a few pieces of information:</p> <ol> <li>the Xcode build scheme of your choice (e.g. &quot;AwesomeApp&quot;).</li> <li>your app bundle ID (e.g. &quot;com.awesome.app&quot;).</li> <li>name of an existing simulator (e.g. &quot;iPhone 6 Plus&quot;). If you don't want to look it up in Xcode GUI, look for it in output of command <code>xcrun simctl list</code> .</li> </ol> <p>Ready? Here we go.</p> <p>(These commands should be run in the project folder).</p> <p>Build the target:</p> <pre><code>xcodebuild -scheme AwesomeApp -destination 'platform=iphonesimulator,name=iPhone 6 Plus' -derivedDataPath build </code></pre> <p>Launch the simulator:</p> <pre><code>xcrun instruments -w 'iPhone 6 Plus' </code></pre> <p>Install the bundle (after simulator is launched and target is built with previous commands):</p> <pre><code>xcrun simctl install booted build/Build/Products/Debug-iphonesimulator/AwesomeApp.app </code></pre> <p>Launch the app in simulator (after it's installed with the previous command):</p> <pre><code>xcrun simctl launch booted com.awesome.app </code></pre> <p>Uninstall the bundle:</p> <pre><code>xcrun simctl uninstall booted com.awesome.app </code></pre> <p>Quite a few parameters needs to be added for the build step if you have a comlex project. Please RTFMs. Write some script to automate the steps, if are a lazy typiest like me.</p> Sat, 07 Feb 2015 20:35:02 -0800 https://duan.ca/2015/02/07/build-and-run-ios-apps-in-commmand-line/ https://duan.ca/2015/02/07/build-and-run-ios-apps-in-commmand-line/ <p>You have a <code>UITableViewController</code> with a couple of static cells, you want to invoke some code for each cell in the delegate. Here's a quick way to do it:</p> <pre><code> - (void)tableView:(UITableView *)tableView didSelectRowAtIndexPath:(NSIndexPath *)indexPath { SEL action = (SEL[]){@selector(method1), @selector(method2)}[indexPath.row]; ((void (*)(id, SEL))[self methodForSelector: action])(self, action); } </code></pre> <p>It's got everything you love about C and Objective-C: array literals, function pointers, casting, selectors and something called <a href="http://www.cocoawithlove.com/2008/02/imp-of-current-method.html">IMPs</a>.</p> <p>This piece of code maps selected cells to methods by putting methods by indexing selectors in a C array.</p> <p>Why all the fuss on the second line? wouldn't a simple <code>performSelector:</code> work? The short answer is: to show the compiler that we are responsible adults. You can read more about it [here](SO Answer);</p> Sat, 03 May 2014 13:42:00 -0600 https://duan.ca/2014/05/03/tableview58didselectrowatindexpath58-in-two-lines/ https://duan.ca/2014/05/03/tableview58didselectrowatindexpath58-in-two-lines/