Keith Smiley
Keith Smiley
Thanks, this is all good now, we can close unless you want to keep around to track the core issue
cc @meteorcloudy
cc @philwo since you did the last one :pray:
Yea I guess considering master doesn't have that warning that would be ideal. The project I'm looking at uses the .bazelrc configs, but doesn't actually care about the rules that...
I assume the go version will be the one to stick around, but FWIW I don't think the `go build` solution should be recommended since we probably shouldn't assume that...
I'm using bazelisk 1.1.0 https://github.com/bazelbuild/bazelisk/releases/tag/v1.1.0
Any reason Bazelisk couldn't run your Bazel to get this?
Can you add a sample project that reproduces the issue?
The problem here is that since you want CardIO to be a dependency of both your app, and a dynamic framework, CocoaPods will refuse to do this since that would...
You have the dependency on it in 2 places though, TestProj (in the podspec) and TestProjFramework (in the Podfile)