Fix exports in v4 binary
authorSimon Hausmann <simon.hausmann@digia.com>
Thu, 7 Feb 2013 15:14:44 +0000 (16:14 +0100)
committerLars Knoll <lars.knoll@digia.com>
Sat, 9 Feb 2013 09:38:10 +0000 (10:38 +0100)
Don't use the export macro on internal debug classes.

Change-Id: Id2f8069cc8b6703a3fafd3058524d46252eb57f8
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
tools/v4/main.cpp

index 0d215b9..25ebc5c 100644 (file)
@@ -72,7 +72,7 @@ namespace builtins {
 
 using namespace QQmlJS::VM;
 
-struct Q_V4_EXPORT Print: FunctionObject
+struct Print: FunctionObject
 {
     Print(ExecutionContext *scope): FunctionObject(scope) {
         name = scope->engine->newString("print");
@@ -91,7 +91,7 @@ struct Q_V4_EXPORT Print: FunctionObject
     }
 };
 
-struct Q_V4_EXPORT TestHarnessError: FunctionObject
+struct TestHarnessError: FunctionObject
 {
     TestHarnessError(ExecutionContext *scope, bool &errorInTestHarness): FunctionObject(scope), errorOccurred(errorInTestHarness) {
         name = scope->engine->newString("$ERROR");
@@ -114,7 +114,7 @@ struct Q_V4_EXPORT TestHarnessError: FunctionObject
     bool &errorOccurred;
 };
 
-struct Q_V4_EXPORT GC: public FunctionObject
+struct GC: public FunctionObject
 {
     GC(ExecutionContext* scope)
         : FunctionObject(scope)