Move fileapi into its own component

webkit/fileapi/fileapi_export.h

Index: webkit/fileapi/fileapi_export.h
diff --git a/webkit/fileapi/fileapi_export.h b/webkit/fileapi/fileapi_export.h
new file mode 100644
index 0000000000000000000000000000000000000000..85be9e3ef8dd0aa2e1c1d3ae2af9124a06fb2d87
--- /dev/null
+++ b/webkit/fileapi/fileapi_export.h
@@ -0,0 +1,35 @@
+// Copyright (c) 2012 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.
+
+#ifndef WEBKIT_FILEAPI_FILEAPI_EXPORT_H_
+#define WEBKIT_FILEAPI_FILEAPI_EXPORT_H_
+#pragma once
+
+#if defined(COMPONENT_BUILD)
+#if defined(WIN32)
+
+#if defined(FILEAPI_IMPLEMENTATION)

[ericu, 2012/05/29 17:59:49]

What's the difference between FILEAPI_EXPORT and FILEAPI_EXPORT_PRIVATE?  Unless
I'm misreading this file, I don't see any in the definitions.  If there's going
to be a difference later, is there any automated way of catching it if we use
the wrong one?

[benwells, 2012/05/29 23:46:52]

There is no difference. Apparently this is a documentation kind of thing, which
means there is no way of knowing if it is right or not which is less than
desirable.

This pattern is used elsewhere (e.g. BASE_EXPORT), I was told on irc it's the
correct thing to do.

+#define FILEAPI_EXPORT __declspec(dllexport)
+#define FILEAPI_EXPORT_PRIVATE __declspec(dllexport)
+#else
+#define FILEAPI_EXPORT __declspec(dllimport)
+#define FILEAPI_EXPORT_PRIVATE __declspec(dllimport)
+#endif  // defined(FILEAPI_IMPLEMENTATION)
+
+#else // defined(WIN32)
+#if defined(FILEAPI_IMPLEMENTATION)
+#define FILEAPI_EXPORT __attribute__((visibility("default")))
+#define FILEAPI_EXPORT_PRIVATE __attribute__((visibility("default")))
+#else
+#define FILEAPI_EXPORT
+#define FILEAPI_EXPORT_PRIVATE
+#endif
+#endif
+
+#else // defined(COMPONENT_BUILD)
+#define FILEAPI_EXPORT
+#define FILEAPI_EXPORT_PRIVATE
+#endif
+
+#endif  // WEBKIT_FILEAPI_FILEAPI_EXPORT_H_