英文:
Why doesn't tensorflow's go/ subdirectory use go_library from Bazel rules_go?
问题
在https://github.com/tensorflow/tensorflow/tree/master/tensorflow/go的README中描述了一个有些不连贯的构建过程。
为什么不使用SWIG和https://github.com/bazelbuild/rules_go中的go规则呢？
英文:
The README in https://github.com/tensorflow/tensorflow/tree/master/tensorflow/go describes a build process that's a bit disjointed.
Why not use SWIG and the go rules in https://github.com/bazelbuild/rules_go?
答案1
得分: 1
这没有什么好的理由，除了"历史偶然性"之外。在rules_go非常成熟之前，Tensorflow已经有了Go代码，所以他们实现了自己的规则。
在过去的几个月里，我全职致力于rules_go。今年我们的主要任务是通过构建所需功能并使规则易于使用，支持Kubernetes迁移到Bazel。当这个工作完成后（很快），我们将开始支持其他使用Bazel和Go的项目。我希望其中包括Tensorflow。
英文:
There's no good reason for this, other than "historical accident". Tensorflow had Go code before rules_go was very mature, so they implemented their own rules.
I've worked on rules_go full time for the past several months. Our main priority this year has been to support Kubernetes' migration to Bazel by building out the features they need and making the rules simple to use. When that effort is completed (soon), we'll move on to supporting other projects using Bazel and Go more directly. I hope this will include Tensorflow.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论