[roll] Roll fuchsia [dso_runner] Initial skeleton Basic core functionality that supports sync and async components that share an address space. This changelist includes: - "synchronous" components - components that get a dedicated thread - "async" components - components that run in a shared Fuchsia Driver Framework thread pool, much like components in driver runner. - Component lifecycle support for start/stop/exit - Unit tests - Simple example (//examples/components/dso) Not included/upcoming in future changes: - Namespacing support for either sync or async components. For now they share the same global namespace/fdio/etc. as the runner process. - Running the components in a separate address space for the runner. This currently isn't too important since all the DSO components share the same address space, but it could become relevant when/if we support multiple "containers". - Integration test - I want to have this but I think it makes sense to land the namespacing support first. - Routing of dso_runner in the component topology Original-Bug: 403545512 Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1481458 Original-Revision: b7546aed9cffe3925cfafd98f5da1f98a964309a GitOrigin-RevId: b2684a1eeea49d81127311015a040924271db5a1 Change-Id: I06fc03929022361ba88aea8859b40f43788763b0
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 in one of the communication channels documented at get involved.
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.