qt with glut on windows 10

[gtx]

Main.cpp

#include "mainwindow.h"
#include <QApplication>
#include <GL/glut.h>
 
int main(int argc, char *argv[])
{
    glutInit(&argc,argv);
    QApplication a(argc, argv);
    MainWindow w;
    w.show();
    return a.exec();
}

#include "mainwindow.h"
#include <QApplication>
#include <GL/glut.h>

int main(int argc, char *argv[])
{
    glutInit(&argc,argv);
    QApplication a(argc, argv);
    MainWindow w;
    w.show();
    return a.exec();
}

To copy to clipboard, switch view to plain text mode 

also when i place the line debugger on the gluinit
it seems it something like a segmentation fault my guess cause glut isnt configured correctly, it runs for 2-3 secs then it crashes
segfault.jpg

[anda_skoa]

Don't really have an idea on the crash, but you should not be using QGLWidget if you are on Qt5.

Use QOpenGLWidget instead.

Cheers,
_

[gtx]

Yea i've heard of this however the only youtube video tutorial i've found the seemed complete and i could understand was using qglwidget. I don't think qglwidget is the problem because it was working before i added the glut.

[d_stranz]

Where is your GLWidget being constructed? Did you add it in Qt Designer (and so it is being constructed via setupUi())?

You probably need to at least set the viewport size in the resizeGL() method:

void GLWidget::resizeGL( int w, int h )
{
    glViewport( 0, 0, (GLint)w, (GLint)h );
}

void GLWidget::resizeGL( int w, int h )
{
    glViewport( 0, 0, (GLint)w, (GLint)h );
}

To copy to clipboard, switch view to plain text mode 

You could simply your test case further by eliminating the MainWindow:

#include "glwidget.h"
#include <QApplication>
#include <GL/glut.h>
 
int main(int argc, char *argv[])
{
     glutInit(&argc,argv);
     QApplication a(argc, argv);
     GLWidget w;
     w.show();
     return a.exec();
}

#include "glwidget.h"
#include <QApplication>
#include <GL/glut.h>
     
int main(int argc, char *argv[])
{
     glutInit(&argc,argv);
     QApplication a(argc, argv);
     GLWidget w;
     w.show();
     return a.exec();
}

To copy to clipboard, switch view to plain text mode 

This makes the GLWidget your top-level application widget and eliminates MainWindow as the cause of any errors.

[gtx]

Ok i am trying that debuggin technique and I get "call to constructor of 'GLWidget is ambigous call to overloaded function could be GL::GLWidget(QWidget*)' or GL::GLWidget(void) while trying to match argument list '0' i also include the glwidgets designer view


glwidgetanonymous.jpgqtdesign.jpg

[d_stranz]

You probably need to change the signature for the GLWidget constructor to add a default value for the "parent" argument:

// glwidget.h
 
class GLWidget : public QGLWidget
{
    Q_OBJECT
 
public:
    GLWidget( QWidget * parent = 0 );  // default value for parent
 
//...
}

// glwidget.h

class GLWidget : public QGLWidget
{
    Q_OBJECT

public:
    GLWidget( QWidget * parent = 0 );  // default value for parent

//...
}

To copy to clipboard, switch view to plain text mode 

[gtx]

it did have that in glwidget.h with the word explicit at the beginning but no Q_OBJECT, i tried adding Q_OBJECT but then i get build time errors so i removed it again

[anda_skoa]

Yea i've heard of this however the only youtube video tutorial i've found the seemed complete and i could understand was using qglwidget. I don't think qglwidget is the problem because it was working before i added the glut.

I also don't think it is the cause of the problem but why use obsolete technology when the replacement is virtually identical in API?

it did have that in glwidget.h with the word explicit at the beginning but no Q_OBJECT, i tried adding Q_OBJECT but then i get build time errors so i removed it again

It should't matter unless you define your own slots, signals or properties.

However, if you get build errors when adding the Q_OBJECT marker the usual fix is to re-run qmake.

Cheers,
_

[gtx]

ok ive reran qmake and the q_object build errors went away but the program is still crashing after a few secs in runtime urgh.

[d_stranz]

the program is still crashing after a few secs in runtime

Then you really need to learn how to use the debugger and run your program in debug mode. When the program crashes, you look at the call stack and that will tell you the complete sequence of calls made by your program from the beginning up to the point where the crash occurs.

Just keep in mind that -where- the crash occurs might not be the actual cause that leads to the crash. For example, a memory error earlier in the program may not actually cause a problem until the code that tries to use the corrupted memory gets executed. You need to look at not only where the crash happens, but what the program is trying to do when it crashes.

Once you have established where the crash happens, if you don't understand why then report back and maybe someone here can provide some help. Just don't post screen shots of the call stack, copy and paste the text instead.

[gtx]

I have added that line to glwidget.h but i'm still getting call to constructor GLWidget w; is ambigous

main.cpp

GLWidget w;
    w.show();

GLWidget w;
    w.show();

To copy to clipboard, switch view to plain text mode 

on the GLWidget w; line

[d_stranz]

Your GLWidget class shows two constructors in its header:

GLWidget();
 
// and
 
explicit GLWidget( QWidget * parent = 0 );

GLWidget();

// and

explicit GLWidget( QWidget * parent = 0 );

To copy to clipboard, switch view to plain text mode 

These two are indistinguishable to the compiler when used as you are doing ("GLWidget w;"). Get rid of the first constructor (GLWidget()) and the warning will go away.