Dear Rooters,
I am using Win2k, BNL QtRoot 5.18, Qt 4.4.0 and MSVS2005 as IDE.
When I want to use a TQtWidget I get this unresolved symbol message:
But the libGQt.lib is included. If I don’t use libGQt.lib I get one more error message:
My code is symply
int main(int argc, char **argv)
{
TQtWidget MyWidget;
TGraph myGraph;
QWidget myWidget;
return 0;
}
TGraph and QWidget don’t produce errors.
For me it looks as if libGQt.lib does not define TQtWidget completely. But I am more or less a beginner in C++.
Can someone solve this problem?
Thanks in advance
Axel
gserver|kserver|pserver):[[user][]@]host[:[port]]/path
Sorry, I am wondering if RootForum did no like the file “sh” extension. I added “.txt” and re-uploaded it. Please, download, remove the “.txt” extension then execute.
[/quote] It is up to you. However, I do not think it is wise to wait at this point as soon as QtRoot for ROOT 5.20/0 + Qt 4.4 on Win32 is concern. There are a few Win32/VC++ nasty features you should take in account and learn anyway planning your activities. Here you are, with VC++ all libraries your application is going to use must be compiled consistently. That means, for example, ALL of them must be compiled with the “debug” option “on” or “debug” option “off”. You cannot mix easily the DLLs compiled with the “debug” option (for example Qt) and DLL compiled with no debug
No, it is not. One can use any 
available Qt version 3.3.x and higher . What is special with very Qt 4.4.x - it is “free” on Windows platform with VC++ compiler.[quote=“Axel_Muc”]I did not build QtRoot. I used the selfinstalling exe.[/quote]What you had downloaded is the binary rather the source code installation. This installation was compiled against of Qt 3.3.7 and run-time environment of Qt 3.3.7 is included in to that selfinstalling exe[quote=“Axel_Muc”]Now I tried to understand what the script does, because I wanted to build QtRoot (against Qt 4.4) on my own[/quote]Yes, this is what the uploaded script does. It does build Qt 4.4.x also. You are recommended to build all packages together to make all builds consistent. One had told, this is Win32 VC++ feature; on Win32 platform one has to build the different packages consistently.