install headers from runtime/backend

[swolchok]

Looks like these are all public and we simply missed installing them.

[swolchok]

Stack from ghstack (oldest at bottom):

• Delete tools/cmake/{buck_util,resolve_buck}.py #13588
• Switch from print_exported_headers to CMake's installed headers in scripts/build_apple_frameworks.sh #13559
• ->install headers from runtime/backend #13558
• Add check_for_installed_private_headers_in_cmake_out #13485

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13558

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 2 New Failures, 3 Cancelled Jobs

As of commit 2b5e2b6 with merge base 335de46 ():

NEW FAILURES - The following jobs have failed:

• Build documentation / build (buck2) / Build doc (gh)
  At least one of the pre-conditions you specified did not hold
• pull / android / run-emulator (gh)
  The process '/usr/bin/sh' failed with exit code 255

CANCELLED JOBS - The following jobs were cancelled. Please retry:

• Lint / link-check / lint-urls / linux-job (gh)
• Lint / link-check / lint-xrefs / linux-job (gh)
• Lint / lintrunner / linux-job (gh)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[JacobSzwejbka]

why do we need one for basically every runtime subdir as opposed to just one runtime/?

[swolchok]

I wanted to keep the exclude patterns narrowly scoped.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[meta-cla]

Hi @swolchok!

Thank you for your pull request.

We require contributors to sign our Contributor License Agreement, and yours needs attention.

You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at cla@meta.com. Thanks!

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.

[github-actions]

Looks like this PR hasn't been updated in a while so we're going to go ahead and mark this as Stale.
Feel free to remove the Stale label if you feel this was a mistake.
If you are unable to remove the Stale label please contact a maintainer in order to do so.
If you want the bot to never mark this PR stale again, add the no-stale label.
Stale pull requests will automatically be closed after 30 days of inactivity.