Split mojo_system dylib into public and private

This CL splits the mojo_system dylib into two pieces:
1) A dynamic library suitable for apps to link against
2) A component suitable for linking into mojo_shell

The first dylib doesn't depend on base and simply jumps through a vtable into
an implementation defined by its embedder. The second implements the vtable and
actually contains the code to implement the API.

After this CL, Mojo should basically work in the static build. This CL is a
prerequiste for fixing the Android port.

R=darin@chromium.org
BUG=326918

Review URL: https://codereview.chromium.org/106173003

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

1 files changed, 2 insertions, 2 deletions

diff --git a/mojo/system/message_pipe_endpoint.h b/mojo/system/message_pipe_endpoint.h
index 2939c93..7017596 100644
--- a/mojo/system/message_pipe_endpoint.h
+++ b/mojo/system/message_pipe_endpoint.h
@@ -12,8 +12,8 @@
 #include "base/basictypes.h"
 #include "base/memory/ref_counted.h"
 #include "mojo/public/system/core.h"
-#include "mojo/public/system/system_export.h"
 #include "mojo/system/message_in_transit.h"
+#include "mojo/system/system_impl_export.h"
 
 namespace mojo {
 namespace system {
@@ -30,7 +30,7 @@ class Waiter;
 // |MessagePipeEndpoint| also implements the functionality required by the
 // dispatcher, e.g., to read messages and to wait. Implementations of this class
 // are not thread-safe; instances are protected by |MesssagePipe|'s lock.
-class MOJO_SYSTEM_EXPORT MessagePipeEndpoint {
+class MOJO_SYSTEM_IMPL_EXPORT MessagePipeEndpoint {
  public:
   virtual ~MessagePipeEndpoint() {}