Let's say I want to run super-duper ultra game. I have beefy GPU and CPU, 32GB of RAM.
And I want to use them to run extremely requiring game.
This The Game requires latest technologies and many calculations.
Let's suppose that Wine has all required dependencies of The Game.
How can I find them, in order to include them into emulated environment?
Is this possible to me (regular medium-/high-language programmer and IT enthusiast), or you really need to be heavy ditched into C++/Python/Perl?
How can I find dependencies?
Re: How can I find dependencies?
If Wine has everything the game needs, you don't have to do anything but install and run it.
Re: How can I find dependencies?
It uses them automatically? Then what is Winetricks for? If Wine detects required parts, why do premade installations allow you to add/remove dependencies?
Re: How can I find dependencies?
Winetricks is mainly used to install native dlls that are not yet implemented or where Wine's builtin version is inadequate.
I have no idea what you mean by "premade installations." If you're using some sort of third party wrapper (e.g., PlayOnLinux, etc.), that's not supported here.
I have no idea what you mean by "premade installations." If you're using some sort of third party wrapper (e.g., PlayOnLinux, etc.), that's not supported here.
Re: How can I find dependencies?
Could it possibly contain DLL's that I would require for The Game? If so, how would I find them and how would I install them?dimesio wrote:Winetricks is mainly used to install native dlls that are not yet implemented or where Wine's builtin version is inadequate.
Re: How can I find dependencies?
Start by checking the AppDB for any known information about your game. If there are recent test reports or howtos, follow them. If there is no information, or what's there is old, you will have to test it yourself. Install the game to a clean wineprefix using the latest development release of Wine and try to run it. If it works, you don't need to do anything with winetricks. If anything doesn't work, post terminal output. http://wiki.winehq.org/FAQ#get_log