News for hackers. Stuff that matters.
Re:Bazel Release 1.0 by ihnorton on Thursday October 10, 2019 @10:18AM (#21214756)
I hope that this 1.0 status will prompt the Qt people to take a closer look at Bazel, but that's probably strongly conditioned on the quality of Windows support. Qt Co. have indicated that CMake is the most likely replacement for qmake in Qt 6, which would be a lateral change at best.

Is anyone using Bazel to ship cross-platform GUI applications?

Re:Bazel Release 1.0 by adev_ on Thursday October 10, 2019 @12:56PM (#21216754)
> I hope that this 1.0 status will prompt the Qt people to take a closer look at Bazel

By the sake of God no.

The last thing I need to compile Qt is a gigantic framework requiring the JVM. Plus the fact Bazel has so many side effect that that even quantum physics experiments looks more reproducible: Just try to compile tensorflow and enjoy the fun.

Stick to CMake, thanks.

Re:Bazel Release 1.0 by weberc2 on Thursday October 10, 2019 @07:09PM (#21220129)
I get not wanting a JVM (although all else equal I’ll take the JVM dependency any day over CMake), but how is CMake _more_ reproducible than Bazel? The latter builds in a clean room, Make does not.
Re:Bazel Release 1.0 by adev_ on Friday October 11, 2019 @03:02AM (#21222176)
> how is CMake _more_ reproducible than Bazel?

Because CMake contrary to Bazel do not break its retro-compatibility in its options and config every two minor versions ?

> The latter builds in a clean room, Make does not.

Sandboxing should be the concern of the package manager / deployment pipeline, Not the build system concern. That just makes things redundant and painful to debug.

Re:Bazel Release 1.0 by weberc2 on Friday October 11, 2019 @07:22AM (#21223262)
> Because CMake contrary to Bazel do not break its retro-compatibility in its options and config every two minor versions ?

Lol that’s only recently true. CMake was infamous for breaking compatibility. Anyway, Bazel was pre-1.0 until just now, so of course expect some instability.

> Sandboxing should be the concern of the package manager / deployment pipeline, Not the build system concern. That just makes things redundant and painful to debug.

It makes things specifically very easy to debug. Not everyone enjoys troubleshooting issues on their machine due to their local environment.

Re:Bazel Release 1.0 by dgellow on Thursday October 10, 2019 @10:27AM (#21214871)
Isn’t Bazel jre based? I don’t think that something like Qt will ever go for a build tool that requires the whole java runtime as a dependency.

(Also, cmake has become the de facto solution for open source libraries, not sure why they would select something else)

Re:Bazel Release 1.0 by aiuto on Wednesday October 23, 2019 @09:17AM (#21334287)
Being written in Java is essentially a non-issue. Bazel ships as a binary that self-extracts a JRE for its own use. You don't have to install Java unless you want to build Java apps.

The real issue for highly reusable products like Qt is portability of the build tool. CMake works on the long tail of OSes, some of which do not have any usable JRE available. That limits the ability to use Bazel as the only build tool.

For Bazel to be useful to projects like Qt (and other horizontal libraries like openssl, ICU, curl, ...) one would need a system for generating CMakefiles from BUILD files. The developers of those apps could use Bazel to improve build and test scaling, and then generate CMake (or other build tool) files as part of their packaging and distribution. I don't propose that this is an easy thing to do - all rules would need translation into other languages - just that it is a path which may benefit some projects.

Re:Bazel Release 1.0 by ahartmetz on Thursday October 10, 2019 @10:39AM (#21215027)
Qt is moving to CMake for Qt6, they are already working on it. Qt6 release is planned in a year or so.
Re:Bazel Release 1.0 by dgellow on Thursday October 10, 2019 @11:52PM (#21221422)
I’m aware, that’s why I mentioned it.
Re:Bazel Release 1.0 by jchw on Thursday October 10, 2019 @11:45AM (#21215841)
CMake may have a longer history of being used by open source, but Meson has been growing in popularity for some important projects. I definitely prefer Meson to CMake.

Bazel is also a great build system, but yeah, the JRE dependency will obviously make it less desirable for some users. Still, I hope people consider it anyways, because its focus on correctness is pretty great.

Re:Bazel Release 1.0 by berti on Friday October 11, 2019 @12:59AM (#21221676)
Last time I checked meson still doesn't have great Qt support e.g. it can't track rcc dependencies [0]. Funnily enough that issue is about rcc not making dependencies available to the build system, but I believe it actually started doing so somewhere down the track. I did a little work on it a couple of years back but regrettably never followed up [1].

[0] https://github.com/mesonbuild/meson/blob/27c01dff01832fa9d0c... [1] https://github.com/mesonbuild/meson/issues/97#issuecomment-3...

Re:Bazel Release 1.0 by pjmlp on Friday October 11, 2019 @06:05AM (#21222906)
Unless Meson gets to support all the toolchains and OS supported by CMake, and the existing plugins eco system it is non starter.

Meson will most likely be kept as the GTK, GNOME build system.

Re:Bazel Release 1.0 by jchw on Friday October 11, 2019 @12:05PM (#21225663)
Non-sense. It only needs to support the toolchains and OSes people actually want, by no stretch of the imagination does it have to support all of the same stuff CMake does. It is not a non-starter for many.

It is the build system of lots of projects already, not just GNOME but also freedesktop stuff too, libinput is one.

Re:Bazel Release 1.0 by pjmlp on Friday October 11, 2019 @01:01PM (#21226215)
That is not how adoption at scale works.

Everyone on C++ community is gravitating towards CMake, Conan and vcpkg, they won't migrate to something else now.

Re:Bazel Release 1.0 by jchw on Friday October 11, 2019 @01:36PM (#21226580)
Yes it is. CMake was adopted long before it supported everything it supports today.
Re:Bazel Release 1.0 by pjmlp on Friday October 11, 2019 @03:10PM (#21227445)
Let us know when Meson gets first class support on Eclipse CDT, Clion, Qt Creator, KDevelop, Android Studio, VSCode and Visual Studio.
Re:Bazel Release 1.0 by jchw on Friday October 11, 2019 @03:19PM (#21227523)
OK, ping me in 3 years.
Re:Bazel Release 1.0 by pjmlp on Friday October 11, 2019 @03:40PM (#21227709)
Surely. I have seen too many carriages drive by.
Re:Bazel Release 1.0 by jchw on Friday October 11, 2019 @04:15PM (#21228039)
Actually, there’s already an excellent Meson plugin for VSCode, and a pretty good one for Qt Creator, so I hope you’re a fan of losing bets :p
Re:Bazel Release 1.0 by pjmlp on Friday October 11, 2019 @05:09PM (#21228494)
So far, everyone that has bet against CMake has lost to overtake it.

Scons, qmake, waf, premake, Gradle C++, MSBuild, ...

I know which horse to bet on.

Re:Bazel Release 1.0 by jchw on Friday October 11, 2019 @06:33PM (#21229089)
Scons and qmake both predate CMake. It’s weird to characterize them as trying to “overtake” CMake; that’s not really a thing I think happened. As a matter of fact, there was a time when qmake was a better option; it was a fairly complete Makefile generator that had good support for subprojects and out of tree builds.

Then again, this is all irrelevant. What these projects all had to offer at one point is historical. Qt has to leave qmake because of qmake. During that time they evaluated many options, including a fairly innovative design called qbs - Qt Build System. In the end, the choice of CMake makes a lot of sense, as it is clearly the best available choice that had ecosystem support. Qt is unlikely to switch build systems again soon.

This entire argument has happened before, but instead of meson vs CMake it was CMake vs autoconf. The thing is, I suspect CMake will still exist even as Meson inevitably continues to gain traction, just as autoconf (unfortunately) exists today.

There is, in fact, room for more C++ build systems, and almost definitely room for better interop. (Meson and CMake have some interop today.)

Re:Bazel Release 1.0 by weberc2 on Thursday October 10, 2019 @02:14PM (#21217548)
> Also, cmake has become the de facto solution for open source libraries, not sure why they would select something else

It is definitely not the de facto solution for open source. After using CMake as a C++ developer, I will never use CMake again. I simply don't have time to write a program in a slow, stringly-typed, ad hoc DSL just to build my actual program.

Re:Bazel Release 1.0 by renox on Thursday October 10, 2019 @03:23PM (#21218245)
At work, we use cmake; i've never seen a technology with so little 'traction'; I know one guy who is good with cmake all the other (including me) avoid touching this thing as much as possible!

Sigh, I remember debugging a complex makefile generation issue (it took me 3 days, two guys before me failed) and it didn't make me hate the make tool, I just wished it had better tracing/debugging but cmake that's a different story..

Re:Bazel Release 1.0 by jcelerier on Thursday October 10, 2019 @03:26PM (#21218280)
> It is definitely not the de facto solution for open source. After using CMake as a C++ developer, I will never use CMake again.

most projects are using CMake nowadays : https://www.jetbrains.com/research/devecosystem-2018/cpp/

Re:Bazel Release 1.0 by weberc2 on Thursday October 10, 2019 @06:14PM (#21219716)
Most _C++_ projects are using CMake, but it has virtually no adoption among other mainstream languages, and given most open source is not C++, CMake definitely doesn't have any strong share of the open source market.
Re:Bazel Release 1.0 by dgellow on Thursday October 10, 2019 @11:58PM (#21221447)
My comment was about Qt, which is a C++ project. Of course CMake doesn’t have any market share outside of C++, but in the C++ world it has become the main build tool for open source projects. Even Microsoft is now spending their time supporting CMake via both Visual Studio and vcpkg.
Re:Bazel Release 1.0 by henryaj on Thursday October 10, 2019 @12:43PM (#21216601)
Please[0] is a Bazel-like build system written in Go.

[0] http://please.build/

Re:Bazel Release 1.0 by andrewbinstock on Thursday October 10, 2019 @02:28PM (#21217676)
But, unlike Bazel, it doesn't run on Windows, which is a big limitation in enterprises.
Re:Bazel Release 1.0 by Quekid5 on Thursday October 10, 2019 @02:35PM (#21217730)
That, and it doesn't actually support the multitude of weird things that Bazel does.