It looks like you're new here. If you want to get involved, click one of these buttons!
Hi Matthias,
We tried to build up klayout v0.23.1 on an old platform, and it failed with the following error messages, although the qt4 version(4.4.3) is too old to be supported, we still hope to setup new version klayout on this platform, could you help us to solve this problem? thanks.
This platform could be used to build up klayout v0.22.9 .
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc:602: error: invalid use of undefined type `struct QHeaderView'
/usr/lib/qt4/include/QtGui/qtreeview.h:52: error: forward declaration of `struct QHeaderView'
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc:603: error: invalid use of undefined type `struct QHeaderView'
/usr/lib/qt4/include/QtGui/qtreeview.h:52: error: forward declaration of `struct QHeaderView'
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc:606: error: no matching function for call to `lay::SearchReplaceDialog::connect(QHeaderView*, const char[32], lay::SearchReplaceDialog* const, const char[35])'
/usr/lib/qt4/include/QtCore/qobject.h:197: note: candidates are: static bool QObject::connect(const QObject*, const char*, const QObject*, const char*, Qt::ConnectionType)
/usr/lib/qt4/include/QtCore/qobject.h:303: note: bool QObject::connect(const QObject*, const char*, const char*, Qt::ConnectionType) const
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc: In member function `void lay::SearchReplaceDialog::header_columns_changed(int, int)':
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc:1427: error: invalid use of undefined type `struct QHeaderView'
/usr/lib/qt4/include/QtGui/qtreeview.h:52: error: forward declaration of `struct QHeaderView'
/source/klayout-0.23.1/src/laySearchReplaceDialog.cc:1427: error: incomplete type `QHeaderView' used in nested name specifier
chhung
Comments
Hi,
that can be fixed with a
somewhere at the beginning of laySearchAndReplaceDialog.cc.
I am sorry about that, but I can't test all possible combinations of gcc/Qt/Ruby ...
I'll include that patch in the source.
Thanks for the hint,
Matthias
Hi Matthas,
This issue has been fixed with your solution, really thanks for your kindly support.
Best Regards,
chhung