It's a simple question, but i think the answers arent. So well, from where can i know what dlls a application needs?
Thanks for every answer
From where can i know what dll a application needs?
Re: From where can i know what dll a application needs?
Start by testing the application in a clean wineprefix. If everything works as expected, it doesn't need any. If there are problems, check the AppDB for any maintainer Howtos and/or information about workarounds in test reports. You can also check bugzilla for known bugs, as workarounds may be mentioned in a comment.
If none of that helps, post terminal output here with the name of the app, the Wine version tested (should be the latest development or staging release), and a description of what exactly is not working.
If none of that helps, post terminal output here with the name of the app, the Wine version tested (should be the latest development or staging release), and a description of what exactly is not working.
Re: From where can i know what dll a application needs?
If the WineHQ AppDB isn't of use, for the particular application you are testing...ReySKR wrote:It's a simple question, but i think the answers arent. So well, from where can i know what dlls a application needs?
Thanks for every answer
Then it's probably worth running the application with
Code: Select all
export WINEDEBUG=+loaddll
wine start ... &>~/wine_loaddll_log.txt
Also an application will often call a WIN API entry point, which does not exist in a builtin dll - typically result in an ERR, or results in a FIXME warning (due to only being partially implemented).
These entry point functions can usually be looked up quite easily on MSDN, to see what dll they correspond to.
Bob