NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.

To learn about what's going on, see About the Archive Site.

Re: [netcdfgroup] looking for some hardy windows C/C++ programmers to help check out the new windows DLL...

  • To: Ed Hartnett <ed@xxxxxxxxxxxxxxxx>
  • Subject: Re: [netcdfgroup] looking for some hardy windows C/C++ programmers to help check out the new windows DLL...
  • From: tom fogal <tfogal@xxxxxxxxxxxx>
  • Date: Thu, 10 Mar 2011 11:50:04 -0700
On 03/10/2011 11:45 AM, Ed Hartnett wrote:

I have not yet generated the (windows-only) .lib file. Is this file
really needed? Seems like the utilities are accessing the DLLs just fine
without it.


.lib files are confusing on windows.
Static libraries are named .lib. Thus if you're distributing static libraries.. well, those *are* the static libraries, so you need to distribute them :)
However, MS also uses .lib for so-called "import libraries". These are built in tandem with DLLs, and are a distinct binary than the static libraries, despite sharing the same name. Import libraries are required for an application to *build against* a DLL, but applications linked to a DLL have no need for the import libraries. 

Hope that clarifies things,

-tom
  • 2011 messages navigation, sorted by:
    1. Thread
    2. Subject
    3. Author
    4. Date
    5. ↑ Table Of Contents
  • Search the netcdfgroup archives: