From 96e7b2db77552e1b322427125a9044381f778182 Mon Sep 17 00:00:00 2001
From: Anderson Lizardo <anderson.lizardo@openbossa.org>
Date: Mon, 29 Mar 2010 14:24:27 -0400
Subject: QEasingCurve::setCustomType typesystem workaround

Due to bug #201, typesystem signatures that take pointer to function
types are incorrectly expanded.

To workaround this bug, the typesystem signature for
QEasingCurve::setCustomType removal is:

<modify-function signature="setCustomType(double)" remove="all"/>

But for ARM, this same workaround does not work, and has to be:

<modify-function signature="setCustomType(float)" remove="all"/>

This is probably due to how apiextractor/shiboken is incorrectly
expanding the pointer to function signature. To remove setCustomType on
ARM (and thus allow the build to succeed), this commit adds both
signatures.

This is a temporary fix just while bug #201 is not fixed.

Reviewed-by: Lauro Moura <lauro.neto@openbossa.org>
Reviewed-by: Bruno Araujo <bruno.araujo@openbossa.org>
---
 PySide/QtCore/typesystem_core.xml | 4 ++++
 1 file changed, 4 insertions(+)

(limited to 'PySide/QtCore')

diff --git a/PySide/QtCore/typesystem_core.xml b/PySide/QtCore/typesystem_core.xml
index 67d48f79f..1f50621cd 100644
--- a/PySide/QtCore/typesystem_core.xml
+++ b/PySide/QtCore/typesystem_core.xml
@@ -2836,6 +2836,10 @@
 
   <value-type name="QEasingCurve">
     <modify-function signature="customType() const" remove="all"/>
+    <!-- FIXME: setCustomType() actually takes a pointer to function type
+    (EasingFunction), but for some reason apiextractor thinks it is a float/double:
+    http://bugs.openbossa.org/show_bug.cgi?id=201 -->
+    <modify-function signature="setCustomType(float)" remove="all"/>
     <modify-function signature="setCustomType(double)" remove="all"/>
   </value-type>
 
-- 
cgit v1.2.3