Is there a process for integrating a preexisting repository with fbcode_builder?

[mszabo-wikia]

Hello,

fbcode_builder has become the de facto standard for most of Meta's C++ OSS projects since it greatly simplifies the task of resolving and building their dependency chain that commonly involves compiling several other projects from source.

It would be great if this tooling could encompass some additional projects too, such as mcrouter, which currently uses a legacy autotools-based build system with an additional set of custom scripts responsible for installing and compiling dependencies. These scripts regularly become outdated when dependency requirements change, which then leads to unnecessary drudgery for repo maintainers and end users alike, as the scripts must be updated by hand. fbcode_builder would help obviate most problems like this.

In #2268 and related tasks, I've attempted to set up the required scaffolding for mcrouter. However, it seems additional work is needed to actually sync fbcode_builder automatically into its Git mirror in the same way it is done for other projects. #2282 adds some additional configuration that might help with this, but it has unfortunately been stalled for a few months now.

Given this, I would like to clarify the following:

• What is the process for integrating a new project with fbcode_builder?
• Is there a different, preferred, approach instead? A potential alternative I could think of would be to open-source the relevant buck2 build files as already being done for folly and a few other projects, and let the community make alterations as needed to make them function outside of fbcode, but this might still ultimately benefit from fbcode_builder for dependency management purposes.

Thanks in advance.