How to distribute add on XXXX.dll.so ?

[Dewdman42]

I am trying to find the best way to distribute a XXXX.dll.so for general use on wine on OSX. (more specifically the OSX version of wineasio). Right now there is no clean distribution of this very helpful add-on for wine on OSX. There is some src and a binary on github, with manual install instructions that overwhelms some people that want to use it.

There are some technical limitations making it difficult to distribute, but maybe you guys can help me figure out the best way to distribute something like this in general? Wine mechanisms that may be in place to help me script an installer or something...

Are there any mechanisms in wine that make it a bit easier for distributing an installer that can add one of those dll.so's? Here are some of the challenges:

1. It can't be distributed with winetricks because its not stored under the PREFIX, its stored under lib/wine
2. It can't be integrated into wine itself, I don't think, because of Steinberg's asio.h being used, which can't be distributed with the wine src. It has to be built into a binary and distributed as a binary in some way.
3. After manually installing the dll.s into lib/wine, each time a new PREFIX is created, the DLL has to be manually registered with regsvr32, I don't know how to add a dll.so to a wine install so that whenever a new PREFIX is created, it will inherit the DLL as registered and available. Is this possible?
4. I don't know how to determine the location of lib/wine. In cases where env variables are setup, or when wine is located under /usr, its easier to make assumptions, but in the mac world most people are using wineskin or wine bottler or some other distro that has all the wine stuff inside an app bundle and not always in the same dir structure. So I don't know how I can programatically locate the location of lib/wine to install it with an installer, aside from a brute force search. Plus see point#3 above, I wonder if there is a way to install something into a wine install so that each new PREFIX will be able to use it.

[Dewdman42]

so I see that

Code: Select all

wineboot.exe --init

is somehow used to init a new prefix... Its not entirely clear where that is run from when a PREFIX doesn't exist yet. Presumably this copies a bunch of stuff from somewhere, not sure where..to create a registry and builds a drive_c with all the basic stuff that comes with wine. Is there any way to modify the default registry that gets created by wineboot, so that some defaults are maintained with each prefix? if not, is there some way to automatically run a script as a post action to that?