On Wed, Feb 4, 2009 at 1:07 PM, Austin English <austinenglish@xxxxxxxxx> wrote: > On Wed, Feb 4, 2009 at 12:03 PM, Charity Abbott <angeliqer@xxxxxxxxx> wrote: >> On Wed, Feb 4, 2009 at 12:39 PM, Austin English <austinenglish@xxxxxxxxx> wrote: >>> On Wed, Feb 4, 2009 at 11:35 AM, antoniong <wineforum-user@xxxxxxxxxx> wrote: >>>> Is there absolutelu no (unofficial) way to detect whether a programm is running using Wine? >>>> >>>> In this way a programm could decide to use other routines for those features that do not work fine using Wine. >>>> >>>> >>>> >>>> >>>> >>>> >>> >>> There are several ways, but it's not recommended. If wine fixes those >>> bugs in the future, the program may break. File bugs, write testcases >>> and get the bug fixed properly. >>> >>> -- >>> -Austin >>> >>> >> >> This is done in a round about way already. Lots of programs >> (especially games) come with configuration files that turn features on >> and off. AppDB tells you what configuration works. The only downside >> to this is the user has to know enough to set it up properly. If a >> programmer wanted to make it easier for a program to run on Linux, it >> really should be ported to Linux rather than working through wine. >> Wine is mainly for those uncooperative programmers. >> >> > > Not necessarily. It takes a lot more effort, money and time to port to > a native Linux app. That also leaves OS X/FreeBSD/OpenSolaris users > out in the cold. > > Tweaking an app to work both on Wine and Windows is *much* easier. > > -- > -Austin > I would disagree with that unless you're talking about low level hardware drivers or programs written in assembly. Most of the time, it just involves interface translation to OpenGL and recompiling for the architecture. The process for that varies greatly depending on the program. For some apps, it would be very minimal. For games or 3D graphic driven programs, it would be more complex.
