Project

General

Profile

Actions

Pull request #382

closed

Update pinocchio, ndcurves, example-robot-data & python-qt

Added by Guilhem Saurel about 1 year ago. Updated about 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Repository URL:
https://github.com/nim65s/robotpkg
Repository branch:
master

Description

Hi

While here, ros-noetic-ros-comm is now 1.16

Best,
Guilhem

Actions #1

Updated by Anthony Mallet about 1 year ago

For py-pythonqt, did you actually check that the patches are not
required anymore?

Actions #2

Updated by Guilhem Saurel about 1 year ago

Yes, I managed to build py-pythonqt with this setup on Arch, 18.04 and 20.04

Actions #3

Updated by Anthony Mallet about 1 year ago

OK, pushing!

Actions #4

Updated by Guilhem Saurel about 1 year ago

Ok, so it looks like my tests with PythonQt where all super lucky.

for http://robotpkg.openrobots.org/rbulk/robotpkg/graphics/py-pythonqt/py27-pythonqt-3.4.0/Ubuntu-18.04-x86_64/build.html I think here is a workaround in Makefile:
QMAKE_ARGS+= PYTHON_DIR=${PREFIX.python38} ; but I don't know the way to get "python38" right here.

for http://robotpkg.openrobots.org/rbulk/robotpkg/graphics/py-pythonqt/py38-pythonqt-3.4.0/Ubuntu-20.04-x86_64/build.html I can reproduce by installing the libqt5webkit5-dev package, so one workaround would be to remove it from the build VM… But I guess `sed -i 148d extensions/PythonQt_QtAll/PythonQt_QtAll.pro` is more appropriate (and I tested it). Anyways, I opened an upstream issue: https://github.com/MeVisLab/pythonqt/issues/100

Actions #5

Updated by Anthony Mallet about 1 year ago

On Tuesday 14 Mar 2023, at 12:04, Guilhem Saurel wrote:

Ok, so it looks like my tests with PythonQt where all super lucky.

Yup, I'm currently fixing it :)

I think here is a workaround in Makefile: QMAKE_ARGS+=
PYTHON_DIR=${PREFIX.python38} ; but I don't know the way to get
"python38" right here.

Right, I've done that already.

I can reproduce by installing the libqt5webkit5-dev package, so one
workaround would be to remove it from the build VM… But I guess `sed
-i 148d extensions/PythonQt_QtAll/PythonQt_QtAll.pro` is more
appropriate (and I tested it). Anyways, I opened an upstream issue:
https://github.com/MeVisLab/pythonqt/issues/100

It seems that implementation is missing for Qt>=5.11?
For earlier versions there is a dir in generated_cpp_*

But I actually defined the extensions to be built according to the
registered dependencies. I'll push that soon, you will be able to
cross check. Do you need more extensions than those in the listed
dependencies?

Actions #6

Updated by Guilhem Saurel about 1 year ago

  • Status changed from New to Closed

Looks good now, thanks!

Actions

Also available in: Atom PDF