🚀 go-pugleaf

"Nick B. Cassos" <nbc@no_spam.ath.forthnet.gr> wrote:
> I think, you should start with GetModuleFileName() to obtain the path
> of your DLL's process. Armed with this info, you can follow Window's
> logic to look first in the process's directory, then the current one,
> system, windows, and anything in the PATH environment string. If there
> are 2 or more instances of your DLL in several directories then I give
> up.

GetModuleFileName returns the fully-qualified filename, so there's no need
to search any paths.  Simply pass this API the HINSTANCE that the OS passes
to you in DllMain:

BOOL WINAPI DllMain
    ( HINSTANCE hinstDLL
    , DWORD dwReason
    , LPVOID lpvReserved )
    {
    switch( dwReason )
        {
        case DLL_PROCESS_ATTACH:
            {
            std::vector< char > path( MAX_PATH + 1 );
            Win32Check( GetModuleFileName
                ( reinterpret_cast< HMODULE >( hinstDLL )
                , &*path.begin()
                , path.size( ) ) );
            /* Note: you should really use a loop to handle
                paths longer than MAX_PATH, but that's an
                exercise for the reader :-) */
            }
        }
    }

--
-- Early Ehlinger CEO, ResPower Inc - Toll-Free : 866-737-7697
-- www.respower.com -- 500+ GHz Supercomputer Starting At USD$0.50/GHz*Hour