If the APIs use a C system calling convention, there is no reason why we
couldn't create a DLL that worked with both EMX and VACPP.
So maybe it is just a build problem?
Mike
Henry Sobotka wrote:
> Michael Kaply wrote:
> >
> > I believe the solution to these problems is not to rename the DLLs but
> > to figure out why Warpzilla cannot use the "standard" versions of these
> > DLLs.
> >
> > I'm asking for help here in figuring this out.
>
> I did a emx build yesterday with the versions generally used with
> XFree86/2; right now JPEGs work, but not PNGs and it looks like that's
> just due to my having a screwed-up zlib installation here.
>
> If renaming is out, I don't think anything can be done about the
> conflict between the vacpp and emx versions of those DLLs other than to
> tell people to expect problems if they simultaneously run a (vacpp)
> Warpzilla and XFree86/2 or any app that uses the emx versions of those
> libraries.
>
> h~
