what??! there is no up-to-date pkg-config module. you know. the standard way of getting dependencies as a piece of software which will be packaged by a distro, assuming one doesn't want to get keelhauled by distro maintainers?
does anyone actually ... use #bazel for anything that expects to be packaged by a Linux distro without bazel owning the entry point?
outdated rules: https://github.com/cherrry/bazel_pkg_config
🌗 發布 rules_img：在 Bazel 中實現更高效的容器映像檔構建流程
➤ 從資料搬運工到元數據管家：重新定義容器映像檔的封裝效率
✤ https://www.tweag.io/blog/2025-12-18-rules_img/
在大型 Bazel 專案中構建容器映像檔時，開發者經常遇到建置速度變慢、CI 耗時增加等問題，其核心原因在於傳統工具必須頻繁下載與移動數百 MB 甚至 GB 級別的基礎映像檔圖層。本文介紹了新一代規則集 `rules_img`，它透過「元數據優先」的設計理念，徹底重塑了映像檔的建置邏輯。與現行的 `rules_oci` 不同，`rules_img` 在構建階段僅處理極輕量級的 JSON 配置與清單文件，而將沈重的資料塊（blobs）留在遠端存儲中，直到最後推送階段才進行必要的串流傳輸。這種優化大幅降低了網路頻寬與本地磁碟的負擔，為現代化的軟體交付流程提供了更為敏捷的解決方案。
+ 終於有人解決了 CI 跑一次就要抓好幾 GB 基礎映像檔的痛點，這對於節省雲端計算成本和頻寬非常有幫助。
##Bazel #容器化 #DevOps #雲原生 #軟體工程
🚀✨ Behold, "rulesimg" – because the world was desperately waiting for a *faster* way to do something #Bazel was already good at. 🙄 Because clearly, what #developers need is more layers and configurations to spice up their effortless #containerization experience. 😂
https://www.tweag.io/blog/2025-12-18-rules_img/ #rulesimg #techhumor #softwareengineering #HackerNews #ngated
A faster path to container images in Bazel
https://www.tweag.io/blog/2025-12-18-rules_img/
#HackerNews #Bazel #Container #Images #Faster #Path #Tweag #DevOps
Why not switch your crappy software from crappy #SCons build system to even more crappy #Bazel build system over a patch release, call it "fully backwards compatible", and then effectively leave all the distros stuck on old versions with half a dozen vulnerabilities?
Yeah, just a random reminder that #MongoDB is total crap, and you shouldn't use it. Or expect people to package it for you.
Bazel không chỉ là một công cụ build — đó là cả một hệ sinh thái gồm các rule, công cụ và cộng đồng hỗ trợ xây dựng phần mềm quy mô lớn. Từ rules như rules_python, rules_docker đến toolchains, remote execution, IDE integrations và các dự án nổi tiếng như TensorFlow, Kubernetes — tất cả tạo nên "Bazel ecosystem". #Bazel #DevTools #BuildSystem #Engineering #HệSinhTháiBazel #CôngCụLậpTrình #XâyDựngPhầnMềm
https://dev.to/sushilbaligar/what-exactly-is-the-bazel-ecosystem-5g79
Slack folks gave an interesting talk about their Gradle to Bazel for their Android builds journey and why the effort ultimately got cancelled.
Testing Blender Launcher bazelized with Claude Sonnet 4.5 #Blender #Bazel - fork here: https://github.com/Vertexwahn/Blender-Launcher-V2-bazelized - run via `bazel run //:blender_launcher -- --help`, `bazel run //:blender_launcher -- -force-first-time`, `bazel run //:blender_launcher`
choosing a build system is a really technical choice that's all about the language you code in, not something strategic, right? not necessarily; the same principles that make #Bazel so powerful are showing up in other, broader tools for devops like Helm. but it's too hard to adopt, right? maybe not!
there are hardly any other companies that work exactly like Google, but Google is *really big* and uses a lot of languages, so tools written to help Google, like Bazel, have something for almost everyone Ulf Adams of #Engflow tells me - and almost every org has the 'works on my machine' problem when it comes to debugging.
Bazel promises fast, reproducible builds with artefacts you can cache and reuse and you can get the benefits without having to adopt all the rigour Alex Eagle of #AspectBuild explains to me, while Max Kanat-Alexander (who used to run Google's code health team) tells me why being hermetic and reproducible is so powerful when you can do more of it.
if you're not Adobe, Nvidia, Snowflake, LinkedIn or one of the other big companies adopting Bazel with the resources to do a huge migration, that doesn't mean it's not for you: there are JetBrains and VScode plugins and an entire ecosystem of companies run by people who worked on Bazel and Blaze - like EngFlow and Aspect Build.
Bazel is also a really interesting open source governance story. the usual tension between a founder company that needs to control the tool it relies on and a large and vocal open source community gets a possibly unique solution: an open source project for the engine and a foundation for the rules (written in Starlark, another powerful tool) that will be the voice of the community for Google, Helen Altshuler tells me.
will it work? well, that's the same split as inside Google itself, EngFlow's Luis Pino tells me, so there's a good chance it will,.
https://www.thestack.technology/why-everyone-is-moving-to-googles-bazel-build-system/
Stareți de pe Athos le cere grecilor să nu ia cărțile de identitate digitale noi - identitatea digitală "Trăim, fără îndoială, în vremuri apocaliptice. Deci, să dobândim o "îngrijorare bună" cu privire la ceea ce se întâmplă în jurul nostru. În spatele comodităților promise ale societății digitale moderne se află cătușele unui sistem neliberal", au subliniat călugării. 👉 https://c.aparatorul.md/dvo79 👈 #Antihrist #anulareanumerarului #Apocalipsei #Atoniții #bazel...
https://c.aparatorul.md/dvo79
"Bazel has a tremendously large number of flags. Many are obscure, many are important to use, and many have an undesirable default value.“
So sassy! 😂
https://github.com/mxpv/rules_vulkan/releases/tag/v0.7.0 #Bazel One of the easiest ways to setup Vulkan. Can you build with one command? With those rules you can. Works even on macOS via MoltenVK. A bit unsure about hardware ray tracing support on M1-M5 - will this proberly mapped to Metal? We will see.
At #BazelCon, Malte Poll presented asset-fuse, a FUSE-based filesystem for bringing large files into Bazel or Buck2. 🗂️
Watch the recording: https://www.youtube.com/watch?v=i07kTWg38q8
Want to learn the Bazel basics — including tips for debugging build errors?
▶️ Watch the recording of Alejandro Gómez Londoño’s #BazelCon training: https://www.youtube.com/watch?v=1CX6x2siC28
🌘 遷移至 Bazel 符號宏
➤ 從傳統到符號：掌握 Bazel 宏的現代化遷移之路
✤ https://www.tweag.io/blog/2025-11-20-migrating-bazel-symbolic-macros/
本文為資深 Bazel 工程師或負責現代化程式碼建構的中層技術人員提供指南，闡述如何從傳統宏遷移至 Bazel 的符號宏。符號宏透過強化類型參數、限定目標可見性，提升了程式碼的清晰度與管理性。文中探討了符號宏在命名約束、存取權限、參數傳遞與預設值設定上的具體實踐與注意事項，並透過程式碼範例說明如何正確運用這些特性，以實現更穩健、易於理解的建構系統。
+ 這篇文章對符號宏的解釋相當深入，特別是關於命名規則的部分，非常實用！
+ 感謝作者詳細的比較，讓我更清楚傳統宏和符號宏在參數處理上的差異，避免了不少潛在 bug。
#Bazel #軟體建構 #開源
At #BazelCon, Malte Poll presented rules_img, a faster and more efficient approach to building container images with Bazel. 🛠️
Watch the full recording: https://www.youtube.com/watch?v=biYXmAv4Ppk
Think Bazel is just for code? Think again.
🎬 Watch the recording of Daniel Thagard’s #BazelCon talk to learn how to connect build systems with media editing workflows: https://www.youtube.com/watch?v=YrcsDu63OWA
New blog post from Alexey Tereshenkov. For you experience #Bazel engineers migrating from legacy macros to symbolic macros as introduced in Bazel 8. Read for Alex's guide with hands-on examples, actionable tips, and subtleties to be wary of: https://www.tweag.io/blog/2025-11-20-migrating-bazel-symbolic-macros/
Didn't make it to #BazelCon?
Watch Guillaume Maudoux’s talk on Python dependency management with FawltyDeps in Bazel. 🐍
🎥 Check out the recording: https://www.youtube.com/watch?v=5j2bb44CV1g
