Sorry to dig this old thread.
I now one of the solution right now is to put the enum to different proto
file and put them into different package. But that doesn't really work if
the enums are under the same message.
I would suggest add an option for c/c++, like below:
enum Foo {
option c_
The use of Cocoapods seems to be an alternative to makefiles ?
On Monday, November 9, 2015 at 12:42:16 PM UTC-5, Henner Zeller wrote:
>
> Isn't this what Makefiles are for ?
>
> On 9 November 2015 at 09:14, Rob Cecil >
> wrote:
> > I'm using Cocoapods and my initial project build succeeds. Step
Isn't this what Makefiles are for ?
On 9 November 2015 at 09:14, 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
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
