How The Heck Dynamic Library Works?

Question

1. Assume i got an application called "X-Zak", this application is set with static library. So when the user install it, all dll's, etc be stored in a specified path, so user can run the program normally, if one of these files deleted, program won't function properly. RIGHT?

2. If "X-Zak" is set with dynamic library, then when user install the application, none of the dll's be installed because its not included in .exe. So user must have the dll's files ready in his machine! User by default, can't have it, he might have the OS system dll's, but not the dll's that specific for Application! so how does this function? Does user need to load a different set of files (dll's, etc) and install manually & then install the .exe, so when user runs the application. The object code (or whatever in there) can link to the extras (user dll's) dynamically? Can u explain?

THANKS

Answer 1

A dynamic library is loaded into the program at runtime from external files (called dlls in Windows). A static library is inked at compile time, so there's a single executable file, and it includes all the library routines the program needs.

Answer 2

If you're in using Dynamic Link, when you create the installer you add all the DLLs the user will need to run "X-Zak". That's what installers are for. Otherwise the user will get errors.

Answer 3

i had a similar problem recently installing a DVD burner into a tower with an existing CD. the drivers were so closely related, the system couldn't successfully assign them to the proper device. this doesn't happen very often and is pretty hard to troubleshoot. just so you know it is a possibility you could double check the jumpers on the drives, try switching them between the master and slave positions, or try booting with only one drive installed. i would suggest just getting rid of the CD drive and use only the DVD.