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:
parent
cb4920152e
commit
361c5ea65c
|
@ -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)
|
||||
|
|
Loading…
Reference in New Issue