Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


Standard Windows DLLs


Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.

  • You cannot reply to this topic
3 replies to this topic

#1 htcoles   Members   -  Reputation: 182

Like
0Likes
Like

Posted 08 April 2012 - 01:27 PM

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.
--------------------------------------Not All Martyrs See Divinity, But At Least You Tried

Sponsor:

#2 ApochPiQ   Moderators   -  Reputation: 16412

Like
0Likes
Like

Posted 08 April 2012 - 08:24 PM

Couple of points:
  • 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


#3 Endurion   Crossbones+   -  Reputation: 3687

Like
0Likes
Like

Posted 08 April 2012 - 11:08 PM

VS will also remove unneeded dependencies when optimizing, so your final executable will not require these to run.
Fruny: Ftagn! Ia! Ia! std::time_put_byname! Mglui naflftagn std::codecvt eY'ha-nthlei!,char,mbstate_t>

#4 Chris_F   Members   -  Reputation: 2464

Like
1Likes
Like

Posted 09 April 2012 - 12:05 AM

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.




Old topic!
Guest, the last post of this topic is over 60 days old and at this point you may not reply in this topic. If you wish to continue this conversation start a new topic.



PARTNERS