We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
On my system (Ubuntu 10.10 amd64 + gcc 4.5.2), the build fails at QMAVIScript.h as follows:
make -C/tmp/buildd/mmdai-1.7.3.2+git20110605/debian/plugins/QMAVIManagerPlugin make[2]: Entering directory `/tmp/buildd/mmdai-1.7.3.2+git20110605/debian/plugins/QMAVIManagerPlugin' g++ -c -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_NO_DEBUG -DQT_PLUGIN -DQT_GUI_LIB -DQT_CORE_LIB -DQT_SHARED -I/usr/share/qt4/mkspecs/linux-g++ -I../../../QMA/plugins/QMAVIManagerPlugin -I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4 -I../../../MMDME/include -I../../../MMDAI/include -I/usr/include -I/usr/local/include -I/usr/include/bullet -I/usr/local/include/bullet -I../../../QMA -I. -I../../../QMA/plugins/QMAVIManagerPlugin -I. -o QMAVIManagerPlugin.o ../../../QMA/plugins/QMAVIManagerPlugin/QMAVIManagerPlugin.cc In file included from ../../../QMA/plugins/QMAVIManagerPlugin/QMAVIManagerPlugin.h:50:0, from ../../../QMA/plugins/QMAVIManagerPlugin/QMAVIManagerPlugin.cc:39: ../../../QMA/plugins/QMAVIManagerPlugin/QMAVIScript.h:84:37: error: expected ';' before '(' token
It seems that uint32_t is undefined in QMAVIScript.h , so I think that #include <MMDME/Common.h> in QMAVIScript.cc should be moved to QMAVIScript.h .
#include <MMDME/Common.h>
The text was updated successfully, but these errors were encountered:
No branches or pull requests
On my system (Ubuntu 10.10 amd64 + gcc 4.5.2), the build fails at QMAVIScript.h as follows:
It seems that uint32_t is undefined in QMAVIScript.h , so I think that
#include <MMDME/Common.h>
in QMAVIScript.cc should be moved to QMAVIScript.h .The text was updated successfully, but these errors were encountered: