[solved] Questions on deployment
-
Because dependency walker only shows the dependencies of the exe or dll you load into it and the DLLs that it can reach.
So, let's suppose you have prog.exe that depends on fancy.dll and that fancy.dll depends on standard.dll then, if you do not have fancy.dll reachable bye depends.exe, it only shows that prog.exe depends on fancy.dll. As soon as you make fancy.dll reachable, it shows you that standard.dll is also needed.
-
Well, after playing with Dependency Walker for a bit, I now realize that I don't understand exactly how to use the information it supplies. How do I go about ensuring that I've locally supplied all necessary libraries? Do I need to remove or disable the paths to them in my PATH environment variable? Because it seems that DW will list them whether or not I've locally supplied them.
Also, I don't seem to have a file "libpthread-2.dll" on my system. I do have a "libpthread.a" which I take it is a static library. Should I move this over?
-
Perhaps the best way for you is forget about dependency walker for now.
Most Qt ddl you will need should be in C:\QtSDK\Desktop\Qt\4.7.4\mingw\bin . If you don't have this diretory in your system path, your program will not work outside QtCreator, i.e if you run the executable from file explorer.
Then create a new directory with your exe file, paste the files that Volker already told you, one by one, until your program starts working from the file explorer. Then you should have all the necessary files in that directory ready to go.
You can now zipped, or better, create a fancy setup.exe package. I usually use install creator (http://www.clickteam.com/website/usa/install-creator.html) but there are manny others and perhaps better programs to pack you software. It's very easy to use, and doenst require any scripting.You could install dll files in windows system or system32 directory, thats usually the windows way of installing things, but that can cause some problems that I'm not going to talk about here, so perhaps it's best to keep it simple and install all dll files in the same directory of your exe file, usually C:\Program Files (x86)\your_program
-
Hey, John - thanks for the reply. A few notes:
I'm using 4.8.0, not 4.7.4.
I'm trying to get this working on a program that uses no QT libraries.
I still have an unidentified file (libpthread-2.dll)
probably because of #3, when I run the DW profiler, I get some output that looks rather unsuccessful. I'll postpone posting it until I get that last file that Volker mentioned resolved.
So, again, I'm kind of going for "proof of concept" here. I just want to know that I can make this work. Once I'm successful with this program, I'll start using the same technique with those that will use the Qt libraries. Right now, though, I'm stuck until I get that final file nailed down.
-
I don't use the SDK builds, but a stand alone MinGW installation + manually compiled Qt libs. I don't know the exact setup of the SDK and how all the libs are named there. But, all the needed DLLs are in the SDK, otherwise you wouldn't be able to run the apps from Qt Creator :-)
-
[quote author="Volker" date="1334132257"]I don't use the SDK builds, but a stand alone MinGW installation + manually compiled Qt libs. I don't know the exact setup of the SDK and how all the libs are named there. But, all the needed DLLs are in the SDK, otherwise you wouldn't be able to run the apps from Qt Creator :-)[/quote]
At present, my concern isn't whether the SDK supplies everything or not; it's whether I've successfully copied all files that are necessary to my executable's directory.
Again, since the SDK is in my PATH variable, how do I know that when my program needs a library, it's getting it from the local directory and not via PATH? Do I need to remove the SDK from PATH to test this?
I hope this makes sense; it's 4 AM here.
-
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?
