RE: Regarding .lib and .dll



Hi Kanungo,

 

In MSVC, give the path to *.lib files allows you only to have access to definitions of library functions. By default, any application is compiled dynamically; I mean to use the *.dll files. If you want compile your application statically with MSVC, you need to prevent DLL binding in the “Linker” tab. It’s a bit similar to the –static option required by GCC.

 

Regards

 

Marco Dos Santos Oliveira

EBU/European Broadcasting Union

Technology and Innovation Department

 

From: gtk-i18n-list [mailto:gtk-i18n-list-bounces gnome org] On Behalf Of Parth Kanungo
Sent: mercredi 10 avril 2013 15:10
To: gtk-i18n-list gnome org; Behdad Esfahbod
Subject: Re: Regarding .lib and .dll

 

 

Just wanted to add that the question was asked in context of Microsoft Visual Studio. 

 

In Linux, when I used the pango libraries, I required only the .so files (which are analogous to dll files of Windows). 

 

Correct me, if I am wrong.

 

 

 

On Wed, Apr 10, 2013 at 11:24 AM, Parth Kanungo <kanungoparth gmail com> wrote:

Hi all,

 

Why does pango require both .lib and .dll to run ?

 

Normally, in any applications, I use either .dll or .lib. 

 

From what I know, whenever I make a .dll or a .lib, the functions contained in both the files are same. The only difference is that .dll links dynamically and can be shared, whereas a .lib links statically during compilation.

 

-- 

Parth 



 

--

Parth 


**************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error, please notify the system manager. This footnote also confirms that this email message has been swept by the mailgateway
**************************************************



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]