You haven't applied this patch either.
This is more understandable since I'm
not 100% happy with it either eventhough
it is IMHO better then nothing.
Ultimately it would be good to specificy
which module to test as builtin or native
at runtime.
This would presumably require quite a lot
of work since it would require unloading the
old and reloading the new module at runtime
so this might not be so easy.
Of course even the abillity to specify it once
before the first loading of module would be
useful like:
BEGIN {
require wine;
&wine::module_native("wininet");
&wine::module_builtin("imm32", "msacm32");
}
use imm32;
use msacm32;
use wininet;
This can perhaps be easily done by abusing
MODULE_AddLoadOrderOption?
What do you say? Do you think such a feature
would be useful?
Do you think the slightly more advanced feature
with hotswapping native/builtin would be useful
as well?
This would allow the test to compare the results
of builtin/native in the same run.
What about applying the patch below in the meantime?
---8<---
*** runtest
* Make.rules.in,
programs/winetest/runtest:
- Made runtest "use strict"
- Added new option -M to specify which DLL:s (modules)
that should be tested as builtin regardless of
the settings in ~/.wine/config.
Attachment:
runtest.diff
Description: Binary data
