Re: Using static library

Tech-Archive recommends: Fix windows errors by optimizing your registry

myfavdepo@xxxxxxxxx wrote:
what i do not understand is that how the
buiding of the static library was successful first time without
resolving the references to the xerces?

A static library is nothing but a collection of object files. If there are
unresolved symbols, they simply stay unresolved until the final linking
stage. In fact I think the no resolving at all is done.

Uli

.

Relevant Pages

  • Re: unresolved symbol with shared library
    ... the C++ programming language as defined by the ISO, ... > I compile the libs as before and then try: ... > for resolving any symbol and my application is still complaining about ... It maintains a list of unresolved symbols ...
    (comp.lang.cpp)
  • Re: unresolved symbol with shared library
    ... >>The compiler then comes with a waring that the libvrpn.a is not used ... >>for resolving any symbol and my application is still complaining about ... It maintains a list of unresolved symbols ... >is nothing after the .o files, so you get a linking error. ...
    (comp.lang.cpp)
  • Re: Gloss error
    ... Never mind about the previous posting, ... that one time texify test was enough for resolving all references, ...
    (comp.text.tex)
  • Referencing mso enumerations (e.g., msoLineSolid)
    ... I receive compile errors in resolving ... references to mso enumerations that work in Office ...
    (microsoft.public.excel.programming)