Re: GetModuleFileName mysteries

2003-12-31 Thread Alexandre Julliard
Boaz Harrosh <[EMAIL PROTECTED]> writes: > Until recently 95% of the work was done on wine. WineLib was a side effect. > Look what happens, if I have a "-wrap" application (C++) I need to > place a link to it in WINEDLLPATH to even load. and also to all it's > supporting DLLs (I know I have 36 of

Re: GetModuleFileName mysteries

2003-12-31 Thread Tom
Boaz Harrosh wrote: And while we are at it. What is the wine policy about Built-in DLLs versions. I have encountered problems where setups where complaining about versions been "0.0.0.0" and also some other not high enough versions. Should we make a quick study about Windows versions and serve

Re: GetModuleFileName mysteries

2003-12-31 Thread Boaz Harrosh
Well there is now! Until recently 95% of the work was done on wine. WineLib was a side effect. Look what happens, if I have a "-wrap" application (C++) I need to place a link to it in WINEDLLPATH to even load. and also to all it's supporting DLLs (I know I have 36 of them). If any one is working

Re: GetModuleFileName mysteries

2003-12-30 Thread Alexandre Julliard
"Ralf Juengling" <[EMAIL PROTECTED]> writes: > But what is the reason for having GetModuleFileName return the system > dir for "builtin DLLs"? Because we don't know the real path, and even if we did there is no guarantee that it is accessible from a Windows drive. > Also, why does it behave diff

Re: GetModuleFileName mysteries

2003-12-24 Thread Ralf Juengling
- Original Message - From: "Eric Pouech" <[EMAIL PROTECTED]> To: "Ralf Juengling" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, December 23, 2003 11:05 PM Subject: Re: GetModuleFileName mysteries > basically, because for buil

Re: GetModuleFileName mysteries

2003-12-24 Thread Eric Pouech
Well yes ... and ... I don't get it I ask for foo.dll.so (GetModuleFileName) please give it to me. What is this problems here? I would like to look into my self. Any problems with that? Usually I Just need to know the full path of the Installation. Built in or not give me the file strait, no Ic

Re: GetModuleFileName mysteries

2003-12-24 Thread Boaz Harrosh
Eric Pouech wrote: basically, because for builtin DLLs, the real file (foo.dll) doesn't exist (only foo.dll.so does). So, we decided to return all builtin DLLs in the system dir. Note that this only applies to builtin DLLs, native DLLs will return the correct path in GetModuleFileName. There'

Re: GetModuleFileName mysteries

2003-12-24 Thread Eric Pouech
Ralf Juengling wrote: I have some Windows code that uses GetModuleFileName in order to read some additional files at runtime that are expected at certain place relative to the executable. In Wine, GetModuleFileName doesn't work as intended, and I have trouble to track down the problem. I had to u

GetModuleFileName mysteries

2003-12-22 Thread Ralf Juengling
I have some Windows code that uses GetModuleFileName in order to read some additional files at runtime that are expected at certain place relative to the executable. In Wine, GetModuleFileName doesn't work as intended, and I have trouble to track down the problem. I had to use winemaker's "wrap"