Installation on Gentoo Linux

[pogwizd]

Hi guys,

I am trying to test SavvyCAN, by installing it on my system which is Gentoo Linux, and unfortunetely, I have a problem straight from he beginning.
I have both, Qt5 & Qt6 installed on my system, and here is the error message I got:

me@MyPC ~/Repositories_Git $ git clone https://github.com/collin80/SavvyCAN.git
Klonowanie do „SavvyCAN”...
remote: Enumerating objects: 8175, done.
remote: Counting objects: 100% (1950/1950), done.
remote: Compressing objects: 100% (323/323), done.
remote: Total 8175 (delta 1775), reused 1627 (delta 1625), pack-reused 6225 (from 3)
Pobieranie obiektów: 100% (8175/8175), 13.10 MiB | 20.69 MiB/s, gotowe.
Rozwiązywanie delt: 100% (5823/5823), gotowe.

me@MyPC ~/Repositories_Git $ cd SavvyCAN/

me@MyPC ~/Repositories_Git/SavvyCAN $ qmake5
Info: creating stash file /home/me/Repositories_Git/SavvyCAN/.qmake.stash
Project ERROR: Unknown module(s) in QT: serialbus serialport

me@MyPC ~/Repositories_Git/SavvyCAN $

I tried with both version of Qt, and have the same result.

Thank for any help,

[evermind-zz]

have you installed dev-qt/
qtserialport and dev-qt/
qtserialbus ?

[pogwizd]

Hi,

Indeed, those were not installed, so of course, I did it (qt-6, since qtserialport for qt5 is not available, and qt5 is about to die anyway) -> Thanks evermind-zz

So I started the compilation after that, and ended up with an error during the make process:

me@MyPC ~/Repositories_Git/SavvyCAN $ qmake6
Info: creating stash file /home/krzysztof/Repositories_Git/SavvyCAN/.qmake.stash

me@MyPC ~/Repositories_Git/SavvyCAN $ make
/usr/lib64/qt6/libexec/uic ui/candatagrid.ui -o ui_candatagrid.h
/usr/lib64/qt6/libexec/uic triggerdialog.ui -o ui_triggerdialog.h
/usr/lib64/qt6/libexec/uic ui/canbridgewindow.ui -o ui_canbridgewindow.h
/usr/lib64/qt6/libexec/uic ui/dbcnodeduplicateeditor.ui -o ui_dbcnodeduplicateeditor.h

......

connections/lawicel_serial.cpp: In member function ‘void LAWICELSerial::serialError(QSerialPort::SerialPortError)’:
connections/lawicel_serial.cpp:391:23: error: ‘ParityError’ is not a member of ‘QSerialPort’
  391 |     case QSerialPort::ParityError:
      |                       ^~~~~~~~~~~
connections/lawicel_serial.cpp:394:23: error: ‘FramingError’ is not a member of ‘QSerialPort’
  394 |     case QSerialPort::FramingError:
      |                       ^~~~~~~~~~~~
connections/lawicel_serial.cpp:397:23: error: ‘BreakConditionError’ is not a member of ‘QSerialPort’
  397 |     case QSerialPort::BreakConditionError:
      |                       ^~~~~~~~~~~~~~~~~~~
connections/lawicel_serial.cpp: In member function ‘void LAWICELSerial::readSerialData()’:
connections/lawicel_serial.cpp:489:27: error: invalid conversion from ‘unsigned char’ to ‘const char*’ [-fpermissive]
  489 |         mBuildLine.append(c);
      |                           ^
      |                           |
      |                           unsigned char
/usr/include/qt6/QtCore/qstring.h:950:59: note: initializing argument 1 of ‘QString& QString::append(const char*)’
  950 |     QT_ASCII_CAST_WARN inline QString &append(const char *s)
      |                                               ~~~~~~~~~~~~^
make: *** [Makefile:2764: lawicel_serial.o] Error 1

me@MyPC ~/Repositories_Git/SavvyCAN $

Any ideas?

[evermind-zz]

the qt6 port seems to be not complete. I guess we are stuck on qt5.
But on https://packages.gentoo.org/packages/dev-qt/qtserialport
the version 5.15.17 is still available, maybe it is masked.

Sorry, I can't help more as I have no viable gentoo system running

[pogwizd]

My mistake, I meant qtserialbus is not available anymore for Qt5.

About Qt6, that's what I thought. I guess I will have to wait a little more for some update...

[evermind-zz]

on last thing did you check the QT6WIP branch as this seems to be the ongoing qt6 port.

[pogwizd]

Indeed, Haven't seen the specific branch.
So I manage to get it started, now, I have another problem. It does not see my Peak CAN interface

Maybe a problem with the QtSerialBus.
I am sure the device itself is working correctly, as it is properly detected by my system.