PDA

View Full Version : Qt 4.1.0 on Visual Studio 2005



nErnie
5th July 2006, 20:52
I am a newbie. I just intall Qt 4.1.0 yesterday. I had already install Visual Studio 2005

I ignored all the installation notes and allowed the installer wizard do its job.

Things seemed to go pretty well. I found the path environment variables setup automatically.

So I launched Visual Studio, and was not even greeted with any sign of Qt or so :mad: ;-( . Could someone please help me out! How can i integrate QT 4.1.0 with VS2005, so that i can just program from there on? Any tips :confused: ?

nErnie

gfunk
5th July 2006, 21:07
The open source version does not come with integration for VS2005, you have to buy a Qt license to get the specially-developed VS Integration that Trolltech has written. I'm not sure the steps to use VS2005 with Qt without the VS Integration, but I don't imagine it is very smooth. I believe Qt open source is meant for people who are generally experienced with using Unix prompt and editing makefiles.

I can tell you that if you do buy the license, the VS Integration is quite good - it makes the VS2005 handle all the moc'ing and uic'ing, add Qt GUI classes, and can design UI files from within VS2005 using QtDesigner (rather than spawn separate process).

jpn
5th July 2006, 21:12
Qt4 with Visual Studio (http://qtnode.net/wiki/Qt4_with_Visual_Studio)

Seth
5th July 2006, 22:49
Greatd link!

Any idea if Visual Studio .NET (2003) the student version would work with QT integration?

green here, thanks!

Seth

gfunk
5th July 2006, 22:55
Wow! That is an interesting link. I had been wondering how to use msvc with the open source version.

It does seem like a bit of work to just set up Qt though, and that's before even compiling the sources! If they could distribute a package that contains the Qt after it has been patched and compiled, I think that would be convenient.

As for standard code development, using open source Qt with msvc is probably better than starting out with the VS integration, because then it teaches you the underworkings, the foundations of Qt. The VS integration tends to hide it (make it easier to use), so when you run into weird problems, it can be hard to figure out what is going on.

gfunk
5th July 2006, 23:00
Any idea if Visual Studio .NET (2003) the student version would work with QT integration?


With Trolltech's VS integration? I'm not sure what the student version has stripped away. I think it would work though, you could ask Trolltech.
http://www.trolltech.com/products/qt/indepth/vs-integration

Seth
6th July 2006, 00:01
gfunk,


As for standard code development, using open source Qt with msvc is probably better than starting out with the VS integration, because then it teaches you the underworkings, the foundations of Qt. The VS integration tends to hide it (make it easier to use), so when you run into weird problems, it can be hard to figure out what is going on.

Yes, I am just starting out, very green, so good words above!

Do you think I should take a further step back and use MinGW w/ QT4? Would that give me a better understanding of the needed underpinnings? Or should I just go ahead and try to get Qt 4 with msvc working? What long term benefits would I gain by using MinGW w/ QT4?

Thanks in advance!

gfunk
6th July 2006, 00:25
Er, I have not actually tried much minGW, nor the plain MSVC/Qt without the integration. I would say, try them both, see which one you prefer, than report back :P
Actually, you should be able to ask Trolltech through email for a 2-week evaluation copy of the VS integration from Qt prior to actually getting the commercial license (which then costs like $1-2k).
The more environments you try, the better of a feel you should get for the cross-platform benefits of Qt.

Brandybuck
6th July 2006, 01:56
Do you think I should take a further step back and use MinGW w/ QT4? Would that give me a better understanding of the needed underpinnings?
If you do not need Visual Studio, then I would say go ahead and use mingw. VS has a very good debugger, but I've never been impressed with the rest of it.