eepe 405 does not compile on Fedora 20 64-bit

How to use eePe
Post Reply
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

Attempting to compile eepe 405 from SVN, I get:

[scldad@mustang src]$ make
/usr/lib64/qt4/bin/uic modeledit.ui -o ui_modeledit.h
/usr/lib64/qt4/bin/uic generaledit.ui -o ui_generaledit.h
/usr/lib64/qt4/bin/uic mixerdialog.ui -o ui_mixerdialog.h
/usr/lib64/qt4/bin/uic burnconfigdialog.ui -o ui_burnconfigdialog.h
/usr/lib64/qt4/bin/uic avroutputdialog.ui -o ui_avroutputdialog.h
/usr/lib64/qt4/bin/uic simulatordialog.ui -o ui_simulatordialog.h
/usr/lib64/qt4/bin/uic donatorsdialog.ui -o ui_donatorsdialog.h
/usr/lib64/qt4/bin/uic printdialog.ui -o ui_printdialog.h
/usr/lib64/qt4/bin/uic preferencesdialog.ui -o ui_preferencesdialog.h
/usr/lib64/qt4/bin/uic downloaddialog.ui -o ui_downloaddialog.h
/usr/lib64/qt4/bin/uic customizesplashdialog.ui -o ui_customizesplashdialog.h
/usr/lib64/qt4/bin/uic serialdialog.ui -o ui_serialdialog.h
/usr/lib64/qt4/bin/uic telemetryDialog.ui -o ui_telemetryDialog.h
/usr/lib64/qt4/bin/uic SimSerialDialog.ui -o ui_SimSerialDialog.h
/usr/lib64/qt4/bin/uic reviewOutput.ui -o ui_reviewOutput.h
g++ -c -pipe -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fstack-protector-strong --param=ssp-buffer-size=4 -grecord-gcc-switches -m64 -mtune=generic -O2 -Wall -W -D_REENTRANT -DQESP_NO_UDEV -D__linux__ -DQT_NO_DEBUG -DQT_XML_LIB -DQT_GUI_LIB -DQT_NETWORK_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/lib64/qt4/mkspecs/linux-g++ -I. -I/usr/include/QtCore -I/usr/include/QtNetwork -I/usr/include/QtGui -I/usr/include/QtXml -I/usr/include -I. -I. -I. -o qextserialport.o qextserialport.cpp
In file included from qextserialport.cpp:1011:0:
moc_qextserialport.cpp:15:34: fatal error: private/qucomextra_p.h: No such file or directory
#include <private/qucomextra_p.h>

QT version is 4.8.6

User avatar
MikeB
9x Developer
Posts: 17990
Joined: Tue Dec 27, 2011 1:24 pm
Country: -
Location: Poole, Dorset, UK

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by MikeB »

moc_qextserialport.cpp is generated by the compile process. I'm not sure what the file "private/qucomextra_p.h" is. On my wondows compile my moc_qextserialport.cpp doesn't have this as an include. (Qt is 4.7.3).

Perhaps you could post the moc_qextserialport.cpp file you have.

Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

[scldad@mustang src]$ cat moc_qextserialport.cpp
/****************************************************************************
** QextSerialPort meta object code from reading C++ file 'qextserialport.h'
**
** Created: Wed Jan 21 16:53:09 2015
** by: The Qt MOC ($Id: qt/moc_yacc.cpp 3.3.8 edited Feb 2 14:59 $)
**
** WARNING! All changes made in this file will be lost!
*****************************************************************************/

#undef QT_NO_COMPAT
#include "qextserialport.h"
#include <qmetaobject.h>
#include <qapplication.h>

#include <private/qucomextra_p.h>
#if !defined(Q_MOC_OUTPUT_REVISION) || (Q_MOC_OUTPUT_REVISION != 26)
#error "This file was generated using the moc from 3.3.8b. It"
#error "cannot be used with the include files from this version of Qt."
#error "(The moc has changed too much.)"
#endif

#include <qvariant.h>
const char *QextSerialPort::className() const
{
return "QextSerialPort";
}

QMetaObject *QextSerialPort::metaObj = 0;
static QMetaObjectCleanUp cleanUp_QextSerialPort( "QextSerialPort", &QextSerialPort::staticMetaObject );

#ifndef QT_NO_TRANSLATION
QString QextSerialPort::tr( const char *s, const char *c )
{
if ( qApp )
return qApp->translate( "QextSerialPort", s, c, QApplication::DefaultCodec );
else
return QString::fromLatin1( s );
}
#ifndef QT_NO_TRANSLATION_UTF8
QString QextSerialPort::trUtf8( const char *s, const char *c )
{
if ( qApp )
return qApp->translate( "QextSerialPort", s, c, QApplication::UnicodeUTF8 );
else
return QString::fromUtf8( s );
}
#endif // QT_NO_TRANSLATION_UTF8

#endif // QT_NO_TRANSLATION

QMetaObject* QextSerialPort::staticMetaObject()
{
if ( metaObj )
return metaObj;
QMetaObject* parentObject = QIODevice::staticMetaObject();
#ifndef QT_NO_PROPERTIES
static const QMetaEnum::Item enum_0[] = {
{ "Polling", (int) QextSerialPort::Polling },
{ "EventDriven", (int) QextSerialPort::EventDriven }
};
static const QMetaEnum enum_tbl[] = {
{ "QueryMode", 2, enum_0, FALSE }
};
#endif // QT_NO_PROPERTIES
#ifndef QT_NO_PROPERTIES
static const QMetaProperty props_tbl[2] = {
{ "QString","portName", 0x3000001, &QextSerialPort::metaObj, 0, -1 },
{ "QueryMode","queryMode", 0x0005, &QextSerialPort::metaObj, &enum_tbl[0], -1 }
};
#endif // QT_NO_PROPERTIES
metaObj = QMetaObject::new_metaobject(
"QextSerialPort", parentObject,
0, 0,
0, 0,
#ifndef QT_NO_PROPERTIES
props_tbl, 2,
enum_tbl, 1,
#endif // QT_NO_PROPERTIES
0, 0 );
cleanUp_QextSerialPort.setMetaObject( metaObj );
return metaObj;
}

void* QextSerialPort::qt_cast( const char* clname )
{
if ( !qstrcmp( clname, "QextSerialPort" ) )
return this;
return QIODevice::qt_cast( clname );
}

bool QextSerialPort::qt_invoke( int _id, QUObject* _o )
{
return QIODevice::qt_invoke(_id,_o);
}

bool QextSerialPort::qt_emit( int _id, QUObject* _o )
{
return QIODevice::qt_emit(_id,_o);
}
#ifndef QT_NO_PROPERTIES

bool QextSerialPort::qt_property( int id, int f, QVariant* v)
{
switch ( id - staticMetaObject()->propertyOffset() ) {
case 0: switch( f ) {
case 1: *v = QVariant( this->portName() ); break;
case 3: case 4: case 5: break;
default: return FALSE;
} break;
case 1: switch( f ) {
case 1: *v = QVariant( (int)this->queryMode() ); break;
case 3: case 4: case 5: break;
default: return FALSE;
} break;
default:
return QIODevice::qt_property( id, f, v );
}
return TRUE;
}

bool QextSerialPort::qt_static_property( QObject* , int , int , QVariant* ){ return FALSE; }
#endif // QT_NO_PROPERTIES
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

Just realised that the moc version used to generate moc_qextserialport.cpp was old.
I deleted the generated file and tried again.
This time it progressed much further but then had other, quite different errors.
I am off on leave just now but will follow up when I get back next week.
User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by rperkins »

do you also have qt3 headers installed ?
http://www.linuxquestions.org/questions ... t4-775969/

I have successfully compiled eepe svn 405 on Ubuntu 14.04.1 64 bit

sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

Sorry for the delay in getting back.

I now find that the latest code I can get is V 402 and that compiles with Fedora 21 without any problems.

Forgive the elderly moment but how can one download raw source versions later than 402?
User avatar
MikeB
9x Developer
Posts: 17990
Joined: Tue Dec 27, 2011 1:24 pm
Country: -
Location: Poole, Dorset, UK

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by MikeB »

The source files for r405 are on googlecode. How did you get r402? You should be able to get the r405 source files in the same way.
If you use svn, you may need to specify r405 when getting the files.

Mike.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by rperkins »

from the top of my head. Try 'svn up'
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

If I use svn, I get a .deb package that I don't know how to use on Fedora.

If I use wget -r eepe.googlecode.com/svn/trunk/src, the directory says 405 but the stamp file (and therefore the compiled Help) says 402.
User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by rperkins »

yes the svn includes .debs that shouldnt there imho, but it also includes all the src files. I dont know about using wget. Mike does 'Do his own thing' regularly so he would be the one to say.
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

You are correct. The svn checkout does give me the src directory. Not sure why I didn't see it before. I guess I must have been distracted by the initial .deb files.
However, even though svn says "version 405 checked out", the stamp file still says 402 so the svn result looks to be the same as wget (as one would hope).
Hopefully this means that it is only the stamp file that is out of whack.

BTW, I am happy to contribute 64-bit Fedora executables for eepe, avrdude etc.
User avatar
rperkins
Posts: 1422
Joined: Sun Jan 08, 2012 12:51 pm
Country: -

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by rperkins »

Again off the top of my head( i am away from my home computer).
'svn info' may give the rev number.
My recollection is the debs related to eepe might need to have their dependancies checked, but i havent used the debs for awhile. I just use the svn
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

Spot on!
svn info says V 405 28/4/2014 but the stamp file says V 402 21/4/2014.
The status now is "V405 does compile on Fedora 21";-)

(If we just ignore the .debs, they might go away)

Cheers and thanks,
Stephen
sdavies
Posts: 114
Joined: Wed Jan 21, 2015 6:46 am
Country: Australia
Location: Adelaide SA

Re: eepe 405 does not compile on Fedora 20 64-bit

Post by sdavies »

Just successfully compiled and ran eepskye from the same svn checkout but don't (yet) have a Pro Tx to test with.

Post Reply

Return to “eePe”