3 ms·

> Dflat at the moment requires Bazel. Very few people use Bazel for Android or iOS. Anyone not from Google care to let us know if you're using Bazel for mobile

by throw14082020 6y ago

> Dflat at the moment requires Bazel. Very few people use Bazel for Android or iOS. Anyone not from Google care to let us know if you're using Bazel for mobile development?

deleted 6y ago
[deleted]
pjmlp 6y ago
The irony with Bazel and Google, is that not even Google's own teams bother with Gradle for Android, the large majority seems to prefer use Bazel as per public projects.
- fnord123 6y ago
  Seeing as Bazel comes out Of Google, there's not a great deal of irony there.
  - pjmlp 6y ago
    There is, the Google own teams cannot be bothered to use what outsiders are forced to use when targeting Android.
    - qbasic_forever 6y ago
      I think it's more complex than that, bazel (and its predecessor blaze) were created to make monorepo development at google scale work. They use bazel/blaze not because it works better or more easily for Android, they use it because their entire engineering culture depends on an enormous monorepo of sharing code and rapid changes across the company codebase. There are some great papers they've written about bazel that go into these issues and more.
liuliu 6y ago
Dflat's compiler requires Bazel to build because it is easier to reference to flatbuffers' source code with Bazel than with Swift Package Manager. The runtime itself (which you delivers with your app) can be built with either Bazel or Swift Package Manager (as suggested through CI). It potentially can also be built with CocoaPods, I simply don't provide an official package on CocoaPods at the moment.
rockwotj 6y ago
My company uses bazel for Android development. We tried to use it for iOS but ran into issues with cocoapods. Pinterest uses bazel for their iOS app: https://medium.com/pinterest-engineering/developing-fast-reliable-ios-builds-at-pinterest-part-one-cb1810407b92 https://medium.com/pinterest-engineering/developing-fast-rel...

> Dflat at the moment requires Bazel. Very few people use Bazel for Android or iOS. Anyone not from Google care to let us know if you're using Bazel for mobile development?

deleted 6y ago

[deleted]

pjmlp 6y ago

The irony with Bazel and Google, is that not even Google's own teams bother with Gradle for Android, the large majority seems to prefer use Bazel as per public projects.

fnord123 6y ago
Seeing as Bazel comes out Of Google, there's not a great deal of irony there.
- pjmlp 6y ago
  There is, the Google own teams cannot be bothered to use what outsiders are forced to use when targeting Android.
  - qbasic_forever 6y ago
    I think it's more complex than that, bazel (and its predecessor blaze) were created to make monorepo development at google scale work. They use bazel/blaze not because it works better or more easily for Android, they use it because their entire engineering culture depends on an enormous monorepo of sharing code and rapid changes across the company codebase. There are some great papers they've written about bazel that go into these issues and more.

liuliu 6y ago

Dflat's compiler requires Bazel to build because it is easier to reference to flatbuffers' source code with Bazel than with Swift Package Manager. The runtime itself (which you delivers with your app) can be built with either Bazel or Swift Package Manager (as suggested through CI). It potentially can also be built with CocoaPods, I simply don't provide an official package on CocoaPods at the moment.

rockwotj 6y ago

My company uses bazel for Android development. We tried to use it for iOS but ran into issues with cocoapods. Pinterest uses bazel for their iOS app: https://medium.com/pinterest-engineering/developing-fast-reliable-ios-builds-at-pinterest-part-one-cb1810407b92 https://medium.com/pinterest-engineering/developing-fast-rel...