RE: anyone anyone?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I am nowhere near a wine expert, but here's what I would offer as an answer.

Wine has the ability to pick "builtin" libraries or "native" libraries. You can specify what library it should look for in the .wine/config file.

The goal of wine is to eventually provide enough "builtin" libraries and functionnality to emulate a full windows installation. Builtin libraries are wrote by the wine team. You can find them here on redhat9. In other words, this is where wine will look for "builtin" libraries:
/usr/lib/wine/wine/ntdll.dll.so
etc


There are times the "builtin" implementation is not sufficient. In that case you can copy the real windows dll in your fake windows drive and instruct wine to load the dll "native". Wine looks for "native" libraries in c:\Windows\System first, then looks for it in a few other places. The documentation tells precisely what are the paths processed and in what order.

To know what libraries are loaded and what type (builtin/native), try the following args when running an app:
--debugmsg +loaddll


Except for a few exceptions listed in the default wine config, the default rule is to use bulitin libraries.

so Im reposting. If it didnt I apologize. Simply put my question is how does wine store the path
for its libs? and is it in a place easily changed? the long drawn

_________________________________________________________________
MSN Messenger : discutez en direct avec vos amis ! http://messenger.fr.msn.ca/


_______________________________________________
wine-users mailing list
wine-users@xxxxxxxxxx
http://www.winehq.com/mailman/listinfo/wine-users

[Index of Archives]     [Gimp for Windows]     [Red Hat]     [Samba]     [Yosemite Camping]     [Graphics Cards]     [Wine Home]

  Powered by Linux