RE: Is wine portable?
-Original Message- From: Gerald Pfeifer [SMTP:[EMAIL PROTECTED]] Sent: Friday, December 08, 2000 10:39 AM To: Francois Gouget Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: Is wine portable? On Fri, 8 Dec 2000, Francois Gouget wrote: The target of Wine is the regular Linux user who still needs a few Windows applications. s#Linux user#user of Linux, FreeBSD, or some other Unix-like OS# [Glunz Wolfgang] Unfortunately, this doesn't seem to be reality - at least not for the moment. Recently I tried to compile winlib under Sparc-Solaris and was blocked by the usage of x86 specific ASM code in several source modules. Further, I just needed some parts from the EMF device but it seems so that I have to compile all, because the strong coherence - but this is another issue. This is a design issue - should the lib use it's own APIs as much as possible or should the lib call the native OS functions directly if appropriate? I see pros and cons for both ways. One pro - as mentioned - would be the less tighter coupling and thus it would raise the probability that one can pick a piece without need to compile (and port - see above) _all_ the rest. Wolfgang (I agree with the rest, but -- while using Linux by myself (among others) -- I try to reduce Linuxisms...) Gerald -- Gerald "Jerry" [EMAIL PROTECTED] http://www.dbai.tuwien.ac.at/~pfeifer/
just writing EMF files using libwine
Hi wine developers, I'm the developer of pstoedit - a GPLed program that can translate PostScript to a bunch of different vector formats. (www.geocities.com/wglunz/pstoedit/). For Windows platforms I also provide a driver to create EMF files. This driver currently used the Windows-API. More and more I get requests whether I couldn't provide this EMF driver also on non-Windows platforms, e.g. Sun Solaris (Sparc) or HP-UX or Linux (here as native Linux application, not as .exe). Now I tried to use libwine but have the following problems / questions: Without any change, libwine.a doesn't compile on Solaris-Sparc. I needed to comment out some assembler parts. Question: is libwine not intended to be usable also on non Intel platforms ? The libwine.a as produced by "make libwine.a" doesn't contain the needed GDI calls like: Rectangle Polyline SetTextAlign CreateBrushIndirect CreateMetaFileA So I need e.g. also libgdi32.so - right ? How can I "make" this without building whole wine ? Configure doesn't seem to have an option for this (just for the libwine.a/so) Also libgdi32.so doesn't compile under Solaris-Sparc (using gcc) - same problem with assembler code as above. So I searched for the functions that I need and found most of them in the graphics/enhmetafiledrv directory. Unfortunately, these are not exactly the effective Win32 functions, but instead some internal functions that are called via the upper GDI layer. Now it get's a bit frustrating. It seems so that I need to build lot's of wine (and this doesn't work under Solaris-Sparc due to the assebmler code) just to be able to use the GDI functions that write to a Metafile. Question: isn't there a more direct way I can build just the parts that I need to write a Metafile ? I even cannot imagine why the code to write a Metafile is so platform dependent. Is there a way to get a GDI that supports just metafiles and omit all the stuff that isn't needed ? Any help is greatly appreciated. Wolfgang
