The compiler takes source code and produces a binary from it, which is machine-code for a particular processor. The linker then puts various binaries together, handling the adjustments needed to provide the right memory locations for everything, making sure that every symbol called resolves to one that's actually present, and knitting the whole thing up rather neatly.
If it were otherwise, you could just as easily take your library and link it with a Windows app, or a Linux program. If this were the case, a cross-platform language like C would never have been necessary, and the development of Java would've been re-inventing the wheel. Libraries are as processor-specific as applications. They're just modular. They tend to be linker-specific as well, as Codewarrior libraries don't seem to play well with gcc. On Thu, 24 Feb 2005 20:47:40 -0000, Jonathan King <[EMAIL PROTECTED]> wrote: > As Ben said, the library is just an object file that is not processor > specific. It must be linked to other code to be compiled into processor > instuctions, so therefore will be compiled as whatever it is linked to. > -- > For information on using the Palm Developer Forums, or to unsubscribe, please > see http://www.palmos.com/dev/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
