[IronPython] Anyone know what DLLs is called on Unix?

[Matt Clinton]

Courtesy of http://en.wikipedia.org/wiki/Dynamic_library,

 

GNU <http://en.wikipedia.org/wiki/GNU> /Linux
<http://en.wikipedia.org/wiki/Linux> , Solaris
<http://en.wikipedia.org/wiki/Solaris_%28operating_system%29>  and other
System V Release 4 <http://en.wikipedia.org/wiki/System_V_Release_4>
derivatives, and BSD <http://en.wikipedia.org/wiki/BSD>  variants

libfoo.a and libfoo.so files are placed in directories like /lib,
/usr/lib or /usr/local/lib. The filenames always start with lib, and end
with .a (archive, static library) or .so (shared object, dynamically
linked library), with an optional interface number. For example
libfoo.so.2 is the second major interface revision of the dynamically
linked library libfoo. Old Unix <http://en.wikipedia.org/wiki/Unix>
versions would use major and minor library revision numbers
(libfoo.so.1.2) while contemporary Unixes will only use major revision
numbers (libfoo.so.1). Dynamically loaded libraries are placed in
/usr/libexec and similar directories. The .la files sometimes found in
the library directories are libtool
<http://en.wikipedia.org/wiki/Libtool>  archives, not usable by the
system as such.

Mac OS X <http://en.wikipedia.org/wiki/Mac_OS_X>  and upwards

The system inherits static library conventions from BSD
<http://en.wikipedia.org/wiki/BSD> , with the library being in a .a
file, and can use .so-style dynamically-linked libraries (with the
.dylib suffix instead). Most libraries in Mac OS X, however, are
"frameworks", placed inside of special directories called "bundles
<http://en.wikipedia.org/wiki/Bundle_%28NEXTSTEP%29> ", which wrap the
library's required files and metadata. For example a library called "My
Neat Library" would be implemented in a bundle called "My Neat
Library.framework".

Microsoft Windows <http://en.wikipedia.org/wiki/Microsoft_Windows> 

*.DLL <http://en.wikipedia.org/wiki/Dynamic-link_library>  files are
dynamically linkable libraries
<http://en.wikipedia.org/wiki/Dynamic-link_library> . Other file name
patterns may be used for specific purpose DLLs, e.g. *.OCX for OCX
<http://en.wikipedia.org/wiki/OCX>  control libraries. The interface
revisions are either encoded in the files, or abstracted away using
COM-object <http://en.wikipedia.org/wiki/Component_object_model>
interfaces. Depending on how they are compiled, *.LIB files can be
either static libraries or representations of dynamically linkable
libraries needed only during compilation, known as "Import Libraries".
Unlike in the UNIX <http://en.wikipedia.org/wiki/UNIX>  world, where
different file extensions are used, when linking against .LIB file in
Windows <http://en.wikipedia.org/wiki/Windows>  one must first know if
it is a regular static library or an import library. In the latter case,
a .DLL <http://en.wikipedia.org/wiki/Dynamic-link_library>  file must be
present at runtime.

 

 

________________________________

From: users-bounces at lists.ironpython.com
[mailto:users-bounces at lists.ironpython.com] On Behalf Of Dino Viehland
Sent: Monday, November 05, 2007 4:34 PM
To: users at lists.ironpython.com
Subject: [IronPython] Anyone know what DLLs is called on Unix?

 

Seo proposed this feature a while ago:

 

http://www.codeplex.com/IronPython/WorkItem/View.aspx?WorkItemId=3730

 

and I'm (finally) adding it and wondering what (if anything) we should
do if the platform is Unix.   Unfortunately I don't have a Unix box
handy but I'm just guessing it's not called DLLs there :-).

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ironpython-users/attachments/20071105/60b3441d/attachment.html>