Initial checkin of chromecast content embedder (cast_shell) and related build scripts.

chromecast/common/cast_paths.cc

+// Copyright 2014 The Chromium Authors. All Rights Reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#include "chromecast/common/cast_paths.h"
+
+#include "base/file_util.h"
+#include "base/files/file_path.h"
+#include "base/path_service.h"
+
+namespace chromecast {
+
+bool PathProvider(int key, base::FilePath* result) {
+  switch (key) {
+    case DIR_CAST_HOME: {
+      base::FilePath home = base::GetHomeDir();
+#if defined(__arm__)

[Ryan Sleevi, 2014/07/01 21:13:55]

Seems strange to use this directly, when we have build/build_config.h designed
for abstracting out the build config macros.

[lcwu1, 2014/07/02 23:30:33]

Changed to use ARCH_CPU_ARMEL defined in build/build_config.h.

+      // When running on the actual device, our data directory is
+      // $HOME for the chrome user.

[Ryan Sleevi, 2014/07/01 21:13:55]

This comment suggests a layering violation (comments should be like code, and
not refer to implementation details of 'higher' layers).

It also should be capitalized if you're talking about Chrome (which you
shouldn't be, outside of src/chrome. This is Chromium)

[lcwu1, 2014/07/02 23:30:32]

This comment is really confusing, isn't it? What we really meant here is that
cast_shell runs on the chromecast device as a 'chrome' user. (That is, we have a
user id called 'chrome'.) And $HOME for the 'chrome' user is set to our /data
directory on the device. I will re-word the comment.

+      *result = home;
+#else
+      // When running a development instance as a regular user, use
+      // a data directory under $HOME (similar to chrome).
+      *result = home.Append(".config/cast_shell");
+#endif
+      return true;
+    }
+  }
+  return false;
+}
+
+void RegisterPathProvider() {
+  PathService::RegisterProvider(PathProvider, PATH_START, PATH_END);
+}
+
+}  // namespace chromecast