I was looking at entry C.5 of the 0.9 Todo list: "Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg [TODO]"
Upon first glance I figured the approach is to (not necissarily in this order): add regsvr32.exe calls in the installation scripts, fill in the DllRegisterServer (and DllUnregisterServer) sections of the appropriate libraries, and remove those entries from winedefault.reg.
About a dozen dll files have their names in winedefault.reg. So I checked the native versions of these files, and only half of them have a DllRegisterServer function. I did some further research and found that perhaps DllInstall was what I needed. Well, that only adds one library, and two have *both* functions.
Does anyone have any better ideas on what the "Right Way" to tackle this item is? I am sure that adding external functions that do not exist in native versions is *not* the way.
-- Jeff S
_________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
On December 4, 2002 01:36 pm, Jeff Smith wrote:
Does anyone have any better ideas on what the "Right Way" to tackle this item is? I am sure that adding external functions that do not exist in native versions is *not* the way.
This was Alexandre's idea. Alexandre, a more detailed brain dump on the configuration stuff would be useful. For example:
C.1 Merge configuration into the registry
Any gochas? What would it take?
C.5 Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg
How should this be implemented? See Jeff's questions.
C.6 Write wine.inf script to setup a new Wine installation
Do we have the code that executes .inf scripts? Is this one just a matter of writing the scripts?
"Dimitrie O. Paun" dpaun@rogers.com writes:
C.1 Merge configuration into the registry
Any gochas? What would it take?
Not much, it basically means making the Wine/Config branch into a normal registry branch. It's more a user interface issue, we need tools to edit it because you don't want to make users dig through system.reg manually.
C.5 Make Wine's DLLs register themselves to avoid manual merging of the winedefault.reg
How should this be implemented? See Jeff's questions.
Part of it should be done with DllRegisterServer, the rest can be handled by the .inf script. And I think it's OK to add the necessary DllRegisterServer entry points even if the native dll doesn't have them.
C.6 Write wine.inf script to setup a new Wine installation
Do we have the code that executes .inf scripts? Is this one just a matter of writing the scripts?
It should be, setupapi should support everything we need for that. The main missing feature is the user interface feedback on the install progress, but we can probably live without that at first.
--- Alexandre Julliard julliard@winehq.com wrote:
"Dimitrie O. Paun" dpaun@rogers.com writes:
C.1 Merge configuration into the registry
Any gochas? What would it take?
Not much, it basically means making the Wine/Config branch into a normal registry branch. It's more a user interface issue, we need tools to edit it because you don't want to make users dig through system.reg manually.
You guys have got the ReactOS regedit based on Wine Regedit although it is read only atm. If someone is still planning on adopting it, then that will solve this part of the problem.
Thanks Steven
__________________________________________________ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com
On December 6, 2002 10:18 am, you wrote:
You guys have got the ReactOS regedit based on Wine Regedit although it is read only atm. If someone is still planning on adopting it, then that will solve this part of the problem.
I was looking into it, but it requires a bit of work until is ready for integration. However, I don't think this is what Alexandre had in mind.
Jaco was working on a cool too, I don't know what the status of that is: http://www.dssd.ca/wine/winecfg1.png http://www.dssd.ca/wine/winecfg2.png