Clean up EDK layering

As a precursor to moving SDK thunks around and rewiring them, this
fixes some of the weird layering within //mojo/edk.

Namely this introduces a new //mojo/edk target to subsume the role
of //mojo/edk/system (aliased for now to avoid churn), and splits out
a source_set (//mojo/edk:core) for the bulk of the EDK impl with no
linkage dependencies on //mojo/public.

A follow-up patch (https://crrev.com/c/963548) will get rid of the
alias targets.

Bug: 822034
Change-Id: I6b45ce6e8bb9b3a5392ae8e5cdfb61bbc4761769
Reviewed-on: https://chromium-review.googlesource.com/963766
Commit-Queue: Ken Rockot <rockot@chromium.org>
Reviewed-by: Jay Civelli <jcivelli@chromium.org>
Cr-Commit-Position: refs/heads/master@{#543528}

CrOS-Libchrome-Original-Commit: d86d1e44f344aee3c6a253b359f1ae99a92a0586
20 files changed
tree: f43fefc07adcb0bf9307345053244ccb1c81c564
  1. base/
  2. build/
  3. components/
  4. dbus/
  5. device/
  6. ipc/
  7. mojo/
  8. testing/
  9. third_party/
  10. ui/