I'm afraid we're starting a flame war, but as I'm the Head-Flame-War-Spawner here then I'll answer anyway

Quote Originally Posted by VireX View Post
I been programming C++ for years, and I only used Pure Win API rather than graphics libraries.
WinAPI is C, not C++.

BUTTTTT I would make mine compilable easily with DevC++ and Visual Studio.
Define "compatible". You don't make a library "compatible" with an IDE but with a compiler and Visual Studio compiler is surely supported. I don't know what DevC++ uses, but I know people are using it with Qt, so I guess it doesn't enforce any broken compilers.

Rather than force some sort of qmake/make method that never works out.
1. Nobody forces you to use either qmake or make
2. qmake/make always works for me and furthermore it worked for Windows people I've been working with even if they knew nothing about it and it worked when Visual Studio compilation was failing due to lack of some functionality in the integration plugin or some other problems (I don't know, haven't used the integration).
3. Visual Studio has it's own version of make, which is called nmake and it's a standard tool accompaniating the environment. Of course qmake supports it.
4. Make has been a standard tool for automatic compilation long before Gates even had his garage built.

Even if only the Commercial version has VS projects, I would assume someone might have posted their own DevC++ or VS projects. But since I been on this forum, I am under the impression that no one in this forum that has seen my posts has used DevC++ or VC to compile Qt.
The reason is simple. If you posted a VS project or DevC++ project, you'd be waiting ages for help, as not everyone has those, whereas qmake is a standard tool shipped with Qt, so you can get your answers in a matter of minutes instead of days. And if you look at the set of good habits of posting here (I think we have such a list somewhere), nobody says you have to post qmake projects and not others. I can always call "qmake -project" and have a working qmake project created from scanning the directory. Sometimes some adjustments may be needed if the files you send need some special treatment.

If I can't figure out how to use them, then how can someone who barely learned c++ use them? If it's so easy to figure out, why hasn't anyone explained this to me, I been talking about it for basically all the posts I have on this forum.
Maybe you haven't read the qmake tutorial?


I still have not figured out a single way to use Q_OBJECT/slots without using the moc, or qmake/make, and there is no getting around it,
As for moc - you have to use it. The reason is simple, it is moc which creates the whole signal/slot implementation for you. You could of course to it by hand, but... well... don't count on our help here, we'll suggest using moc...

As for qmake, you can easily call moc by hand, therefore qmake is not needed. It's just a tool that creates a compilation script for you.

but this means I have to use qmake/make to do it FAST. However, if Qmake and make do not compile a standard pro file that is obviously correctly coded,
Neither qmake nor make do any compilation. Your compiler might be broken or your environment is set incorrectly which confuses qmake about your compiler. Which compiler do you use anyway?

and I did everything according to what people told me and what the docs tell me, then this means the developers did not test this library enough, or express it correctly in their documents, or no one on this forum knows how to properly explain compiling. Take your pick.
You've been asked to name the compiler in one of the previous posts, but you failed to do this. Without this nobody will be able to help you, we're not trueseers.

I can only say that if you use the Borland compiler, then Qt4 will not work with it, simply because the Borland compiler is so broken, it doesn't conform to any decent and recent C++ standard.