Hi Rob, unfortunately Cocoapods wants to distance themselves from the use cases of a build system, so the solution you've found is the only one that fits its system.
Another, a bit more blunt, way to make Cocoapods rerun the "prepare_command" commands is to delete your workspace and Podfile.lock files, and run "pod install" again. Cheers, Jorge On Wednesday, November 11, 2015 at 9:43:51 AM UTC-8, Rob Cecil wrote: > > The only solution I have found is to bump the version number in the > .podspec for your proto files. > > On Monday, November 9, 2015 at 12:14:34 PM UTC-5, Rob Cecil wrote: >> >> I'm using Cocoapods and my initial project build succeeds. Steps >> >> 1. Created .podspec referencing my .protos and output directory for >> generated objective-c code. >> 2. Created podfile >> 3. Ran pod install. >> 4. Success, open xcworkspace. >> >> Now when I try to either: >> >> 1. Update a .proto OR >> 2. touch podspec >> >> And run "pod update" >> >> I never see the codegen happen. >> >> What are the steps/best practice to continously refine .proto definitions >> and regenerate code? >> >> Thanks! >> > -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/protobuf. For more options, visit https://groups.google.com/d/optout.
