Win to Lin Library Wrapper

[King InuYasha]

On Wed, Feb 18, 2009 at 2:11 AM, Roderick Colenbrander <
thunderbird2k at gmx.net> wrote:

> > On Mon, Feb 16, 2009 at 1:26 PM, Chris Robinson
> > <chris.kcat at gmail.com>wrote:
> >
> > > On Monday 16 February 2009 9:38:19 am Seth Shelnutt wrote:
> > > > I had an interesting thought the other day, and that is to having
> some
> > > > built in support for forwarding windows dlls to linux .so's.
> > >
> > > IIRC, this kind of thing is generally discouraged, except in cases
> where
> > > needed (eg. opengl32). Part of the problem is internal differences..
> for
> > > example, what would a Linux .so do if it's given a Win32 filename path?
> > > Other
> > > problems would be if the Linux equivalent wants a Window for a function
> > > argument and the DLL wants an HWND instead, or if the DLL has
> > > more/different
> > > functions (eg. CUDA on Win32 has functions for dealing with D3D
> objects;
> > > CUDA
> > > on Linux doesn't, and it wouldn't be straight forward to even implement
> > > them
> > > through wined3d).
> > >
> > > Something like OpenGL, and even OpenAL to some degree, would directly
> > > benefit
> > > from having the DLLs forwarded to their host equivalents as it provides
> > > better
> > > access to the hardware and better integration with the host system.
> > > Something
> > > like zlib or ogg/vorbis and stuff wouldn't though, since the code
> should
> > > largely be the same, and save for some bugs/inefficiencies in Wine
> > (which
> > > should be fixed), would work identically.
> > >
> > >
> > >
> > Does Wine yet have the capability to interface with HAL for Win32
> hardware
> > access similar to NT? It looks like it doesn't from all this talk of
> > forwarding DLLs. What we should do instead of trying to forward DLLs,
> > which
> > is asking for more trouble than its worth, is try to get the NT layer to
> > connect to UNIX HAL so that DLLs can link directly to HAL and operate the
> > hardware.
>
> This can't be done. You would be writing your own operating system and
> hardware can't be shared. It is not that hard to write wrapper libraries.
> Second even if libraries look similar between OSes take for instance Cuda it
> does offer OS-specific functionality like e.g. Direct3D integration.
>
> Roderick
> --
> Jetzt 1 Monat kostenlos! GMX FreeDSL - Telefonanschluss + DSL
> für nur 17,95 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K11308T4569a
>

So it wouldn't be possible to hook Wine's Direct3D implementation into
Gallium3D on Linux and use the hardware directly instead of translating it
to OpenGL and then sending it to the hardware?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-devel/attachments/20090218/bb340649/attachment.htm