Google Git
Sign in
fuchsia/integration/5bf5e2baadacc6eaa61a93b363dec5162b192901
commit
5bf5e2baadacc6eaa61a93b363dec5162b192901
[log]
author
Jeff Bailey <jbailey@fuchsia.infra.roller.raspberryginger.com>
Tue Sep 19 05:45:18 2023 +0000
committer
Copybara-Service <copybara-worker@google.com>
Mon Sep 18 22:47:48 2023 -0700
tree
10ece20a0b325ce811c3a2da3540d7426dcb62d1
parent
cf1a54519a93162a78a09795e98643b16a730c84 [diff]
[roll] Roll llvm-project/libc [libc] Specify path for making include/ subdirs (#66589)

When doing a clean build from vscode, it makes the subdirectories in the
source tree rather than in the build folder. Elsehwere in LLVM, they
prefix the MAKE_DIRECTORY calls, so this appears to be the correct
approach.

GitOrigin-RevId: aba137eeeec28e06a43d7afac45fe46ccd9e94a8
Original-Revision: 5caea5b26647285092fd85c2dd8ae43bbe0ec4bf
Change-Id: If5f9295a2191af81ef5326855e65106a800477f1
1 file changed
tree: 10ece20a0b325ce811c3a2da3540d7426dcb62d1
  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.