Move examples + tests to single-step CMake build #8274
Labels
module: build/install
Issues related to the cmake and buck2 builds, and to installing ExecuTorch
module: user experience
Issues related to reducing friction for users
triaged
This issue has been looked at a team member, and triaged and prioritized into an appropriate module
Milestone
🚀 The feature, motivation and pitch
Currently, many examples and tests are built using a two-step process, where the executorch core is built and then "installed" into the build directory used by the example or test. This ends up being quite fragile as iterative rebuilds often don't work nicely and it's very easy for it not work when the initial build isn't configured exactly right for the test or example. It should be significantly more robust and "just work" if we either migrate all of these targets to include executorch via add_subdirectory (it should be possible to include the parent directory, so long as there is no cycle. Might need to play around with relative vs absolute paths). The other option is to include them from the main build/CMakeLists under the main CMakeLists. It may make sense to do this for tests and keep examples using add_subdirectory, but could be discussed more.
Alternatives
No response
Additional context
No response
RFC (Optional)
No response
cc @larryliu0820 @mergennachin @byjlw
The text was updated successfully, but these errors were encountered: