[roll] Roll fuchsia [devshell] Use relative symlinks for gen artifacts

And always update compile-commands.json after a gen (including after fx
set).

This makes tooling more resilient to a moving Fuchsia directory, either
due to renames or tools like multifuchsia.

There isn't a great cross-platform way to compute relative paths.
Shelling out to Python works since we have it in our tree. This naive
approach could break with really weird paths that have single quotes in
them, but in practice this shouldn't be an issue.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/971190
Original-Revision: 5b908f6294fb98d77fec60e13f570d369bdb8b62
GitOrigin-RevId: 8a092ebdb5e7142887adce71dac3fe538821f33d
Change-Id: Ie76186b99ffc77145500d4623666b64c85799914
1 file changed
tree: 269233471d7a54238baee339e59789b90461ff8c
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. test_durations
  14. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.