Search results

From WineHQ Wiki
Jump to: navigation, search

Page title matches

  • ...bugging in Wine, here's a small overview of process and thread handling in Wine. It has to be clear that there are two different beasts: processes/threads === Wine, debugging and WineDbg ===
    59 KB (9,362 words) - 20:06, 9 February 2016
  • === I. Developing Wine === ====[[Wine Developer's Guide/Debugging Wine|1. Debugging Wine]]====
    10 KB (1,291 words) - 17:05, 7 February 2016
  • To better manage the large volume of debugging messages that Wine can generate, we divide the messages on a component basis, and classify the : Messages in this class indicate serious errors in Wine, such as as conditions that should never happen by design.
    10 KB (1,668 words) - 05:50, 6 October 2016
  • With these limitations in mind, it is possible to implement more stubs in Wine and, eventually, the functions themselves. <li><p>If you found that something broke between wine-1.1.42 and wine-1.1.44 (these are [WWW] release tags). To start regression testing we run:<
    10 KB (1,774 words) - 11:48, 8 February 2016
  • ...Wine, that you should be aware of before doing any serious development in Wine. ...ia email to the Wine patches mailing list, [mailto:wine-patches@winehq.org wine-patches@winehq.org]. Your patch should include:
    10 KB (1,836 words) - 00:22, 22 November 2016
  • ...ll undertaking. Fortunately it can prove very useful to the development of Wine way before it is complete. <p>However, one must remember that the goal of Wine is to run Windows applications on Linux, not to be a clone of any specific
    21 KB (3,598 words) - 11:59, 8 February 2016
  • This chapter describes how you can help improve Wine documentation. ...reating tests, providing organizational assistance, or helping to document Wine.
    19 KB (3,087 words) - 12:19, 8 February 2016
  • Brief overview of Wine architecture... == Wine Overview ==
    28 KB (4,300 words) - 12:27, 8 February 2016
  • This section covers the kernel modules. As already stated, Wine implements the NT architecture, hence provides <tt>NTDLL</tt> for the core == The Wine initialization process ==
    80 KB (13,874 words) - 12:41, 8 February 2016
  • ...ways (though not in others). Accordingly they are stored separately under Wine. ...internal layout of the global handle HACCEL (16 and 32) in Windows 95 and Wine. Exposed to the user as Win16 global handles HACCEL16 and HACCEL32 by the W
    20 KB (3,194 words) - 14:57, 11 January 2018
  • == Writing COM Components for Wine == ...s compatible via padding but unfortunately the one which is imposed to the Wine emulator by the Windows binaries, i.e. the Visual C++ one, is the most comp
    44 KB (7,356 words) - 13:36, 24 February 2016
  • == What is needed to have OpenGL support in Wine == If, after Wine compiles, OpenGL support is not compiled in, you can always check <tt>confi
    6 KB (1,107 words) - 12:58, 8 February 2016
  • <code>User</code> provides for DirectDraw capabilities based on drawing to a Wine window. It uses the <code>User</code> DirectDrawSurface implementation for
    5 KB (756 words) - 13:00, 8 February 2016
  • ...e contains information about the implementation of the multimedia layer of Wine. ...es between kernel and user drivers has changed, but it doesn't impact much Wine. Those changes allow some good things (like kernel mixing, where different
    21 KB (2,853 words) - 13:05, 8 February 2016

Page text matches

  • ...''Q'''uestions, covers general topics about Wine. For questions related to Wine software development, see the [[Developer FAQ]]. ...], [[#Can I store the virtual Windows installation somewhere other than ~/.wine?|using a wineprefix]], [[#How do I create a 32 bit wineprefix on a 64 bit s
    73 KB (12,177 words) - 12:14, 27 December 2017
  • Winecfg is a GUI configuration tool for Wine, designed to make life a little easier than editing the registry. ...to applications that ask for it. Generally, this setting does not change Wine's behavior. If an application never asks for this version information, it
    9 KB (1,474 words) - 05:33, 12 September 2016
  • ...o use --with-wine-tools to point to a plain old 32-bit build of wine. This guide uses [https://en.wikipedia.org/wiki/LXC LXC] (chroot is another option) and * Build 64-bit wine
    9 KB (1,473 words) - 12:28, 27 January 2016
  • Interested in compiling wine from source? Want to submit some patches, run a bisection, or maybe just in ...a single line of ANSI C, there are a few things you need in order to build wine successfully.
    31 KB (5,092 words) - 19:43, 6 February 2017
  • ...interested in contributing code to Wine, getting started can be daunting. Wine is an ambitious project, with a large codebase, a lot of history, and a str ...wiki page has some ideas about [[Main_Page#Contribute|contributing to the Wine Project]].
    5 KB (860 words) - 20:16, 10 February 2016
  • == Writing Tasks for Wine == ...nd writing good documentation. Understanding the actual code that makes up Wine should only be necessary if you want to help make documentation for develop
    5 KB (758 words) - 16:20, 29 February 2016
  • This FAQ covers topics related to software development within the Wine project. For other topics, see our main [[FAQ]]. === How do I become a Wine developer? What do I need to know? ===
    14 KB (2,353 words) - 07:55, 3 January 2018
  • ...osis and support two closely related activities that are very important to Wine. We can always use more people willing to respond to issues that pop up on * General Wine issues and questions can usually be answered in a direct reply, using the s
    15 KB (2,516 words) - 17:19, 29 February 2016
  • == Installing Wine == ...all your distribution's included package versions and update to the latest Wine version available here.
    7 KB (1,232 words) - 18:42, 16 November 2016
  • Certain types of bugs that pop up in Wine follow a pattern. This is a collection of tips that different developers ha ...n it isn't. Managed vs unmanaged is a rather difficult problem, ask on the wine-devel list for help if you wish to change the mode heuristics.
    5 KB (928 words) - 21:50, 28 February 2016
  • ...rder to review code better and use established lines of communication, the Wine project accepts code in the form of patch files (instead of pushing directl ...ment], your patches probably won't be accepted. This is to ensure that the Wine project does not violate any copyrights belonging to Microsoft. Some more n
    13 KB (2,182 words) - 10:06, 13 November 2017
  • == Wine conformance tests == Wine builds a set of [[Unit Test Suites|unit tests]] that check the behavior of
    11 KB (1,916 words) - 13:02, 4 March 2016
  • Writing cmd tests is a bit different than writing standard wine tests. ...tten in C, but directly in the form of batch files, which are processed by wine cmd, then compared line by line to the associated expected result files.
    5 KB (811 words) - 11:31, 23 January 2016
  • == How is Wine translated? == ...al consistency and spelling issues on the [http://fgouget.free.fr/wine-po/ Wine PO] site.
    18 KB (3,073 words) - 13:55, 25 December 2017
  • ...erence guide. This guide is for both the new Wine user and the experienced Wine user, offering full step-by-step installation and configuration instruction If, after examining this guide, the [[FAQ]], and other relevant documentation there is still something you
    76 KB (12,627 words) - 11:22, 27 December 2017
  • === I. Developing Wine === ====[[Wine Developer's Guide/Debugging Wine|1. Debugging Wine]]====
    10 KB (1,291 words) - 17:05, 7 February 2016
  • <metadesc>Foire aux questions (FAQ) en français de Wine</metadesc> ...ts sujets relatifs à Wine. Pour les questions liées au développement de Wine, voyez la [[Developer FAQ|FAQ de développement]].
    97 KB (15,549 words) - 06:36, 10 September 2016
  • This chapter describes how you can help improve Wine documentation. ...reating tests, providing organizational assistance, or helping to document Wine.
    19 KB (3,087 words) - 12:19, 8 February 2016
  • #REDIRECT [[Wine Developer's Guide]]
    36 bytes (4 words) - 11:22, 26 February 2016
  • MIDI should work in Wine as long as it works on your system in general, with some caveats. There is no point in writing to the Wine bug tracker if MIDI does not work on your UNIX system.
    7 KB (1,202 words) - 20:08, 29 February 2016

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)