On Monday, April 11, 2005, at 09:42AM, Veeresh <[EMAIL PROTECTED]> wrote:
>Hi All, > >Could you please clarify the following query: > >I have attached Makefile.PL and the 'DESCRIP.MMS' file generated out of >Makefile.PL by perl with 'perl Makefile.PL' command.When I do 'mms', then it >finally generate 'XXXX.OPT', but I actually wanted is static library. > A. What is the extenstion of static library file in OpenVMS? > B. How to generate static Library? > C. Is there any way to convert .OPT file to static Library? An .OPT file is a linker options file. There's lots of info on this in the OpenVMS Linker Utility manual, and some of your questions might also be answered in the OpenVMS Librarian Utility Manual; both are available from <http://www.hp.com/go/openvms/doc>. The nomenclature on VMS for static vs. dynamic libraries is that a static library is simply called an object library and by default has an extension of .OLB and a dynamic library is called a shareable image and by default has an extension of .EXE. Object libraries are created by the librarian, and shareable images are created by the linker. There is no sense in which a linker options file can be "converted" into an object library; it contains directives the linker uses to generate images (both executable images and shareable images). A normal build of an XS extension will create an object library, and then it will use the linker to create a shareable image from that. Do you not get an oc_lib_tool_xs.olb? And by the way, why do you want one? It's not needed once the shareable image is created.
