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
I understand that. I think I didnt explain well enough... In the source version of wine in the tools folder
there is a "wineinstall" script.... I opened this script and changed the variable "prefix" so that it pointed
to the folder on my server that is in actuality the root of a filesystem. After I install I make a compressed
tar.gz of the root file system that gets downloaded of the network by diskless clients. Here in lies my problem.
When I run wine on the server it runs happy but when I run it on a remote client
it looks for its libs at : /opt/pxes-0.7/stock/dist/lib/wine/ntdll.dll.so Which makes since. The directory "dist"
is the distribution level of the root fs. So when it gets compressed the nodes think dist is root ie the libraries
are in the file system there just not in opt/pxes-0.7/stock/dist/lib/wine/ntdll.dll.so they are in fact in /lib
at the root of the ramdisk.......So my question is where is this path stored? since I built from source is it hardcoded in the app?
or is it in a config file somewhere? I ask because I think all I need to do is fix the path and wine will run...
any ideas anyone?
Thanx for the help
-Alex
On Jan 5, 2004, at 10:50 PM, Philippe Anctil wrote:
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
