Creating slots with Q_OBJECT

[camel]

It becomes extremely annoying when I have to deal with things like qmake and nmake, which I have dealt with in linux, and it's extremely annoying to do.

Personally I do not think so.

When I want to compile a project of mine I do

qmake
make

qmake
make

To copy to clipboard, switch view to plain text mode 

and I am done...

Which is why i found the template file, which should have done all this for me.

Where did you find it? Perhaps you ask the author of the template why it doesn't work as it should?

I even tried an example i found right out of the documentation of trolltech, and not anywhere did i see a #include moc, or any other compiler options to be set anywhere.

The examples use qmake which hides all those nasty things. (If you do not start to digg too deep ;-)

The include trick I mentioned is only needed when you declare a QObject subclass in a cpp file. But that should not normally be needed.

From what you've told me, all I understand is that Qt has some extra things that needs to be done in order to understand things like "emit" "slots" "signals" and instead of them doing all the work in some header file, as I've seen in windows <snip> I have to now do something in order to compile these moc files, which I don't even know where they come from or what makes them... I'm suppose to include something that doesn't exist...

You should not have to care about anything. MOC is an implementation detail that should be abstracted away. It is in qmake, it probably should also for this template, but since I do not work with devc++ I have no idea why it would not.

I usually use Visual Studio .NET 2003, but it can get very very annoying when setting up the settings, and the template file I thought handled most of it, but it seems I still have 3 bulky DLLs which i don't know how to link to my program as "lib" or "a" files.

Allow me the question, why don't you like the dlls? (Just pure curiosity :-)

So how do I do this? Does anyone have "dummy steps" without going into too much technical detail about the library itself?

Does this this thread help?
In the end you "just" have to reconfigure an rebuild Qt to be static.
(But I do not think that you can loose the mingw dll...but you might want to google that)

How do I make these moc files, and if possible, do you think it can be applied into the DevC++ template file?

Well, I am not too fluid with devc++ but from a (german) article it seems that you have to include a custom makefile/qmake step to have devc++ play nice.


Does it have to be DevC++?
In the Qt Software forum a few native Qt4 IDEs have been posted, which probably know how to work with Qt out of the box. (I cannot give you my word that they work since I am a vi/qmake/make user myself :-)

If you like Visual Studio, the comercial edition of Qt 4 for windows has Visual Studio integration available (at a price though).


Hope that helps...