This MWE looks interesting. When I looked over the file it was unclear to me how it uses Nix. I had the following questions:
Is Nix used here as a dependency manager, enabling a package to build over buck?
I saw that a written build.nix is used. Is it right that you somehow use a destinct storage for Nix, I saw some „import <…>“syntax? Is this trying to encapsulate nix packages from another? How does this work?
Is it right that you integrated nix directly in the buck starlak files differently to the approach „use nix to setup the enviornment with all build tools available, then use buck to build the project“. You are doing something different here I guess maybe using Nix in a even more interessting way? You are also building the projects components as package?
Thanks for the clarifications. I am just wondering what your urge was to combine Nix and Buck as you did, it sounds great 😊, Nix is great but not really a monorepo build tool, so thats probably why?
1 Answered parts of my question it was a good read. So this repo is „ Buck drives The tools“ over nix :). I still dont get if each component in this monorepo builds a nix package at the end? Does it? Build dependencies (fetched over nix) are specified where for a component?
This MWE looks interesting. When I looked over the file it was unclear to me how it uses Nix. I had the following questions:
Thanks for the clarifications. I am just wondering what your urge was to combine Nix and Buck as you did, it sounds great 😊, Nix is great but not really a monorepo build tool, so thats probably why?