[Mono-winforms-list] Re: win32 api dlls
Yrjana Rankka
ghard@openlinksw.com
24 Apr 2003 12:33:32 +0200
Agreed. A build script could use wget or similar util to get the dated
target snapshot from Wine.
Then apply the patches, make shared objects and place them in a distrib
directory in the build.
Another script to install these in place and we're go.
Yrjänä
On Wed, 2003-04-23 at 22:01, Miguel de Icaza wrote:
> Hello!
>
> > I think this made diffs with all files, which are absent in directory with
> > my modified wine,
> > but present in native wine
> >
> > Actually my new wine is much less and is cut down for required directories
> > only.
> > so for instance - I have 7 dlls, but native wine - much more - 83 !.
> > Mono does not need them (at least for now)
>
> Am glad that you got diff working, those are good news.
>
> Now, to be able to move forward, the best way to approach this is to a
> list of your changes, so we can maintain these changes until all of them
> have been integrated into Wine proper.
>
> To achieve this, it is important that Mono users be able to:
>
> * Download a pristine and official Wine release.
>
> * Apply the Mono patch.
>
> * Build and install (possibly to a different prefix, if needed)
>
> To reach that goal, we should not trim down Wine and distribute a
> trimmed down wine, because that would force upon us the maintenance of
> it, which we are not ready to do.
>
> Could you hence recreate the missing files from the original
> distribution, or apply your changes to a pristine Wine, so we can get a
> usable patch?
>
> Miguel
--
Yrjana Rankka // ghard@openlinksw.com
Developer // http://www.openlinksw.com
OpenLink Software Ltd //
ODBC, XML & E-Business Infrastructure Technology Providers