Correct, reproducible, fast builds for everyone not running Windows
Not really sure why this is getting downvoted - it's kind of an important detail when choosing a build system if you have to do multiplatform deployment.
Bazel – Correct, reproducible, fast builds for everyone
21–30 of 185 posts
Re: Bazel – Correct, reproducible, fast builds for everyone
#22Working at Google, Blaze is one of the technologies that amazes me most. Any engineer can build any Google product from source on any machine just by invoking a Blaze command. I may not want to build GMail from source (could take a while) but it's awesome to know that I can. I think this could be hugely useful to very large open source projects (like databases or operating systems) that may be intimidating for contri…
I've started at Google 4 months ago, and it's one of the best things to discover. Now open-sourced :)
Re: Bazel – Correct, reproducible, fast builds for everyone
#23A couple of questions:
* If I have a Maven-based project with heavy reliance on pre-built jars from Maven Central, what's the recipe to port it to Bazel?
* Related, if I have multiple github repos, say a couple open source libraries and a couple private repos, what's a good recipe in conjunction to Bazel?
Re: Bazel – Correct, reproducible, fast builds for everyone
#24Correct, reproducible, fast builds for everyone not running Windows
Not really sure why this is getting downvoted - it's kind of an important detail when choosing a build system if you have to do multiplatform deployment.
I am pretty sure it has nothing to do with the average population being biased.
Re: Bazel – Correct, reproducible, fast builds for everyone
#25Is this the tool that Google uses to build its Golang source? Or is that something else which is not available?
Re: Bazel – Correct, reproducible, fast builds for everyone
#26Earlier quoted context omitted.
Any plans on supporting Windows? That will definitely increase the adoption of Bazel.
http://bazel.io/docs/FAQ.html - "What about Windows? We have experimented with a Windows port using MinGW/MSYS, but have no plans to invest in this port right now. Due to its Unix heritage, porting Bazel is significant work. For example, Bazel uses symlinks extensively, which has varying levels of support across Windows versions." In other words: it's a lot of work, and frankly, our team doesn't know enough about win…
Thanks for the feedback! Hopefully the community will contribute..
Re: Bazel – Correct, reproducible, fast builds for everyone
#27Correct, reproducible, fast builds for everyone not running Windows
Not really sure why this is getting downvoted - it's kind of an important detail when choosing a build system if you have to do multiplatform deployment.
I didn't downvote him but it sounds like "he's driving angry". He does work for that "evil" company in Redmond. :-). Maybe he can help make F# a great cross-platform language and increase the goodwill? Microsoft did an incredible job with F# but it really only runs well on Windows.
Re: Bazel – Correct, reproducible, fast builds for everyone
#28What would be needed to get this to work with Haskell?
I read in the "Getting started":
> You can now create your own targets and compose them.
So does this mean it is a replacement for `make`? => Yes
Found the answer here: http://bazel.io/docs/FAQ.html
Re: Bazel – Correct, reproducible, fast builds for everyone
#29A couple of questions: * If I have a Maven-based project with heavy reliance on pre-built jars from Maven Central, what's the recipe to port it to Bazel? * Related, if I have multiple github repos, say a couple open source libraries and a couple private repos, what's a good recipe in conjunction to Bazel?
[deleted]
Re: Bazel – Correct, reproducible, fast builds for everyone
#30Earlier quoted context omitted.
Not really sure why this is getting downvoted - it's kind of an important detail when choosing a build system if you have to do multiplatform deployment.
I didn't downvote him but it sounds like "he's driving angry". He does work for that "evil" company in Redmond. :-). Maybe he can help make F# a great cross-platform language and increase the goodwill? Microsoft did an incredible job with F# but it really only runs well on Windows.
If he works for MS he has zero right to even be mildly annoyed, since we have for decades been living in a world where "only runs on Windows" isn't even in the small print.