11 Oct
2002
11 Oct
'02
1:01 a.m.
Greg Turner <gmturner007(a)ameritech.net> writes:
Is there, aside from "just knowing," or tracing down API's one-by-one, a task which isn't always obvious to me anyhow, a systematic way to check for broken dll dependencies?
"make checklink" does this. It won't tell you which dependencies to add though...
I also presume there are some rules about what is allowed to depend on what, which I also don't know...
The basic rules are that you can't create circular dependencies, and that in general you shouldn't import things that the equivalent dll under Windows doesn't import. -- Alexandre Julliard julliard(a)winehq.com