Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to qt5 before December 2015 #56

Closed
scpeters opened this issue Jun 16, 2015 · 20 comments
Closed

Migrate to qt5 before December 2015 #56

scpeters opened this issue Jun 16, 2015 · 20 comments

Comments

@scpeters
Copy link

From announcement of qt 4.8.7:

"Qt 4.8.7 is planned to be the last patch release of the Qt 4 series. Standard support is available until December 2015, after which extended support will be available. We recommend all active projects to migrate to Qt 5, as new operating systems and compilers with Qt 4.8 will not be supported."

@scpeters
Copy link
Author

We need to do the same for gazebo. We will post updates on our progress.

@dirk-thomas
Copy link
Contributor

The problem is that qt_gui_core is working with both PyQt as well as PySide but PySide is not available for Qt5 atm.

@scpeters
Copy link
Author

Hm... looks like http://www.pyside.org is down right now

@esteve
Copy link

esteve commented Jun 16, 2015

PySide moved to the http://qt.io website:

https://wiki.qt.io/Category:LanguageBindings::PySide

Here's the roadmap, but I don't know how much of PySide has been ported to Qt5:

https://wiki.qt.io/PySide_Roadmap

@scpeters
Copy link
Author

Looks like the last commit was 11 months ago

@dirk-thomas
Copy link
Contributor

There is hope: pyside/pyside-setup@e7f0215

@dirk-thomas
Copy link
Contributor

There is currently a lot of activity in the PSide repos with the suffix 2 (https://github.com/PySide) which is very promising.

@ShawnSchaerer
Copy link

Is anybody actively working on this? If not I will.

@dirk-thomas
Copy link
Contributor

No, currently nobody works on this. If you want to look into it the order would be:

The most problematic part will likely be the PySide bindings.

@ShawnSchaerer
Copy link

I will start to look at it

@ahundt
Copy link

ahundt commented Dec 30, 2015

Any luck with this? I'm using code that depends on qt5 and I'm on a new project that uses ROS so the dependency conflict is an issue for me.

@ShawnSchaerer
Copy link

I have not looked in depth at it. it will be a while. Been focusing on
the URDF v2 / new robot format at the moment :)

On Wed, Dec 30, 2015 at 4:20 PM, Andrew Hundt notifications@github.com
wrote:

Any luck with this? I'm using code that depends on qt5 and I'm on a new
project that uses ROS so the dependency conflict is an issue for me.


Reply to this email directly or view it on GitHub
#56 (comment)
.

@ahundt
Copy link

ahundt commented Dec 30, 2015

Ok thanks, the information is helpful so I can plan accordingly!

@dirk-thomas
Copy link
Contributor

@ahundt What is the conflict you are facing? Afaik Qt 4 and 5 is side-by-side installable so it should be possible to run two applications with different major versions of Qt at the same time.

@ahundt
Copy link

ahundt commented Jan 5, 2016

@dirk-thomas homebrew doesn't seem to encourage side-by-side installation, and I can't use other dependencies that need (or work better with) qt5 when this one is using qt4.

@scpeters
Copy link
Author

scpeters commented Jan 5, 2016

Here's the source of the homebrew troubles:

Qt5 can still be installed in a separate prefix (keg-only), so as a workaround, it could still be usable if you add that prefix to the appropriate environment variables.

@ahundt
Copy link

ahundt commented Jan 26, 2016

Even if both are installed on one machine, am I correct in thinking a single application cannot link to both qt5 and qt4 safely?

@dirk-thomas
Copy link
Contributor

Yes, I am pretty sure a single application can only use a single version.

@nicolaerosia
Copy link

@dirk-thomas
Copy link
Contributor

Yes, the decision has been made that it will happen for Kinetic. See ros-infrastructure/rep#112.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants