Sign in to follow this  
godsenddeath

Standard Windows DLLs

Recommended Posts

I've noticed Visual Studio 2010 adds certain DLLs to the linker input by default. I have an idea of what kernel32, user32, and gdi32 contain, but do I really need winspool.lib,comdlg32.lib,advapi32.lib,shell32.lib, and ole32.lib among others? Is there a resource that would give me an overview of that these libraries contain, and if I would be able to remove some frm my project?

Thanks.

Share this post


Link to post
Share on other sites
Couple of points:
[list]
[*]A lot of libraries are added just for convenience
[*]You can always try removing them one at a time and see if everything still links (you'll get Unresolved Externals if you needed a library you just removed)
[*]Google can probably tell you anything you need to know about what services each of those .libs offers; MSDN can fill in the gaps
[/list]

Share this post


Link to post
Share on other sites
As stated, if the program doesn't actually reference anything in those libraries, then they wont be linked. Also, you shouldn't worry about any of those libraries, they are really not a dependency because it's not as if you are ever going to find a system that is missing one of those. Those DLLs all belong to the Win32 subsystem. They are essential operating system files.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this