GetModuleFileName mysteries

[Ralf Juengling]

----- Original Message ----- 
From: "Eric Pouech" <pouech-eric at wanadoo.fr>
To: "Ralf Juengling" <juenglin at cse.ogi.edu>
Cc: <wine-devel at winehq.org>
Sent: Tuesday, December 23, 2003 11:05 PM
Subject: Re: GetModuleFileName mysteries


> 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's no easy solution to this, and could lead to even stranger 
> results (like a module trying to peek into itself by trying to open as a 
> file the path returned in GetModuleFileName).

You are saying that the DLLs I built are "builtin DLLs", right? So far I
thought only Wine substitutes of Windows system DLLs are called
"builtin DLLs"...

But what is the reason for having GetModuleFileName return the system
dir for "builtin DLLs"?

Also, why does it behave differently for the two programs, as I reported
in my initial posting; is one of the two cases exhibiting a bug?

Thanks,
Ralf