> On Aug 14, 2018, at 2:43 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Yeah - not sure we're quite at the point where LLVM wants to start supporting two build systems again (used to be Configure+Make and the CMake system, now it's just the Cmake system), but if you want to make it work out-of-tree it shouldn't be too difficult (Google does this internally with the internal version of Bazel). Writing a short BUILD extension for running tblgen should be possible without too much complexity - not sure what Tensorflow is doing that makes its solution so complicated, it doesn't seem like it should be terribly hard, just a genrule to run tblgen and generate the appropriate files from the td files.Would it be technically possible for cmake to generate bazel files? If so, it seems that that could be a great bridge, and useful to other projects as well. -Chris
On Wed, Aug 15, 2018 at 10:04 AM Chris Lattner <clattner at nondot.org> wrote:> > > > On Aug 14, 2018, at 2:43 PM, David Blaikie via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > Yeah - not sure we're quite at the point where LLVM wants to start > supporting two build systems again (used to be Configure+Make and the CMake > system, now it's just the Cmake system), but if you want to make it work > out-of-tree it shouldn't be too difficult (Google does this internally with > the internal version of Bazel). Writing a short BUILD extension for running > tblgen should be possible without too much complexity - not sure what > Tensorflow is doing that makes its solution so complicated, it doesn't seem > like it should be terribly hard, just a genrule to run tblgen and generate > the appropriate files from the td files. > > Would it be technically possible for cmake to generate bazel files? If > so, it seems that that could be a great bridge, and useful to other > projects as well. >/maybe/? It's an interesting thought - not sure I know enough about either build system to have a very informed opinion here, though. - Dave> > -Chris > >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180815/57a4d30a/attachment.html>
There have been discussions about adding a Bazel generator before: https://cmake.org/pipermail/cmake-developers/2017-July/030144.html <https://cmake.org/pipermail/cmake-developers/2017-July/030144.html> There does seem to be interest in having that support in CMake, and I can't imagine any insurmountable reason why it couldn't be done. The real issue is that nobody has put in the time to do it. -Chris> On Aug 15, 2018, at 11:21 AM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > > > On Wed, Aug 15, 2018 at 10:04 AM Chris Lattner <clattner at nondot.org <mailto:clattner at nondot.org>> wrote: > > > > On Aug 14, 2018, at 2:43 PM, David Blaikie via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > > > Yeah - not sure we're quite at the point where LLVM wants to start supporting two build systems again (used to be Configure+Make and the CMake system, now it's just the Cmake system), but if you want to make it work out-of-tree it shouldn't be too difficult (Google does this internally with the internal version of Bazel). Writing a short BUILD extension for running tblgen should be possible without too much complexity - not sure what Tensorflow is doing that makes its solution so complicated, it doesn't seem like it should be terribly hard, just a genrule to run tblgen and generate the appropriate files from the td files. > > Would it be technically possible for cmake to generate bazel files? If so, it seems that that could be a great bridge, and useful to other projects as well. > > /maybe/? It's an interesting thought - not sure I know enough about either build system to have a very informed opinion here, though. > > - Dave > > > -Chris > > _______________________________________________ > LLVM Developers mailing list > llvm-dev at lists.llvm.org > http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-dev-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20180815/6f557040/attachment.html>