When I make an installer for my program, then I have to run into a problem that I rely on some files Does. P>
On Windows:
I often miss some DLLs installed on my system. I usually test my installation by transferring the executable to only one folder, this To see what this cry for the DLL is but it will use DLL which is also on my system 32 folder anyway - which may be in the other users' systems, probably not.
In another way I came to know that I open EXE in hex editor and find patterns' DLL 'but DLL can also depend on other DLLs.
Is there any (preferably free) device that can tell me what is the need for my DLL program? So I will not miss anything.
On Linux:
Linux has a good package management system. Creating an installer in those systems means creating a package for them. I can know what is it. So (shared object) my programs are required. But how can I determine which package is the SO file, so during packaging, can I add that package as a dependency?
On Windows, the device you are looking for is a tool that tells you that DLL is a Depending on what the EXE is (or other DLL).
On Linux, see
Comments
Post a Comment