Jump to content
  • Advertisement
Sign in to follow this  
fpsgamer

dll Question....

This topic is 3882 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

I recently downloaded the source code for the Collada DOM API. The source contains a Visual Studio solution which itself contains two projects. One builds a static library and one a dynamic library (dll). The dynamic library project produces a *.dll file and *.lib -- whereas the static library project produces a different *.lib file. I have no idea why the dynamic library project would produce a *.lib file in addition to a *.dll file. Any ideas?

Share this post


Link to post
Share on other sites
Advertisement
a dirty but quick explanation:

- a standalone lib:
you can use it to put the lib code inside your game as if it was a mere couple of .h/.cpp files.

- a lib + a dll:
- you load a dll in runtime, and use the lib to map function names.

- a dll only:
- you load a dll in runtime and need to fetch function pointers from names with something like GetProcAddress

EDIT: corrected typo (thanks Todo)

[Edited by - mystb on April 4, 2008 5:34:24 AM]

Share this post


Link to post
Share on other sites
Quote:
Original post by mystb
- a lib only:
- you load a dll in runtime and need to fetch function pointers from names with something like GetProcAddress


For your information, by that he probably meant: "only a .dll" (typo).

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

We are the game development community.

Whether you are an indie, hobbyist, AAA developer, or just trying to learn, GameDev.net is the place for you to learn, share, and connect with the games industry. Learn more About Us or sign up!

Sign me up!