Fix exports in v4 binary

Don't use the export macro on internal debug classes.

Change-Id: Id2f8069cc8b6703a3fafd3058524d46252eb57f8
Reviewed-by: Lars Knoll <lars.knoll@digia.com>
This commit is contained in:
Simon Hausmann 2013-02-07 16:14:44 +01:00 committed by Lars Knoll
parent cb4920152e
commit 361c5ea65c
1 changed files with 3 additions and 3 deletions

View File

@ -72,7 +72,7 @@ namespace builtins {
using namespace QQmlJS::VM; using namespace QQmlJS::VM;
struct Q_V4_EXPORT Print: FunctionObject struct Print: FunctionObject
{ {
Print(ExecutionContext *scope): FunctionObject(scope) { Print(ExecutionContext *scope): FunctionObject(scope) {
name = scope->engine->newString("print"); 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) { TestHarnessError(ExecutionContext *scope, bool &errorInTestHarness): FunctionObject(scope), errorOccurred(errorInTestHarness) {
name = scope->engine->newString("$ERROR"); name = scope->engine->newString("$ERROR");
@ -114,7 +114,7 @@ struct Q_V4_EXPORT TestHarnessError: FunctionObject
bool &errorOccurred; bool &errorOccurred;
}; };
struct Q_V4_EXPORT GC: public FunctionObject struct GC: public FunctionObject
{ {
GC(ExecutionContext* scope) GC(ExecutionContext* scope)
: FunctionObject(scope) : FunctionObject(scope)