Try again to commit r8486, which updates the manifest

parsing in the Extension class to also parse out user
script details.

The problem was that extension_protocols.cc appears to
link OK if you don't refer to anything in it, but as
soon as you try to use something defined in it, a bunch
of other symbols it refers to turn up undefined.

To avoid this problem in the future, I stopped compiling
extensions_protocol.cc so that we would realize if we
tried to use it.

Also in this change, I absolutified paths in
ExtensionsService before creating Extension instances.
On Linux, the path that PathService was giving us was
not absolute.

Review URL: http://codereview.chromium.org/18704

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@8576 0039d316-1c4b-4281-b951-d872f2087c98

1 files changed, 0 insertions, 12 deletions

diff --git a/chrome/browser/extensions/extension_protocols.h b/chrome/browser/extensions/extension_protocols.h
index 25f9fda..b76c31c 100644
--- a/chrome/browser/extensions/extension_protocols.h
+++ b/chrome/browser/extensions/extension_protocols.h
@@ -7,18 +7,6 @@
 
 #include "base/file_path.h"
 
-// The URL scheme Chromium extensions are served from.
-extern const char kExtensionURLScheme[];
-
-// The URL scheme Chromium user scripts are served from.
-extern const char kUserScriptURLScheme[];
-
-// Gets a FilePath for a resource inside an extension. |extension_path| is the
-// full path to the extension directory. |resource_path| is the path to the
-// resource from the extension root, including the leading '/'.
-FilePath GetPathForExtensionResource(const FilePath& extension_path,
-                                     const std::string& resource_path);
-
 // Registers support for the extension URL scheme.
 void RegisterExtensionProtocols();