Hello everybody

I have a program which has 12 workspaces and each of them after
successful compilation can build a seperate *.lib file. The
documentation of this program says

'once all these files are compiled, link them into a library, or a
shared library, or directly into your program.'

I am not sure what has to be done and how. Can someone please tell me
what is required to be done here? Should a single *.lib has to be
created from all these 12 *.lib? How it can be done? What could
'shared library' mean here?

thanks for any help.

Re: linking into a shared library by William

William
Sun Apr 25 13:49:03 CDT 2004

"seia0106" <miahmed67@yahoo.com> wrote in message
news:4fe296bd.0404250710.6d584aa5@posting.google.com...
> I have a program which has 12 workspaces and each of them after
> successful compilation can build a seperate *.lib file. The
> documentation of this program says
>
> 'once all these files are compiled, link them into a library, or a
> shared library, or directly into your program.'
>
> I am not sure what has to be done and how. Can someone please tell me
> what is required to be done here? Should a single *.lib has to be
> created from all these 12 *.lib? How it can be done? What could
> 'shared library' mean here?

It's cross-platform speak. What are called shareables or shared-libraries
(on VAX/VMS, and the 'nix, 'nux, and 'pux o/s's) are called Dynamic Link
Libraries (DLLs) on Win32.

The good thing about such 'shared' components is that they can be changed
without rebuilding the executable that uses them. That's also the bad thing
about them when a change to the callee necessitates a change to the caller.
And the fact that they are external can result in extra fun in one is moved
or deleted.

In short, you can take the advice or not. If you like you can simply add all
12 libraries to a project which makes use of them and link the whole thing
into one executable.

Regards,
Will