QT IDE and Debugger

[pospiech]

Ah yes... It did not even occur to me that someone trying to install a Qt IDE would not have installed Qt first and adjusted its environment variables... Maybe I become too geeky over the last few years to remember what newbies expect...

Installing Qt first does not help.
If the System Path includes the Path to Qt and other Qt-Dll containing Directories, it is only a matter of luck if it works or not. And deleting other apps from the PATH is no solution. Nobody wants to break apps because of a new one.

[fullmetalcoder]

No sensible packager invades system directory with bundled dll's (unless the package is made for those dll's)... They should be put in local folders where the app may find them.

In the case discussed here, installing Qt PROPERLY first would have helped has the error clearly shows that the executable failed to find Qt. (by properly I mean setting pathes and choosing the correct version).

[pospiech]

No sensible packager invades system directory with bundled dll's (unless the package is made for those dll's)... They should be put in local folders where the app may find them.

That does not help if Applications that are widely used, like Miktex and Matlab (probably every Phd Student of Physics in my university has both if they use Windows), installl dlls in there application folder and add this folder to PATH.

In the case discussed here, installing Qt PROPERLY first would have helped has the error clearly shows that the executable failed to find Qt. (by properly I mean setting pathes and choosing the correct version).

With such an error message AND multiple dlls on the system and within PATH, how should one know what the error is causing and how can I install Qt and not have such problems? This is unclear to me.

[fullmetalcoder]

That does not help if Applications that are widely used, like Miktex and Matlab (probably every Phd Student of Physics in my university has both if they use Windows), installl dlls in there application folder and add this folder to PATH.

well then THEY are responsible for screwing things up... If you bundle everything into a single folder don't add it to the path... It is not up to a program to deal with borked setups, at least that's my opinion and I'm not gonna waste weeks to get things to work on every possible dll mess windows allows to exist.

I'm afraid I ain't got any simple solution to offer apart from building the app from source and, if required, coying the right dlls into Edyuk's installation folder.

[pospiech]

I'm afraid I ain't got any simple solution to offer apart from building the app from source and, if required, coying the right dlls into Edyuk's installation folder.

I agree with you. But, and I say this not in the intention to offend you, other editors like qdevelop ship with dlls in their app folder and do not deal with such problems.