Adding "--output-directory" option for the generate command.

[robbiehanson]

Motivation:

We're using cocoapods-keys in a project, and we automatically generate the .h/.m files during the build process (via a build script). This allows the developer to change key/value pairs as needed, and a simple "Build-and-Run" will automatically "do the right thing".

I.E. if they've changed a key/value pair, then simply compiling in Xcode, will automatically re-generate the corresponding XKeys.m file with the updated value. This helps reduce the cognitive overhead of using the system for the development team:

Steps before:

• update value in .env file
• don't forget to run 'pod install' !
• build-and-go in Xcode

Steps after:

• update value in .env file
• build-and-go in Xcode

Although this currently works, it's less than optimal, as modifying the .h/.m files everytime results in recompiling several files every build. This added feature allows the user to direct the generated .h/.m files elsewhere. Which enables use of diff tool, and thus can avoid overwriting files unnecessarily.

Once this pull request is merged, I can also add a wiki page that demonstrates:

• An example script that runs the 'pod keys generate' command.
• How to automatically integrate it via the Podfile and post_install hook.

[segiddins]

Just curious, why isn't the --project-directory option used by commands such as install and update sufficient?

[robbiehanson]

If I understand correctly, the --project-directory is to specify where the project itself resides. The --output-directory says where to put the generated .h/.m files.

For example, let's say I have a project here: ~/Foo/Foo.xcworkspace

Normally then, running the pod keys generate command will create the following files:

• ~/Foo/Pods/CocoaPodsKeys/FooKeys.h
• ~/Foo/Pods/CocoaPodsKeys/FooKeys.m

But if I instead run pod keys generate --output-directory=/Users/robbie/Foo/Temp/, it will instead create:

• ~/Foo/Temp/FooKeys.h
• ~/Foo/Temp/FooKeys.m

This allows me to execute the following in a build script (executed as part of the Pods/Keys Target, and run BEFORE compiling the source files):

• execute pod keys generate --output-directory=/Users/robbie/Foo/Temp/
• use the diff tool to see if the newly generated files (in '~/Foo/Temp/') are different from the official ones (in '~/Foo/Pods/CocoaPodsKeys/')
• If diff tool says they're different, then I can cp, and replace the official files
• Otherwise I do nothing, and thus no re-compiling is necessary

Side note: the --project-directory option doesn't seem to be working for pod keys commands. See issue #145

[segiddins]

Hmm, I don't really see the benefit to this? It installs where it does now because that's the directory the generated pod needs to have its source files in