[quote=“Axel_Muc”]What I want to create is what the root manual calls “root-based Qt-application”. I just want to use Roots plotting and statistics capabilities.[/quote]Yes I did understand this.
This is where your trouble came from. I did not use g++ I did use VC++
[quote=“Axel_Muc”]After long error searching [/quote]It was your mistake. You had to ask for “ROOT Support” earlier.
[quote=“Axel_Muc”]I realized that the g++ compiler does not work with the VC++ compiled BNL-Root libraries (I am not so experienced in C++).
Therefore I took the Qt4 source and compiled it with VC++ on my own. So I am using VC++ instead of g++ now,[/quote] Yes, it is the correct step.
[quote=“Axel_Muc”]which wasn’t my original intention, but works fine for Qt and seems to work for Root.[/quote] Yes, it should.
[quote=“Axel_Muc”] Just the combination of Root and QT4 (by TQtWidget) makes problems. As you explained this is experimental and I understand that.[/quote]No, it is not.
The experimental nature of the QtRoot with Qt4.4.x is NOT the source of your compilation / linking troubles.
You had to build QtRoot against of Qt 4.4.x. Did you do that? How? I think you did not build QtRoot against Qt properly (it does not matter which version Qt3 or Qt4). The shell script attached does show how this job should be done. It does job. There is another simpler script that does build just QtRoot for windows alone. (It is included into CVS repository too).
Qt4 is NOT just better Qt3. It is the new package. That means the code written for Qt4 cannot be compiled under Qt3 and versa verse. Qt3 is deprecated. It will NOT be supported by the next ROOT production release anyway.
Qt3 is not recommended for the new applications.
[quote=“Axel_Muc”] As I saw the next Root production release is planned for June 25 and since I am just beginning I think I will wait for that. From then on I will test and report bugs. [/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
For you, this means you have to recompile everythting YOURSELF anyway. This is neither Qt nor QtRoot feature, it is Win32/VC++ “nature” that you have to deal with as soon as you create any application for Windows.
Another issue to consider, I doubt CERN is going to produce the Windows distribution with any Qt plug-in.
On the other hand, I’ll be very busy during June, July with my collaboration (STAR ROOT production version 5.12 ) to test the ROOT 5.20 “production” release.
I used to wait 1 month at least before starting building my “binaries” anyway. Since the coming release is significantly different from the previous ones, I anticipate it is going to take an extra time to learn how to make the robust binary distribution for newest ROOT 5.20.
CVS: I do not think it is a typo. Maybe I do not have the rights (in our network) to connect to this server. Maybe I try from my home PC.
Axel[/quote]I am wondering if you should define “http_proxy” environment variable to allow cvs communicating through firewall, see your sys-admin please) QtRoot is available as tar-ball too root.bnl.gov/QtRoot/downloads/qtFullRoot.tar.gz