[solved] Questions on deployment
-
Ah, I see. To test without the SDK do not remove it, it's sufficient to just rename the toplevel directory (e.g. from QtSDK to QtSDK-Blocked) and the do the tests. That's what I do regularly. Don't forget to re-rename it afterwards, otherwise your builds will fail :-)
To see where your DLLs are from, you can switch dependency walker to show the full paths, instead of the filenames only (F9 if I remember correctly).
And as far as I remember, local DLLs take precedence over those in the PATH. Except for those that nee a manifest and where windows insists on them residing somewhere in a system directory. But this is neither true for MinGW nor the Qt DLLs.
-
Well, after so many false starts, I hesitate to claim victory, but it appears that it's working.
I'm still using a couple files from my \windows\syswow64 directory (KERNEL32.DLL and MSVCRT.DLL) but I imagine that's OK. (As a side note, that MSVCRT file isn't a Visual C file is it? I'd have no idea how that crept in there.)
I guess the acid test is to send this to someone without Qt and have them try it, huh?
-
You could start with "Mission Accomplished" ;-)
msvcrt.dll is the microsoft C runtime library. It is used by MinGW too, as MinGW uses native Windows API. Kernel32.dll is ... the kernel :-) ... it's loaded by all applications, you must not copy that into the app directory.
What DLLs do you have in your application directory now?
For test purposes: I usually have a vanilla windows installation running in a virtual machine. You can install your stuff and roll back to a pristine snapshot once you're done.
-
I'd originally marked this solved, but...I realized my job isn't quite finished here. Now that I've discovered all the files necessary to include in my distribution, is there a way to use the Deployment methods in the Run Settings to automatically copy the necessary files, and the executable, into a "delivery" directory that I can then zip and send to a customer?
-
Well...here I thought I had this thing solved. Just tried it on a second application (copying over the same files) and...it doesn't run.
I've looked at the DW log, and it doesn't indicate any missing modules. The program runs OK within Creator. What else besides a missing library might cause the program not to run?
-
Nope. If I double-click on the program from the GUI, it sits for a moment, but does nothing. If I try in invoke from the CLI, I get a prompt back immediately.
I think I found an issue: I copied my DLLs over from the directory with the program that worked, but according to DW, the two programs expect different libraries. One is from \windows\system32; the other from \windows\syswow64. I'm trying to look into that, but at the moment, Creator is giving me some grief that might be related to my downloading the newest release.
Guess I should nuke the build directories and start over?
-
I don't know how I did that, though. According to DW, the two programs are using different libraries, but...I don't see any differences in my build settings.
I could go get the 64-bit libraries for the second program, but I'd rather fix my builds so they use the same ones.
-
I deleted and regenerated the build directories...same behavior.
I think my comment about \windows\system32 vs. \windows\syswow64 may have been a red herring. When I worked in DW and watched a bit more carefully, I noticed that BOTH programs begin with system32 in the dependency tree, but when I profile, BOTH change to syswow64. (This is odd, but I'm not sure it's related to my issue.) When I refresh, both revert to system32.
Both programs show identical dependencies.
Both programs have the mingw files MINGWM10.DLL and LIBGCC_S_DW1-2.DLL in their run directories.
But, one program runs, and the other doesn't. I'm kind of at a loss to explain this.
EDIT:
Another data point: I added the files:
- libgomp-1.dll
- libpthread.a
- libstdc++-6.dll
to the directory of the malfunctioning program (even though they weren't necessary for the one that works)...same results.
-
If anyone's willing to take a look, here's the DW log file after a profile:
"profile.txt":http://scopedin.com/data/profile.txt
I can't read these tea leaves, but perhaps someone else can.
-
Solution discovered, and documented "here.":http://qt-project.org/forums/viewthread/16470/
Thanks to everyone who replied.
