Re: Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set

[Alexandre Julliard]

Dmitry Timoshkov <dmitry(a)sloboda.ru> writes:
> Dmitry Timoshkov <dmitry(a)codeweavers.com>
>     Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set.

I think it would be better to keep the existing support for native
dlls, and simply fall back to loading the builtin library if
SearchPath fails. It's unlikely we are ever going to support proper
LOAD_LIBRARY_AS_DATAFILE for builtin dlls anyway.

-- 
Alexandre Julliard
julliard(a)winehq.com

Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set

[Dmitry Timoshkov]

"Alexandre Julliard" <julliard(a)winehq.com> wrote:
> I think it would be better to keep the existing support for native
> dlls, and simply fall back to loading the builtin library if
> SearchPath fails. It's unlikely we are ever going to support proper
> LOAD_LIBRARY_AS_DATAFILE for builtin dlls anyway.

But here is a problem. This doesn't honor a load order. If load order
of a requested dll explicitly specified as 'builin' but 'native' library
there is somewhere in the path, then we will get unexpected result.
How to cope with it?

At least DONT_RESOLVE_DLL_REFERENCES should be doable.

Allow loading of built-in dlls with LOAD_LIBRARY_AS_DATAFILE flag set

[Dmitry Timoshkov]

"Alexandre Julliard" <julliard(a)winehq.com> wrote:
> I think it would be better to keep the existing support for native
> dlls, and simply fall back to loading the builtin library if
> SearchPath fails.

Does the attached patch look as applicable?