I am considering what larger effort I can help on (in small chunks) over the next month or so. I was considering working on having BUCK support the source-layer approach CMake uses. My guess is that we can make this work by first running CMake in a

buck-out/cmake

folder to checkout repos and patch files, then run BUCK with static configuration to expect third-party code in

./buck-out/cmake

. Then the significant changes to BUCK logic only include adapting the compile logic in CMake, which should be easy. This will enable us to move to newer third-party library versions and remove all dependence on the facebook pre-built layer. The downside of me working on it is that someone else might be able to move faster. Suggestions for what I should work on / how I could approach what I referenced above?

I think it is interesting to keep Buck up to date if we can have something that looks like the internal project at Facebook

I also would avoid having to call two different build systems ^^'

It may work for the migration steps though, and we can detach them later

The problem I'd like to focus the discussion on is third-party management. There is nothing I can do to replicate Facebook's solutions for this into the project. I think our options are to re-use CMake's solution or replicate the logic into BUCK.