[mythtv] [PATCH] Win32 frontend support

[Ian Caulfield]

On Sat, 24 Jan 2004, Matt Zimmerman wrote:

> On Thu, Jan 22, 2004 at 11:02:48AM -0500, Boleslaw Ciesielski wrote:
>
> > No, this is doable with the Microsoft compiler by creating the import library
> > for the executable:
> >
> > 1. Run "lib /def" on the executable object files. This creates .lib and .exp
> > for the executable but does not link.
>
> What is in these files?

The .exp file basically contains a list of symbols exported by an object
file, and the .lib is a stub library to link against to access those
symbols. Recent versions of ld don't need this when linking against other
DLLs, as they can be generated at link-time, but they can be needed if you
have e.g. circular dependencies.

> > 2. Use .lib from 1 to link the DLL. This creates the .lib for the DLL
>
> Use .lib to create .lib?

Using the .lib for the executable to create the .lib for the DLL

The main problem seems to be that a win32 object with unresolved symbols
specifies them as e.g. symbol 'a' from library 'b.dll'. A dll can be built
that will import gContext, but the name of the executable needs to be
specified, and thus it won't work with more than one executable, somewhat
defeating the point of the dynamic linking in the first place for this
case.

Ian