How do you setup your Cocoa projects? Do you always set same warnings, clone configurations and do bunch of other stuff? Or maybe you work in a big company and you are missing some standardised setup?
Programmers tend to automatise boring and repetitive tasks, yet I often see people spending time and time again configuring their Xcode Projects, even thought they always set it up same way.
We all know that Xcode templating system is far from perfect, beside we often use different templates, but same level of warnings, scripts etc.
What if you could define your project setup once (even with optional stuff) then just apply that to all your projects?
Enter crafter
That's why I've created crafter, a ruby gem that you can install, setup your configuration once and enjoy hours of time saved.
So how does it work?
Install it by calling:
gem install crafter
crafter reset
this will create your personal configuration file at ~/.crafter.rb
now open that file with your favourite editor and you will see default configuration, along with description of different parts:
load "#{Crafter::ROOT}/config/default_scripts.rb"
# All your configuration should happen inside configure block
Crafter.configure do
# This are projects wide instructions
add_platform({:platform => :ios, :deployment => 6.0})
add_git_ignore
duplicate_configurations({:adhoc => :debug, :profiling => :debug})
# set of options, warnings, static analyser and anything else normal xcode treats as build options
set_options %w(
RUN_CLANG_STATIC_ANALYZER
GCC_TREAT_WARNINGS_AS_ERRORS
)
# set shared build settings
set_build_settings({
:'WARNING_CFLAGS' => %w(
-Weverything
-Wno-objc-missing-property-synthesis
-Wno-unused-macros
-Wno-disabled-macro-expansion
-Wno-gnu-statement-expression
-Wno-language-extension-token
-Wno-overriding-method-mismatch
).join(" ")
})
# and configuration specific ones
set_build_settings({
:'BUNDLE_ID_SUFFIX' => '.dev',
:'BUNDLE_DISPLAY_NAME_SUFFIX' => 'dev'
}, configuration: :debug)
set_build_settings({
:'BUNDLE_ID_SUFFIX' => '.adhoc',
:'BUNDLE_DISPLAY_NAME_SUFFIX' => 'adhoc'
}, configuration: :adhoc)
set_build_settings({
:'BUNDLE_ID_SUFFIX' => '',
:'BUNDLE_DISPLAY_NAME_SUFFIX' => ''
}, configuration: :release)
# set non boolean options
set_build_settings ({
:'OTHER_CFLAGS' => '-Wall'
})
# target specific options, :default is just a name for you, feel free to call it whatever you like
with :default do
# each target have set of pods
pods << %w(NSLogger-CocoaLumberjack-connector TestFlightSDK)
# each target can have optional blocks, eg. crafter will ask you if you want to include networking with a project
add_option :networking do
pods << 'AFNetworking'
end
add_option :coredata do
pods << 'MagicalRecord'
end
# each target can have shell scripts added, in this example we are adding my icon versioning script as in http://www.merowing.info/2013/03/overlaying-application-version-on-top-of-your-icon/
scripts << {:name => 'icon versioning', :script => Crafter.icon_versioning_script}
# we can also execute arbitrary ruby code when configuring our projects, here we rename all our standard icon* to icon_base for versioning script
icon_rename = proc do |file|
extension = File.extname(file)
file_name = File.basename(file, extension)
File.rename(file, "#{File.dirname(file)}/#{file_name}_base#{extension}")
end
Dir['**/Icon.png'].each(&icon_rename)
Dir['**/[email protected]'].each(&icon_rename)
Dir['**/Icon-72.png'].each(&icon_rename)
Dir['**/[email protected]'].each(&icon_rename)
end
# more targets setup
with :tests do
add_option :kiwi do
pods << 'Kiwi'
scripts << {:name => 'command line unit tests', :script => Crafter.command_line_test_script}
end
end
end
As you can see the configuration files is quite easy, yet is pretty flexible. Once you set it up as you see fit, go to your project folder (the one with xcodeproj, workspace etc.) and call:
crafter
it will guide you through project setup, with default configuration it would look like this:
1. sample
2. sampleTests
Which target should I use for default?
1
1. sample
2. sampleTests
Which target should I use for tests?
2
do you want to add networking? [Yn]
n
do you want to add coredata? [Yn]
y
do you want to add testing? [Yn]
n
duplicating configurations
setting up variety of options
preparing git ignore
preparing pod file
adding scripts
Finished.
Now your project should have all options applied, generated Podfile (call pod install or set it up in your configuration).
I'm learning Ruby, so I'm looking forward to pull requests on GitHub
Send me your thoughts, I'm merowing_ on twitter
Acknowledgements:
The App Business (the company I worked for) for supporting my idea.
to @alloy, @orta, @romainbriche - for taking some of their valuable time and sharing their thoughts about beta version.
Inspired by liftoff
![post_install hook on Podfile [question]](https://avatars.githubusercontent.com/u/2642850?v=4)
431 Dec 12, 2022
1.3k Dec 31, 2022
5.9k Jan 2, 2023
22 Jan 5, 2023
438 Nov 8, 2022
60 Dec 12, 2022
22 Jul 18, 2022
78 Jan 13, 2021
21 Dec 14, 2022
2 Apr 9, 2022
7 Jan 1, 2023
164 May 4, 2022
64 Jun 3, 2021
130 Nov 8, 2022
6.1k Jan 2, 2023
3.2k Dec 30, 2022
43 Sep 28, 2022
51 Oct 27, 2022
1.1k Dec 24, 2022