How to setup Qt for MSVC2010 after successfull build (correct path moc.exe) (Change Qt-Path)
-
Did you have a look to the source of qpatch ?
Respectively, did you try to use?As it looks it simply does read all the files in question, supplied in a file list. Every occurance of the old dir path will be replaced with the new dir. This seems to be fairly simple. However, I will not recommend doing without that tool. But it might be worth a try.
-
I tried it. At first i will modify the src. So that it pathes all files. It makes no sense to pass every file in the qt-dir to the command-line. I'll modify it so that it patches each file. Or could you tell me with files i have to patch? This is a real trivial thing and Qt makes to much work out of it...
-
If you go to the "repository":http://qt.gitorious.org/qt-creator/qt-creator/trees/master/src/tools/qpatch there is the short cpp-file and also the lists of files to change.
-
Glad to see that you were succeeding.
What is the OS you have?
I was trying it myself after the last post. However, the it was not as easy to handle as it looked in the beginning. I have Win7 64 bit. All security measures were activated. I could not debug nor run it easily from a command prompt. I am wondering about the best way around such issues. It is not helpful when you cannot read the output messages on screen.
-
" I could not debug nor run it easily from a command prompt " ... you can't run qPatch?
I think we should correct qPatch to make it a bit more comfortable. Why can we install Qt with mingw without these problems or Qtmsvc2008 without these problems...and after building with msvc2010....problems.
-
I can run, but it is not as you are used to. However, this is not a Qt problem.
In case you are not aware of this. On Win7 ( and Vista) you have to confirm the actions of any program trying to search the disk or writing to the areas where programs are installed. When you start such a program a window pops up asking for confirmation. Unfortunately, the functionality is not returned to the command window you started off, but it is continued in a new command window. The window pops up and it is closed when the program finished. Unfortunately the output is gone with closing of the window. :-( Simple piping did not work, so I had to change qpatch to write to disk. So this becomes quite ackward when you are trying to find the proper spelling of the dir names as you lined out above.
The debugging is probably not running because of Win7 again. The same security measure signals a nogo to the debugger.
BTW it could be also an additional feature of the virus scanner.Probably one can switch off all these security features, but on the other side I prefer to see, when someone else is going to do things on my machine.
I guess most of the problems are existing because more open source ethusiasts are on linux. Would be interesting to see a statistic about that.
-
The link you referred to was broken. Can you find it again and post the new location? I'm trying to find the list of files that needs to be patched. Thanks
[quote author="koahnig" date="1309794847"]If you go to the "repository":http://qt.gitorious.org/qt-creator/qt-creator/trees/master/src/tools/qpatch there is the short cpp-file and also the lists of files to change. [/quote]
-
[quote author="textral" date="1324554733"]The link you referred to was broken. Can you find it again and post the new location? I'm trying to find the list of files that needs to be patched. Thanks
[/quote]here is a link again.
"qPatch":http://qt.gitorious.org/qt-creator/qt-creator/trees/9e972b068d5beef0cc5041f7397efd2ff5ad7570/src/tools/qpatch
However this is not a solid way to reference it. It seems to be part of a clone, which google spilled out. The link may be broken again soon. Furthermore, the status is completely unclear. Unfortunately, I could not find that section in the official source tree of creator anymore. -
Here is a "link":http://db.tt/30Lx4Gz7 to the source found on my drive. The source has been adapted for debug output to a file. I doubt that there are other changes. However, one has to check anyhow.
