[Bug 458975] Review Request: Pivy - Coin binding for Python

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=458975





--- Comment #10 from Ralf Corsepius <rc040203 at freenet.de>  2009-07-29 10:30:59 EDT ---
(In reply to comment #9)
> So, what the last build was useful for ?
To get rid of qt3.

> here, We need a Coin (3.1.0) build with a Coin-SoQt (understand, SoQt SVN built
> against Coin 3.x.x) and the daily version of Pivy that I'm preparing.
No way, I am not going to ship packages built from daily snapshots, nor package
being cluttered with API/ABI breaking changes.

I don't see any alternative for you patch Pivy to build against SoQt-1.4.1 (the
latest official version of SoQt).

Wrt. Coin3: I am preparing packages for submission for quite a while and plan
to submit them when "they are ready". However, packaging Coin3 has proven to be
problematic and needs further work on my part.

> Does using qt4 makes sense at all while using Coin2 ?
Yes it does. SoQt is supposed to be buildable against Coin2 and Coin3 (actually
it predates Coin3) and to be buildable against Qt3 and Qt4.

However the better question would be: Does using SoQt still make sense at all?

At one point in the past (ca. 1 year ago) SIM released Quarter as successor of
SoQt. As consequence of this SoQt hasn't seen much attention at all. If I'm not
mistaken, there are indications this might have changed recently.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.