| commit | cbb67325aeee3d6731bd210cf5079297c4a21363 | [log] [tgz] |
|---|---|---|
| author | Megan Batty <mgnb@fuchsia.infra.roller.google.com> | Wed Nov 22 22:29:05 2023 +0000 |
| committer | Copybara-Service <copybara-worker@google.com> | Wed Nov 22 14:30:09 2023 -0800 |
| tree | 6334168984804693708702a6cc2f3b3637aadf5d | |
| parent | 958fad0347f870f8fe37296b30f4241072f13b38 [diff] |
[roll] Roll fuchsia [ffx][sdk] Don't resolve symlinks in sdk search When run in google3 or otherwise through symlinks (such as in the bazel sdk built in-tree), if we're searching for the SDK from the executable's location, we should not resolve symlinks which means we can't use `std::env::current_exe()` (which resolves them on linux but not other platforms) or `Path::canonicalize()` (which always resolves symlinks). In google3 this is especially problematic because the actual location of the binary is in a CAS and not adjacent to the SDK at all, so it just fails. Instead, use argv[0] joined to the current working directory and search from there. Original-Fixed: b/312491133 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/950018 Original-Revision: 8b0498033261194094a625b9f43f7b182d4dfd76 GitOrigin-RevId: 6dde325a993f306836f7a08d175240bc1fa64c4b Change-Id: I3c24bd407405d0974689bb5a88f5cbdc04ef5475
This repository contains Fuchsia's Global Integration manifest files.
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.
First install Jiri.
Next run:
$ jiri init $ jiri import minimal https://fuchsia.googlesource.com/integration $ jiri update
Third party projects should have their own subdirectory in ./third_party.