Re: Alternate file types for RUN ?

Arne Vajhøj wrote:
JF Mezei wrote:
Arne Vajhøj wrote:
When did you last see a static linked image on VMS ?

Run time libraries such as the C RTL are associated with the image at
link time. While you may be able to do tricks with logicals to use a
different file, the association is still static since symbols are
resolved at link time and the image will just branch to specific
addresses where the routine is expected to reside within the shareable
image.
This is qwuite diffferent from lib$find_image_symbol where nothing
happens at link time and the finding and resolving of symbols within
some image file is done truly at run time.

No and no.

Static linking means that the code of the library is in the
executable EXE.

Dynamic linking means that the code of the library is in a
shareable EXE.

Static linking is a concept practically unknown on VMS.

I agree with you up until this point.

I have many applications that link against OLB libraries. The code from the library gets copied into the executable. My build procedures rarely link against OBJ files. Much better to have them in a library.

--
David Froble Tel: 724-529-0450
Dave Froble Enterprises, Inc. E-Mail: davef@xxxxxxxxxxxxx
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA 15486
.

Relevant Pages

  • Re: static library and dynamic library
    ... Also the code of the library will load into the program. ... yeah, at link time, all the code and data from the library goes into the binary, which is part of why using lots of static libs tends to produce large binaries... ... so, the loader will also grab the libraries, and resolve the addresses to the addresses in the library. ... in windows, however, DLLs are typically fixed-address to allow sharing. ...
    (comp.lang.c)
  • Re: Alternate file types for RUN ?
    ... resolved at link time and the image will just branch to specific ... happens at link time and the finding and resolving of symbols within ... executable EXE. ... Static linking is a concept practically unknown on VMS. ...
    (comp.os.vms)
  • SUMMARY: _F64_stat symbol missing
    ... Problem arises at link time when trying to link to _F64_stat and _F64_fstat ... library needs to be built on V4.0 or you need to upgrade to V5.1. ... As in this case your libraries reference symbols that exist ... I would contact cisco and ask them for 4.0 compiled libraries. ...
    (Tru64-UNIX-Managers)
  • Re: Shared objects
    ... Depending on the file type, ... to that of using function pointers: If you know the function name ... libraries: If you know the library name at link time you just ...
    (comp.unix.programmer)
  • Re: Anjuta C++ Project problems
    ... > Looks like you are not linking against the needed libraries. ... > now are about undefined symbols in the objects (link time), ...
    (Debian-User)