Vijay Kiran Kamuju
infyquest at gmail.com
Fri Jun 16 10:12:43 CDT 2006
The libgdiplus for mono is implementing things quite differently.
I think its only working with mono.
We need to modify our wine code so that it works with mono. (You must
really ask Julliard for this) or modify libgdiplus of mono to work
What I am saying is why re-invent the wheel, its already implemented
by mono project or we can keep a modified version of libgdiplus in our
sources. (This might cause some problems if you have mono installed).
Regarding the stub dll, how does mono install the gdiplus, if it
install the gdiplus as gdiplus.dll.so, it might be a problem.
Those are all my concerns.
On 6/16/06, Steven Edwards <winehacker at gmail.com> wrote:
> On 6/15/06, Vijay Kiran Kamuju <infyquest at gmail.com> wrote:
> > I think we rather use mono project's libgdiplus(gdiplus.dll
> > implementation) than a stub implementation.
> > This will help in later implementing the .Net Compatibility Layer to Wine.
> What do you mean? I looked at this before and even if we are to use
> libgdiplus we need some way to wrap it in a way the Windows app
> expects. I tried to make a stub wrapper that dlopened libgdiplus and
> forwarded the calls but I kept running in to some sort of problem. In
> any case I don't see whats wrong with accepting this stub dll. It will
> force us to implement it rather than depending on the Microsoft
> version of the dll.
> Steven Edwards
> "There is one thing stronger than all the armies in the world, and
> that is an idea whose time has come." - Victor Hugo
More information about the wine-patches