On Fri, 3 Oct 2003, Eduardo Chappa wrote:
> Hi,
>
> This is a quick (and probably stupid) question about dependencies. I am
> trying to build Pine to clear a problem with the mbx driver. It's not big
> harm that there's a problem with it right now, but I think it's important
> to support it for several reasons, which I won't discuss here, since it's
> not the purpose of this message.
>
> The only way that I've found that I can solve the problem is by linking
> with "-lkernel32", which is a library included in the w32api package, so
> the question is, if I were to release this new version of Pine, would that
> require any change in the required list of packages?
>
> (cygcheck returns 2 Dlls from C:\Windows\system32, I am not sure if I
> can assume that those exist in the users machine or not).
>
> Thanks,
> Eduardo
Eduardo,
w32api contains import libraries that allow linking programs with standard
Windows DLLs. These import libraries are not needed afterwards to run the
program - only the DLLs are. kernel32.dll is a Windows DLL that will be
present on any Windows machine, so you won't need extra dependences for
that. You may want to indicate w32api as a build dependence, though (in
the README).
Igor
--
http://cs.nyu.edu/~pechtcha/
|\ _,,,---,,_ [EMAIL PROTECTED]
ZZZzz /,`.-'`' -. ;-;;,_ [EMAIL PROTECTED]
|,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D.
'---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow!
"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster." -- Patrick Naughton
