build sql as a component - this will help ensure there is only one copy

of sqlite getting linked in.

R=rsesek@chromium.org

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

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

1 files changed, 3 insertions, 2 deletions

diff --git a/sql/connection.h b/sql/connection.h
index 5807e36..5446c0c 100644
--- a/sql/connection.h
+++ b/sql/connection.h
@@ -13,6 +13,7 @@
 #include "base/basictypes.h"
 #include "base/memory/ref_counted.h"
 #include "base/time.h"
+#include "sql/sql_export.h"
 
 class FilePath;
 struct sqlite3;
@@ -76,7 +77,7 @@ class Connection;
 // the OnError() callback.
 // The tipical usage is to centralize the code designed to handle database
 // corruption, low-level IO errors or locking violations.
-class ErrorDelegate : public base::RefCounted<ErrorDelegate> {
+class SQL_EXPORT ErrorDelegate : public base::RefCounted<ErrorDelegate> {
  public:
   ErrorDelegate();
 
@@ -99,7 +100,7 @@ class ErrorDelegate : public base::RefCounted<ErrorDelegate> {
   virtual ~ErrorDelegate();
 };
 
-class Connection {
+class SQL_EXPORT Connection {
  private:
   class StatementRef;  // Forward declaration, see real one below.