Xcode Project Configuration

Slides for my @CocoaHeadsBE talk from 31/03/2015

Transcript

1. Project Configuration 1
2. 2 @thomaskeuleers iOS Developer at iCapps
3. Table of contents • Targets • .xcconfig • Configurations • Demo • .plist 3
4. Why bother configuration? • Saves you time and prevents stupid mistakes • Keep it simple, only chose for a more advanced configuration when you really need to. • The bigger the project, the more important it gets 4
5. –https://developer.apple.com “specifies a product to build and contains the instructions for building the product from a set of files in a project or workspace ” Xcode Target 5
6. Xcode Target 6
7. Xcode Target • Outputs 1 product • Separates physically different build products Example: Tests, extension, … 7
8. Real world case: Step 1 8 Make a new app that has: • Application Target • Tests • Extension • Watchkit app
9. Xcode Target 9
10. Xcode Target 10
11. Setup completed 11
12. But then the app scales 12
13. … some parameters should be added 13
14. Additions Support testing environments Each environment has a separate build product: • Icon • Bundle identifier • Server url • … 14
15. We can handle this 15
16. Xcode Target 16
17. Xcode Target 17
18. Xcode Target - Bundle ID 18
19. Xcode Target - App Icon 19
20. Xcode Target - Server URL #if TARGET_TEST let serverURL = "https://test.companywebsite.be/api" #elseif TARGET_ACCEPT let serverURL = "https://accept.companywebsite.be/api" #else let serverURL = "https://companywebsite.be/api" #endif Step 1 Step 2 20
22. it’s also pretty messy… 22
23. Xcode Target duplication Benefit(s) Downsides Room for error Not scalable Quick setup Quick setup but made up time will catch up 23
24. File add 24
25. Are multiple targets bad? 25
26. When to use targets 26
27. Sharing code 27 Session 223 WWDC 2014
28. Cocoapods 28
29. Back to our real world case 29
30. Extensions are announced 30
31. Extension can only be embedded in 1 target… 31
32. Result 10 Targets for 2 build products (app + watch) with some deviations 32
33. Time for a change 33
34. Introducing .xcconfig 34
35. .xcconfig • Plain text key-value file • Declaring build parameters in one spot • Shared configuration for your target(s) 35
36. Adding one 36
37. Disclaimer This is just one way of using .xcconfig Demo 37 Transforming a project to use .xcconfig
38. .xcconfig completed 38
39. A little extra 39
40. AdHoc Distribution 40
41. Xcode Configurations 41
42. Xcode Configuration 42 • 2 standard ones • differ mostly in debug info and build optimisation • sufficient for product development needs • Most developers never need to change these Debug & Release
43. Xcode Configurations 43
44. So what do we change? Adhoc signing vs. Ordinary signing 44
45. Demo 45
46. .plist configuration 46
47. .plist configuration • Write mechanism yourself • Ok, but I like the Apple way 47
48. Recap 48
49. Q & A 49
50. Thanks! 50