[RFC] Bazel support

[garrettmoon]

From @nguyenhuy on March 15, 2017 15:37

With recent internal developments around build tools, we'll need Bazel support for ASDK in the next few months. The first step is to be able to build ASDK-Core and tests. Then it'll be nice to eventually build PINRemoteImage and PINCache, and sample projects. Finally, by the end of this year, hopefully we'll have a Bazel CI and HTTP cache that should boost our build time quite significantly.

Buck support, sadly, has seen limited usage but I hope it'll not be the case for Bazel support. We can keep Buck support for now and remove it when it becomes a burden to maintain.

Copied from original issue: facebookarchive/AsyncDisplayKit#3184

[jerrymarino]

Hey @garrettmoon - is this still an issue? I recently setup an test case for Texture under Bazel over at PodToBUILD. Via PodToBUILD it's guaranteed to build under Bazel identically to Xcode, and no one needs to maintain BUILD files, since PodToBUILD generate the build files based on Podspecs - Texture.podspec. This has been the supported way to build Texture ( and all internal cocoapods ) under Bazel since we migrated 🎉

[LeeWong]

I tried PodToBUILD to build texture. It does not seem to work well with Swift app.

[bolsinga]

@LeeWong Please file a bug on PodToBUILD for your issue; It's used extensively at Pinterest with Texture. We update to master weekly.

@garrettmoon I agree with @jerrymarino I think this may be closed.