diff --git a/assets/wine/share/applications/wine.desktop b/assets/wine/share/applications/wine.desktop deleted file mode 100644 index e76dd0d..0000000 --- a/assets/wine/share/applications/wine.desktop +++ /dev/null @@ -1,32 +0,0 @@ -[Desktop Entry] -Type=Application -Name=Wine Windows Program Loader -Name[ar]=منظومة واين لتشغيل برامج وندوز -Name[cs]=Zavaděč programů pro Wine -Name[de]=Wine Windows-Programmstarter -Name[es]=Wine - Cargador de programas de Windows -Name[lt]=Wine Windows programų paleidyklė -Name[nl]=Wine Windows programmalader -Name[sv]=Wine Windows Programstartare -Name[ro]=Wine - Încărcătorul de programe Windows -Name[ru]=Wine - загрузчик Windows программ -Name[uk]=Wine - завантажувач Windows програм -Name[fr]=Wine - Chargeur de programmes Windows -Name[ca]=Wine - Carregador d'aplicacions del Windows -Name[pt]=Carregador de aplicativos Windows Wine -Name[pt_br]=Carregador de aplicativos Windows Wine -Name[it]=Wine Carica Programmi Windows -Name[da]=Wine, Programstarter til Windows-programmer -Name[nb]=Wine - for kjøring av Windows-programmer -Name[nn]=Wine - for køyring av Windows-program -Name[sr]=Wine - дизач Windows програма -Name[sr@latin]=Wine - dizač Windows programa -Name[tr]=Wine - Windows programı yükleyicisi -Name[hr]=Wine - dizač Windows programa -Name[he]=Wine — מריץ תכניות Windows -Name[ja]=Wine Windowsプログラムローダー -Exec=wine start /unix %f -MimeType=application/x-ms-dos-executable;application/x-msi;application/x-ms-shortcut;application/x-bat;application/x-mswinurl -Icon=wine -NoDisplay=true -StartupNotify=true diff --git a/assets/wine/share/man/de.UTF-8/man1/wine.1 b/assets/wine/share/man/de.UTF-8/man1/wine.1 deleted file mode 100644 index 2cd129c..0000000 --- a/assets/wine/share/man/de.UTF-8/man1/wine.1 +++ /dev/null @@ -1,278 +0,0 @@ -.\" -*- nroff -*- -.TH WINE 1 "November 2007" "Wine 10.17" "Windows On Unix" -.SH NAME -wine \- Windows-Programme auf Unix-Systemen ausführen -.SH ÜBERSICHT -.B wine -.IR Programm " [" Argumente ] -.br -.B wine --help -.br -.B wine --version -.PP -Für das Übergeben von Kommandos an Windows-Programme siehe den -Abschnitt -.B PROGRAMM/ARGUMENTE -in dieser Manpage. -.SH BESCHREIBUNG -.B wine -lädt und führt ein Windows-Programm aus. Dieses Programm kann ein -beliebiges DOS/Win3.1/Win32-Programm sein; es wird nur die -x86-Architektur unterstützt. -.PP -Um wine zu debuggen, nutzen Sie anstelledessen das Kommando -.BR winedbg . -.PP -Um rein kommandozeilenbasierte Programme auszuführen, nutzen Sie -.B wineconsole -anstelle von -.BR wine . -Wenn Sie nicht -.B wineconsole -für CLI-Programme nutzen, kann dies dazu führen, dass das Programm -nicht korrekt ausgeführt werden kann. -.PP -Wenn wine nur mit -.B --help -oder -.B --version -als Argument aufgerufen wird, wird -.B wine -nur einen kleinen Hilfetext oder die Version ausgeben und sich beenden. -.SH PROGRAMM/ARGUMENTE -Der Programmname kann auf DOS-Art -.RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE ) -oder auf UNIX-Art angegeben werden -.RI ( /msdos/windows/sol.exe ). -Sie können Argumente an die Windows-Anwendung übergeben, indem Sie -sie einfach an den wine-Befehl anhängen (z. B.: -.IR "wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT" ). -Sie müssen unter Umständen Sonderzeichen und/oder Leerzeichen -mit '\(rs' maskieren, wenn Sie wine über die Kommandokonsole aufrufen, -z.B. -.PP -wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe -.PP -.SH UMGEBUNGSVARIABLEN -.B wine -leitet die Umgebungsvariablen der Shell, in der es gestartet wurde, an -die Windows-Applikation weiter. Um eine für Ihre Applikation nötige -Variable zugänglich zu machen, folgen Sie der Anleitung Ihrer Shell zu -Umgebungsvariablen. -.TP -.B WINEPREFIX -Wenn gesetzt, wird dieser Ordner als Speicherort für die -Konfigurationsdateien von -.B wine -genutzt. Die Standardeinstellung ist -.IR $HOME/.wine . -Dieser Ordner wird auch für den UNIX-Socket zur Kommunikation mit -.IR wineserver . -genutzt. Alle -.B wine --Prozesse, die den gleichen -.B wineserver -nutzen (z.B. Prozesse desselben Nutzers) teilen sich bestimmte Objekte -wie die Registry, Arbeitsspeicher und die Konfigurationsdateien. Mit -dem Setzen von -.I WINEPREFIX -beim Starten verschiedener -.B wine --Prozesse ist es möglich, eine Anzahl vollkommen unabhängiger -.B wine --Prozesse zu starten. -.TP -.B WINESERVER -Gibt den Ort der -.B wineserver --Anwendung an. Wenn diese Variable nicht gesetzt ist, sucht -.B wine -in $PATH und anderen Orten nach wineserver. -.TP -.B WINEDEBUG -Wählt die Stufe der Debug-Meldungen aus. Die Variable hat das Format -.RI [ Klasse ][+/-] Kanal [,[ Klasse2 ][+/-] Kanal2 ]. -.RS +7 -.PP -.I Klasse -ist optional und kann z.B. folgende Werte annehmen: -.BR err , -.BR warn , -.BR fixme , -oder -.BR trace . -Wenn -.I class -nicht angegeben ist, werden alle Debugmeldungen dieses Kanals -ausgegeben. Jeder Kanal gibt Meldungen einer bestimmten -.BR wine . --Komponente aus. Das folgende Zeichen kann entweder + oder - sein, je -nachdem ob der Kanal ein- oder ausgeschaltet werden soll. Wenn keine -.I Klasse -angegeben ist, kann das führende + weggelassen werden. In WINEDEBUG -sind keine Leerzeichen erlaubt. -.PP -Beispiele: -.TP -WINEDEBUG=warn+all -zeigt alle Nachrichten der Kategorie "warning" an (empfohlen zum -Debuggen). -.br -.TP -WINEDEBUG=warn+dll,+heap -schaltet alle DLL-Meldungen der Kategorie "warning" sowie jegliche -Heap-Meldungen an. -.br -.TP -WINEDEBUG=fixme-all,warn+cursor,+relay -schaltet alle FIXME-Nachrichten ab, Zeigernachrichten der Kategorie -"warning" an und schaltet alle Relay-Meldungen (API-Aufrufe) an. -.br -.TP -WINEDEBUG=relay -schaltet alle Relay-Nachrichten an. Für mehr Kontrolle über die im -Relaytrace angezeigten DLLs und Funktionen siehe den [Debug]-Abschnitt -der Wine-Konfigurationsdatei. -.PP -Für mehr Informationen zu den Debug-Meldungen siehe den Abschnitt -.I Running Wine -im Wine-Benutzerhandbuch. -.RE -.TP -.B WINEDLLPATH -Gibt den Pfad/die Pfade an, in denen wine nach eigenen DLLs und -Winelib-Anwendungen sucht. Die Einträge der Liste werden mit einem ":" -getrennt. -.TP -.B WINEDLLOVERRIDES -Definiert die Bibliotheksüberschreibung und Ladereihenfolge der DLLs, -die beim Laden jeder DLL berücksichtigt wird. Derzeit gibt es zwei Typen von -DLLs, die in den Speicher eines Prozesses geladen werden können: -Native Windows-DLLs -.RI ( native ), -und -.B wine --interne DLLs -.RI ( builtin ). -Der Typ kann mit dem ersten Buchstaben abgekürzt werden -.RI ( n ", " b ). -Jede Anweisungssequenz muss mit einem Komma abgeschlossen werden. -.RS -.PP -Jede DLL kann ihre eigene Ladereihenfolge besitzen. Die -Ladereihenfolge bestimmt, welche DLL-Version als erste geladen werden -soll. Wenn die erste versagt, ist die nächste an der Reihe und so -weiter. Viele DLLs mit derselben Reihenfolge können durch Kommata -getrennt werden. Es ist auch möglich, mit dem Semikolon verschiedene -Reihenfolgen für verschiedene DLLs festzulegen. -.PP -Die Ladereihenfolge für eine 16bit-DLL wird immer durch die -Reihenfolge der 32bit-DLL bestimmt, die sie enthält. Diese 32bit-DLL -kann durch Ansehen des symbolischen Links der 16bit .dll.so-Datei -gefunden werden. Wenn zum Beispiel ole32.dll als "builtin" eingestellt -ist, wird storage.dll ebenfalls als "builtin" geladen, da die -32bit-DLL ole32.dll die 16bit-DLL storage.dll enthält. -.PP -Beispiele: -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n,b" -.br -Versuche, die DLLs comdlg32 und shell32 als native Windows-DLLs zu -laden; wenn dies fehlschlägt, soll Wine die mitgebrachte Version -benutzen. -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b" -.br -Versuche, die DLLs comdlg32 und shell32 als native Windows-DLLs zu -laden. Weiterhin, wenn eine Anwendung versucht, die DLL -c:\(rsfoo\(rsbar\(rsbaz.dll zu laden, soll wine die eingebaute DLL baz -verwenden. -.TP -WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n" -.br -Versuche, die mitgebrachte comdlg32-Bibliothek zu laden; wenn dies -fehlschlägt soll Wine die native comdlg32-DLL nutzen. Bei shell32 soll -immer die mitgebrachte Version verwendet werden; bei comctl32 immer -die native. -.RE -.TP -.B DISPLAY -Gibt das zu nutzende X11-Display an. -.TP -OSS sound driver configuration variables -.TP -.B AUDIODEV -Gerät für Audio-Ein-/Ausgabe festlegen. Standard: -.BR /dev/dsp . -.TP -.B MIXERDEV -Audiomixer-Gerät festlegen. Standard: -.BR /dev/mixer . -.TP -.B MIDIDEV -MIDI-Sequencergerät festlegen. Standard: -.BR /dev/sequencer . -.SH DATEIEN -.TP -.I wine -Der -.B wine --Programmstarter -.TP -.I wineconsole -Der -.B wine --Programmstarter für Konsolenapplikationen (CLI) -.TP -.I wineserver -Der -.B wine --Server -.TP -.I winedbg -Der -.B wine --Debugger -.TP -.I $WINEPREFIX/dosdevices -Dieser Ordner enthält die DOS-Gerätezuweisungen. Jede Datei in diesem -Ordner ist ein Symlink auf die Unix-Gerätedatei, die dieses Gerät -bereitstellt. Wenn zum Beispiel COM1 /dev/ttyS0 repräsentieren soll, -wird der Symlink $WINEPREFIX/dosdevices/com1 -> /dev/ttyS0 benötigt. -.br -DOS-Laufwerke werden auch mit Symlinks angegeben. Wenn z.B. das -Laufwerk D: dem CD-ROM-Laufwerk entsprechen soll, das auf /mnt/cdrom -eingebunden ist, wird der Link $WINEPREFIX/dosdevices/d: -> /mnt/cdrom -benötigt. Es kann auch die Unix-Gerätedatei angegeben werden; der -einzige Unterschied ist der "::" anstelle dem einfachen ":" im Namen: -$WINEPREFIX/dosdevices/d:: -> /dev/hdc. -.SH AUTOREN -.B wine -ist dank der Arbeit vieler Entwickler verfügbar. Für eine Liste siehe -die Datei -.B AUTHORS -im obersten Ordner der Quellcodedistribution. -.SH COPYRIGHT -.B wine -kann unter den Bedingungen der LGPL genutzt werden; für eine Kopie der -Lizenz siehe die Datei -.B COPYING.LIB -im obersten Ordner der Quellcodedistribution. -.SH FEHLER -.PP -Statusberichte für viele Anwendungen sind unter -.I https://appdb.winehq.org - verfügbar. Bitte fügen Sie Anwendungen, die Sie mit Wine nutzen, der - Liste hinzu, sofern noch kein Eintrag existiert. -.PP -Fehler können unter -.I https://bugs.winehq.org -gemeldet werden. -.SH VERFÜGBARKEIT -Die aktuellste öffentliche Wine-Version kann auf WineHQ, -.UR https://www.winehq.org/ -die Hauptseite der wine-Entwicklung -.UE , -bezogen werden. -.SH "SIEHE AUCH" -.BR wineserver (1),\ winedbg (1) diff --git a/assets/wine/share/man/de.UTF-8/man1/winemaker.1 b/assets/wine/share/man/de.UTF-8/man1/winemaker.1 deleted file mode 100644 index 99dd52a..0000000 --- a/assets/wine/share/man/de.UTF-8/man1/winemaker.1 +++ /dev/null @@ -1,264 +0,0 @@ -.\" -*- nroff -*- -.TH WINEMAKER 1 "Januar 2012" "Wine 10.17" "Wine Entwicklerhandbuch" -.SH NAME -winemaker \- Erzeugt eine Build-Infrastruktur, um Windows Programme unter Unix zu kompilieren -.SH ÜBERSICHT -.B "winemaker " -[ -.BR "--nobanner " "] [ " "--backup " "| " "--nobackup " "] [ "--nosource-fix " -] -.br - [ -.BR "--lower-none " "| " "--lower-all " "| " "--lower-uppercase " -] -.br - [ -.BR "--lower-include " "| " "--nolower-include " ]\ [ " --mfc " "| " "--nomfc " -] -.br - [ -.BR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " "| " "--lib " -] -.br - [ -.BI "-D" macro "\fR[=\fIdefn\fR] ] [" "\ " "-I" "dir\fR ]\ [ " "-P" "dir\fR ] [ " "-i" "dll\fR ] [ " "-L" "dir\fR ] [ " "-l" "library " -] -.br - [ -.BR "--nodlls " "] [ " "--nomsvcrt " "] [ " "--interactive " "] [ " "--single-target \fIname\fR " -] -.br - [ -.BR "--generated-files " "] [ " "--nogenerated-files " "] -.br - [ -.BR "--wine32 " "] -.br -.IR " Arbeitsverzeichnis" " | " "Projektdatei" " | " "Workspacedatei" - -.SH BESCHREIBUNG -.PP -.B winemaker -ist ein Perl-Script um Ihnen das Konvertieren von Windows-Quellcode -zu einem Winelib-Programm zu erleichtern. -.PP -Zu diesem Zweck beherrscht \fBwinemaker\fR folgende Operationen: -.PP -- Quellcodedateien und Verzeichnisse in Kleinbuchstaben umbenennen, falls -diese beim Übertragen komplett in Großbuchstaben angekommen sind. -.PP -- Konvertierung von DOS- zu Unix-Zeilenenden (CRLF nach LF). -.PP -- Include-Anweisungen und Resourcenreferenzen durchsuchen, um Backslashes -durch Slashes zu ersetzen. -.PP -- Während des obigen Schrittes wird \fBwinemaker\fR ebenfalls nach der angegebenen Datei -im Includepfad suchen und die entsprechende Zeile, falls nötig, mit der korrekten -Groß-/Kleinschreibweise austauschen. -.PP -- \fBwinemaker\fR wird ebenso andere, exotischere Probleme wie die Benutzung von -\fI#pragma pack\fR, \fIafxres.h\fR in nicht-MFC-Projekten und mehr untersuchen. -Sollte etwas ungwöhnliches vorkommen, wird \fBwinemaker\fR Sie warnen. -.PP -- \fBwinemaker\fR kann eine ganze Verzeichnisstruktur auf einmal durchsuchen, -schätzen welche ausführbaren Dateien und Bibliotheken Sie zu erstellen -gedenken, diese den passenden Quelldateien zuordnen und entsprechende \fIMakefile\fR -generieren. -.PP -- letztendlich wird \fBwinemaker\fR eine globale \fIMakefile\fR für den normalen Gebrauch erzeugen. -.PP -- \fBwinemaker\fR erkennt MFC-basierte Projekte und erstellt angepasste Dateien. -.PP -- Existierende Projektdateien können von \fBwinemaker\fR gelesen werden. -Unterstützt sind dsp, dsw, vcproj und sln-Dateien. -.PP -.SH ARGUMENTE -.TP -.B --nobanner -Unterdrückt die Anzeige des Banners. -.TP -.B --backup -Lässt \fBwinemaker\fR Backups von allen Quellcodedateien anlegen, an denen -Änderungen vorgenommen werden. Diese Option ist Standard. -.TP -.B --nobackup -Lässt \fBwinemaker\fR keine Backups anlegen. -.TP -.B --nosource-fix -Weist \fBwinemaker\fR an, keine Quellcodedateien zu ändern (z.B. DOS zu Unix -Konvertierung). Verhindert Fehlermeldungen bei schreibgeschützten Dateien. -.TP -.B --lower-all -Alle Dateien und Verzeichnisse werden in Kleinschreibung umbenannt. -.TP -.B --lower-uppercase -Nur Dateien und Verzeichnisse, die komplett groß geschrieben sind, werden -in Kleinschreibung umbenannt. -\fIHALLO.C\fR würde beispielsweise umbenannt werden, \fIWelt.c\fR jedoch nicht. -.TP -.B --lower-none -Keine Dateien und Verzeichnisse werden in Kleinschreibung umbenannt. -Beachten Sie, dass dies nicht die Umbenennung von Dateien verhindert, deren -Erweiterungen nicht unverändert verarbeitet werden können, z.B. ".Cxx". -Diese Option ist Standard. -.TP -.B "--lower-include " -Wenn die Datei zu einer Include-Anweisung (oder einer anderen Form von -Dateireferenz für Resourcen) nicht auffindbar ist, wird der Dateiname in -Kleinschreibung umbenannt. Diese Option ist Standard. -.TP -.B "--nolower-include " -Es werden keine Änderungen an Include-Anweisungen oder Referenzen vorgenommen, -wenn die entsprechende Datei nicht auffindbar ist. -.TP -.BR "--guiexe " "| " "--windows" -Legt fest, dass für jedes gefundene, ausführbare Target, oder Target unbekannten -Typs angenommen wird, dass es sich um eine grafische Anwendung handelt. -Diese Option ist Standard. -.TP -.BR "--cuiexe " "| " "--console" -Legt fest, dass für jedes gefundene, ausführbare Target, oder Target unbekannten -Typs angenommen wird, dass es sich um eine Konsolenanwendung handelt. -.TP -.B --dll -\fBwinemaker\fR wird im Zweifelsfall annehmen, dass es sich bei einem unbekannten -Target um eine DLL handelt. -.TP -.B --lib -\fBwinemaker\fR wird im Zweifelsfall annehmen, dass es sich bei einem unbekannten -Target um eine statische Bibliothek handelt. -.TP -.B --mfc -Teilt \fBwinemaker\fR mit, dass es sich um MFC-basierte Ziele handelt. In solch einem -Fall passt \fBwinemaker\fR Pfade für Header und Bibliotheken entsprechend an und -verlinkt die Ziele mit der MFC-Bibliothek. -.TP -.B --nomfc -Teilt \fBwinemaker\fR mit, dass es sich nicht um MFC-basierte Ziele handelt. Diese -Option verhindert die Benutzung von MFC-Bibliotheken, selbst wenn \fBwinemaker\fR -Dateien wie \fIstdafx.cpp\fR oder \fIstdafx.h\fR begegnet, was normalerweise automatisch -MFC aktivieren würde, wenn weder \fB--nomfc\fR noch \fB--mfc\fR angegeben wurden. -.TP -.BI -D macro "\fR[=\fIdefn\fR]" -Fügt diese Makrodefinition zur globalen Makroliste hinzu. -.TP -.BI -I dir -Hängt das angegebene Verzeichnis dem globalen Include-Pfad an. -.TP -.BI -P dir -Hängt das angegebene Verzeichnis dem globalen DLL-Pfad an. -.TP -.BI -i dll -Fügt die angegebene Winelib-Bibliothek zur globalen Liste der zu importierenden -Winelib-Bibliotheken hinzu. -.TP -.BI -L dir -Hängt das angegebene Verzeichnis dem globalen Bibliotheks-Pfad an. -.TP -.BI -l library -Fügt die angegebene Bibliothek zur globalen Liste der zu verlinkenden -Bibliotheken hinzu. -.TP -.B --nodlls -Diese Option teilt \fBwinemaker\fR mit, nicht den Standardsatz an Winelib-Bibliotheken -zu importieren. Dies bedeutet, dass jede DLL, die Ihr Quellcode nutzt, explizit -mit \fB-i\fR an \fBwinemaker\fR übergeben werden muss. -Die Standard-Bibliotheken sind: \fIodbc32.dll\fR, \fIodbccp32.dll\fR, \fIole32.dll\fR, -\fIoleaut32.dll\fR und \fIwinspool.drv\fR. -.TP -.B --nomsvcrt -Setzt einige Optionen, die \fBwinegcc\fR daran hindern, gegen msvcrt zu kompilieren. -Nutzen Sie diese Option bei cpp-Dateien, die \fI\fR einbinden. -.TP -.B --interactive -Versetzt \fBwinemaker\fR in einen interaktiven Modus. In diesem Modus wird \fBwinemaker\fR -Sie für die Targetliste jedes Verzeichnisses nach Bestätigung und jeweils -target- und verzeichnisspezifischen Optionen fragen. -.TP -.BI --single-target " name" -Gibt an, dass es nur ein einziges Target gibt, namens \fIname\fR. -.TP -.B --generated-files -Weist \fBwinemaker\fR an, eine \fIMakefile\fR zu erzeugen. Diese Option ist Standard. -.TP -.B --nogenerated-files -Weist \fBwinemaker\fR an, keine \fIMakefile\fR zu erzeugen. -.TP -.B --wine32 -Weist \fBwinemaker\fR an, ein 32-Bit Target zu erstellen. Dies ist nützlich bei -wow64-Systemen. Ohne diese Option wird die Standardarchitektur benutzt. - -.SH BEISPIELE -.PP -Ein typischer \fBwinemaker\fR Aufruf: -.PP -$ winemaker --lower-uppercase -DSTRICT . -.PP -Damit scannt \fBwinemaker\fR das aktuelle Verzeichnis und die Unterverzeichnisse nach -Quellcodedateien. Jede Datei und jedes Verzeichnis, das ganz in Großbuchstaben -geschrieben ist, wird in Kleinbuchstaben umbenannt. Danach werden alle Quellcodedateien -an die Kompilierung mit Winelib angepasst und \fIMakefile\fRs erzeugt. \fB-DSTRICT\fR gibt -an, dass das \fBSTRICT\fR-Makro gesetzt sein muss, um diesen Quellcode zu kompilieren. -Letztendlich wird \fBwinemaker\fR die globale \fIMakefile\fR erzeugen. -.PP -Der nächste Schritt wäre dann: -.PP -$ make -.PP -Wenn Sie an diesem Punkt Compilerfehler erhalten (was recht wahrscheinlich ist, -ab einer gewissen Projektgröße), sollten Sie den Winelib User Guide zu Rate -ziehen, um Problemlösungen und Tipps zu finden. -.PP -Bei einem MFC-basierten Projekt sollten Sie stattdessen folgenden Befehl ausführen: -.PP -$ winemaker --lower-uppercase --mfc . -.br -$ make -.PP -Mit einer existierenden Projektdatei lautet der passende Befehl: -.PP -$ winemaker meinprojekt.dsp -.br -$ make -.PP - -.SH TODO / FEHLER -.PP -In einigen Fällen werden Sie die \fIMakefile\fR oder den Quellcode von Hand -nachbearbeiten müssen. -.PP -Angenommen, die fertigen Windows-Bibliotheken oder Binärdateien sind vorhanden, -könnte mit \fBwinedump\fR ermittelt werden, um welche Art von ausführbarer Datei es -sich handelt (grafisch oder Konsole), gegen welche Bibliotheken sie gelinkt -sind und welche Funktionen exportiert werden (bei Bibliotheken). All diese -Informationen könnten dann für das Winelib-Projekt verwendet werden. -.PP -Weiterhin ist \fBwinemaker\fR nicht sehr gut darin, die Bibliothek zu finden, die -die Anwendung enthält: Sie muss entweder im aktuellen Verzeichnis oder im -.IR LD_LIBRARY_PATH liegen. -.PP -\fBwinemaker\fR unterstützt noch keine Messagedateien und deren Compiler. -.PP -Fehler können im -.UR https://bugs.winehq.org -.B Wine Bugtracker -.UE -gemeldet werden. -.SH AUTOREN -François Gouget für CodeWeavers -.br -Dimitrie O. Paun -.br -André Hentschel -.SH VERFÜGBARKEIT -.B winemaker -ist Teil der Wine-Distribution, verfügbar im WineHQ, dem -.UR https://www.winehq.org/ -.B Hauptquartier der Wine-Entwicklung -.UE . -.SH SIEHE AUCH -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine-Dokumentation und Support -.UE . diff --git a/assets/wine/share/man/de.UTF-8/man1/wineserver.1 b/assets/wine/share/man/de.UTF-8/man1/wineserver.1 deleted file mode 100644 index 3de264b..0000000 --- a/assets/wine/share/man/de.UTF-8/man1/wineserver.1 +++ /dev/null @@ -1,101 +0,0 @@ -.TH WINESERVER 1 "Oktober 2005" "Wine 10.17" "Windows on Unix" -.SH NAME -wineserver \- der Wine Server -.SH ÜBERSICHT -.BI wineserver\ [options] -.SH BESCHREIBUNG -.B wineserver -ist ein Hintergrundprozess, der Wine vergleichbare Dienste bereitstellt, -wie der Windows Kernel unter Windows. -.PP -.B wineserver -startet normalerweise automatisch mit \fBwine\fR(1), daher sollten Sie sich -darüber keine Gedanken machen müssen. In einigen Fällen kann es jedoch von -Nutzen sein, \fBwineserver\fR explizit mit verschiedenen Optionen aufzurufen, -wie im Folgenden beschrieben. -.SH ARGUMENTE -.TP -\fB\-d\fR[\fIn\fR], \fB--debug\fR[\fB=\fIn\fR] -Setzt das Debuglevel auf -.IR n . -0 gibt keine Debuginformationen aus, 1 steht für normale und 2 für extra -detaillierte Ausgabe. Wenn -.I n -nicht angegeben wird, ist 1 der Standardwert. Die Debugausgabe wird -an stderr geleitet. \fBwine\fR(1) wird beim Start von \fBwineserver\fR -automatisch das Debuglevel auf normal setzen, wenn +server in der -Umgebungsvariable WINEDEBUG angegeben ist. -.TP -.BR \-f ", " --foreground -Lässt den Server zur vereinfachten Fehlersuche im Vordergrund laufen, -zum Beispiel für den Betrieb unter einem Debugger. -.TP -.BR \-h ", " --help -Zeigt den Hilfetext an. -.TP -\fB\-k\fR[\fIn\fR], \fB--kill\fR[\fB=\fIn\fR] -Beendet den momentan laufenden -.BR wineserver , -optional mit Signal \fIn\fR. Wenn kein Signal angegeben wurde, wird -SIGINT, gefolgt von einem SIGKILL gesendet. Die zu beendende Instanz von -\fBwineserver\fR wird durch die Umgebungsvariable WINEPREFIX bestimmt. -.TP -\fB\-p\fR[\fIn\fR], \fB--persistent\fR[\fB=\fIn\fR] -Gibt die Dauer an, für die \fBwineserver\fR weiterläuft nachdem alle -Clientprozesse beendet sind. Das erspart den Rechenaufwand und Zeitverlust -eines Neustarts, wenn Anwendungen in schneller Abfolge gestartet werden. -Die Verzögerung \fIn\fR ist anzugeben in Sekunden, der Standardwert ist 3. -Bei fehlender Angabe von \fIn\fR läuft der Server unbegrenzt weiter. -.TP -.BR \-v ", " --version -Zeigt Versionsinformationen an und beendet sich wieder. -.TP -.BR \-w ", " --wait -Wartet, bis sich der gerade laufende -.B wineserver -beendet hat. -.SH UMGEBUNGSVARIABLEN -.TP -.B WINEPREFIX -Wenn gesetzt, wird der Inhalt dieser Umgebungsvariable als Pfad zu einem -Verzeichnis interpretiert, in dem der -.B wineserver -seine Daten ablegt (Standardmäßig in \fI$HOME/.wine\fR). Alle -.B wine --Prozesse, die den selben -.B wineserver -verwenden (z.B. vom selben Benutzer), teilen sich u.a. die selbe Registry, -gemeinsamen Speicher und Kernelobjekte. -Durch Setzen von unterschiedlichen Pfaden als -.B WINEPREFIX -für verschiedene Wine-Prozesse ist es möglich, eine beliebige Zahl komplett -unabhängiger Sitzungen von Wine zu betreiben. -.SH DATEIEN -.TP -.B ~/.wine -Verzeichnis mit benutzerspezifischen Daten, die von -.B wine -verwaltet werden. -.TP -.BI /tmp/.wine- uid -Verzeichnis, das den Unix-Socket des Servers und die lock-Datei enthält. -Diese Dateien werden in einem Unterverzeichnis angelegt, dessen Name sich aus -den Geräte- und Inode-Nummern des WINEPREFIX-Verzeichnisses zusammensetzt. -.SH AUTOREN -Der ursprüngliche Autor von -.B wineserver -ist Alexandre Julliard. Viele andere Personen haben neue Funktionen hinzugefügt -und Fehler behoben. Details finden Sie in der Datei Changelog. -.SH FEHLER -Wenn Sie einen Fehler finden, melden Sie ihn bitte im -.UR https://bugs.winehq.org -.B Wine Bugtracker -.UE . -.SH VERFÜGBARKEIT -.B wineserver -ist Teil der Wine-Distribution, verfügbar im WineHQ, dem -.UR https://www.winehq.org/ -.B Hauptquartier der Wine-Entwicklung -.UE . -.SH "SIEHE AUCH" -.BR wine (1). diff --git a/assets/wine/share/man/fr.UTF-8/man1/wine.1 b/assets/wine/share/man/fr.UTF-8/man1/wine.1 deleted file mode 100644 index e2d5b47..0000000 --- a/assets/wine/share/man/fr.UTF-8/man1/wine.1 +++ /dev/null @@ -1,282 +0,0 @@ -.TH WINE 1 "juillet 2013" "Wine 10.17" "Windows sur Unix" -.SH NOM -wine \- exécuter des programmes Windows sur Unix -.SH SYNOPSIS -.B wine -.IR "programme " [ arguments ] -.br -.B wine --help -.br -.B wine --version -.PP -Pour des instructions sur le passage d'arguments aux programmes Windows, veuillez lire la section -.B PROGRAMME/ARGUMENTS -de la page de manuel. -.SH DESCRIPTION -.B wine -charge et exécute le programme indiqué, qui peut être un exécutable DOS, Windows -3.x, Win32 ou Win64 (sur les systèmes 64 bits). -.PP -Pour déboguer wine, utilisez plutôt -.BR winedbg . -.PP -Pour exécuter des applications en ligne de commande (programmes Windows -console), préférez -.BR wineconsole . -Cela permet d'afficher la sortie dans une fenêtre séparée. -Si vous n'utilisez pas -.B wineconsole -pour les programmes en ligne de commande, le support console sera très limité et votre -programme pourrait ne pas fonctionner correctement. -.PP -Lorsque wine est invoqué avec -.B --help -ou -.B --version -pour seul argument, il -affichera seulement un petit message d'aide ou sa version respectivement, puis se terminera. -.SH PROGRAMME/ARGUMENTS -Le nom du programme peut être spécifié au format DOS -.RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE ) -ou au format Unix -.RI ( /msdos/windows/sol.exe ). -Vous pouvez passer des arguments au programme exécuté en les ajoutant -à la fin de la ligne de commande invoquant -.B wine -(par exemple : \fIwine notepad C:\(rs\(rsTEMP\(rs\(rsLISEZMOI.TXT\fR). -Notez que vous devrez protéger les caractères spéciaux (et les espaces) -en utilisant un '\(rs' lorsque vous invoquez Wine depuis -un shell, par exemple : -.PP -wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMonProg\(rs\(rstest.exe -.PP -Il peut également s'agir d'un des exécutables Windows livrés avec Wine, -auquel cas la spécification d'un chemin complet n'est pas obligatoire, -p.ex. \fIwine explorer\fR ou \fIwine notepad\fR. -.PP -.SH ENVIRONNEMENT -.B wine -passe les variables d'environnement du shell depuis lequel il -est lancé au processus Windows/DOS exécuté. Utilisez donc la syntaxe appropriée -à votre shell pour déclarer les variables d'environnement dont vous avez besoin. -.TP -.B WINEPREFIX -Si définie, le contenu de cette variable est pris comme le nom du répertoire où -Wine stocke ses données (la valeur par défaut est -.IR $HOME/.wine ). -Ce répertoire est également utilisé pour identifier le socket utilisé pour -communiquer avec -.BR wineserver . -Tous les processus -.B wine -utilisant le même -.B wineserver -(c'est-à-dire le même utilisateur) partagent certains éléments comme la base de registre, -la mémoire partagée et les objets du noyau. -En donnant à -.B WINEPREFIX -une valeur spécifique pour différents processus -.BR wine , -il est possible d'exécuter plusieurs sessions de -.B wine -totalement indépendantes. -.TP -.B WINESERVER -Spécifie le chemin et le nom de l'exécutable -.BR wineserver . -Si cette variable n'est pas définie, Wine essaiera de charger un -fichier nommé « wineserver » dans le chemin système ou quelques autres -emplacements potentiels. -.TP -.B WINEDEBUG -Active ou désactive les messages de débogage. La syntaxe est : -.RI [ classe ][\fB+\fR|\fB-\fR] canal [,[ classe2 ][\fB+\fR|\fB-\fR] canal2 ] -.RS +7 -.PP -La -.I classe -est optionnelle et peut avoir une des valeurs suivantes : -.BR err , -.BR warn , -.B fixme -ou -.BR trace . -Si elle n'est pas spécifiée, tous les messages de débogage pour le canal -associé seront activés. Chaque canal imprimera des messages à propos -d'un composant particulier de Wine. -Le caractère suivant peut être \fB+\fR ou \fB-\fR pour activer/désactiver -le canal spécifié. Si aucune -.I classe -n'est spécifiée, le caractère \fB+\fR peut être omis. Notez que les espaces ne sont pas -autorisées dans cette chaîne de caractères. -.PP -Exemples : -.TP -WINEDEBUG=warn+all -activera tous les messages d'avertissement (recommandé pour le débogage). -.br -.TP -WINEDEBUG=warn+dll,+heap -activera tous messages d'avertissement sur les DLL, et tous les messages sur le tas. -.br -.TP -WINEDEBUG=fixme-all,warn+cursor,+relay -désactivera tous les messages FIXME, activera les messages d'avertissement sur le composant cursor et -activera tous les messages du canal relay (appels de l'API). -.br -.TP -WINEDEBUG=relay -activera tous les messages du canal relay. Pour un contrôle plus fin sur l'inclusion et -l'exclusion des fonctions et DLL des traces relay, utilisez la clé -.B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug -de la base de registre. -.PP -Pour plus d'informations sur les messages de débogage, référez-vous au chapitre -.I Exécution de Wine -du guide de l'utilisateur de Wine. -.RE -.TP -.B WINEDLLPATH -Spécifie le(s) chemin(s) où chercher les DLL intégrées et les applications -Winelib. C'est une liste de répertoires séparés par des « : ». En plus des -répertoires spécifiés dans -.BR WINEDLLPATH , -Wine utilisera aussi le répertoire d'installation. -.TP -.B WINEDLLOVERRIDES -Définit le type de remplacement et l'ordre de chargement des DLL utilisées lors du -processus de chargement d'une DLL. Deux types de bibliothèques peuvent actuellement -être chargés dans l'espace d'adressage d'un processus : les DLL natives de -Windows -.RI ( native ") et les DLL intégrées à Wine (" builtin ). -Le type peut être abrégé avec la première lettre du type -.RI ( n " ou " b ). -La bibliothèque peut également être désactivée (''). Les séquences d'ordres -doivent être séparées par des virgules. -.RS -.PP -Chaque DLL peut avoir son ordre de chargement propre. L'ordre de chargement -détermine quelle version de la DLL doit être chargée dans l'espace -d'adressage. Si la première tentative échoue, la suivante est essayée et -ainsi de suite. Plusieurs bibliothèques avec le même ordre de chargement -peuvent être séparées par des virgules. Il est également possible de spécifier -différents ordres de chargements pour différentes bibliothèques en séparant les -entrées par « ; ». -.PP -L'ordre de chargement pour une DLL 16 bits est toujours défini par l'ordre de -chargement de la DLL 32 bits qui la contient (qui peut être identifié en -observant le lien symbolique du fichier .dll.so 16 bits). Par exemple, si -\fIole32.dll\fR est configurée comme builtin, \fIstorage.dll\fR sera également chargée comme -builtin puisque la DLL 32 bits \fIole32.dll\fR contient la DLL 16 bits \fIstorage.dll\fR. -.PP -Exemples : -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n,b" -.br -Charge comdlg32 et shell32 comme des DLL windows natives, ou la version -intégrée en cas d'échec. -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b" -.br -Charge les bibliothèques windows natives comdlg32 et shell32. De plus, si une -application demande le chargement de \fIc:\(rsfoo\(rsbar\(rsbaz.dll\fR, charge la -bibliothèque intégrée \fIbaz\fR. -.TP -WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32=" -.br -Charge la bibliothèque intégrée comdlg32, ou la version native en cas -d'échec ; charge la version intégrée de shell32 et la version native de -comctl32 ; oleaut32 sera désactivée. -.RE -.TP -.B WINEARCH -Spécifie l'architecture Windows à prendre en charge. Peut être -.B win32 -(prise en charge des applications 32 bits uniquement), ou -.B win64 -(prise en charge des applications 64 bits, et 32 bits en mode WoW64). -.br -L'architecture prise en charge par un préfixe Wine donné est déterminée -au moment de sa création et ne peut être modifiée ultérieurement. -Si vous exécutez Wine avec un préfixe préexistant, il refusera de démarrer -si -.B WINEARCH -ne correspond pas à l'architecture du préfixe. -.TP -.B DISPLAY -Spécifie l'affichage X11 à utiliser. -.TP -Variables de configuration du pilote audio OSS : -.TP -.B AUDIODEV -Définit le périphérique pour les entrées/sorties audio, par défaut -.IR /dev/dsp . -.TP -.B MIXERDEV -Définit le périphérique pour les contrôles du mixeur, par défaut -.IR /dev/mixer . -.TP -.B MIDIDEV -Définit le périphérique pour le séquenceur MIDI, par défaut -.IR /dev/sequencer . -.SH FICHIERS -.TP -.I wine -Le chargeur de programme de Wine. -.TP -.I wineconsole -Le chargeur de programme de Wine pour les applications en mode console (CUI). -.TP -.I wineserver -Le serveur Wine. -.TP -.I winedbg -Le débogueur de Wine. -.TP -.I $WINEPREFIX/dosdevices -Répertoire contenant le mapping des périphériques DOS. Chaque fichier dans ce -répertoire est un lien symbolique vers le fichier périphérique Unix qui implémente -un périphérique donné. Par exemple, si COM1 est mappé sur \fI/dev/ttyS0\fR, vous aurez un -lien symbolique de la forme \fI$WINEPREFIX/dosdevices/com1\fR -> \fI/dev/ttyS0\fR. -.br -Les lecteurs DOS sont aussi définis à l'aide de liens symboliques ; par exemple, si le -lecteur D: correspond au CDROM monté sur \fI/mnt/cdrom\fR, vous aurez un lien symbolique -\fI$WINEPREFIX/dosdevices/d:\fR -> \fI/mnt/cdrom\fR. Le périphérique Unix correspondant à un lecteur -DOS peut être spécifié de la même façon, à l'exception du fait qu'il faut utiliser « :: » à -la place de « : ». Dans l'exemple précédent, si le lecteur CDROM est monté depuis /dev/hdc, -le lien symbolique correspondant sera \fI$WINEPREFIX/dosdevices/d::\fR -> \fI/dev/hdc\fR. -.SH AUTEURS -Wine est disponible grâce au travail de nombreux développeurs. Pour une liste -des auteurs, référez-vous au fichier -.I AUTHORS -à la racine de la distribution des sources. -.SH COPYRIGHT -Wine peut être distribué selon les termes de la licence LGPL. Une copie de cette -licence se trouve dans le fichier -.I COPYING.LIB -à la racine de la distribution des sources. -.SH BUGS -.PP -Un rapport sur la compatibilité de nombreuses applications est disponible sur la -.UR https://appdb.winehq.org -.B base de données d'applications de Wine -.UE . -N'hésitez pas à y ajouter des entrées pour les applications que vous -exécutez actuellement, si nécessaire. -.PP -Les bugs peuvent être signalés (en anglais) sur le -.UR https://bugs.winehq.org -.B système de suivi des problèmes de Wine -.UE . -.SH DISPONIBILITÉ -La version publique la plus récente de Wine est disponible sur WineHQ, le -.UR https://www.winehq.org/ -.B quartier général du développement de Wine -.UE . -.SH "VOIR AUSSI" -.BR wineserver (1), -.BR winedbg (1), -.br -.UR https://www.winehq.org/help -.B Documentation et support de Wine -.UE . diff --git a/assets/wine/share/man/fr.UTF-8/man1/winemaker.1 b/assets/wine/share/man/fr.UTF-8/man1/winemaker.1 deleted file mode 100644 index 6bbff19..0000000 --- a/assets/wine/share/man/fr.UTF-8/man1/winemaker.1 +++ /dev/null @@ -1,288 +0,0 @@ -.TH WINEMAKER 1 "jan 2012" "Wine 10.17" "Manuel des développeurs de Wine" -.SH NOM -winemaker \- générer une infrastructure de construction pour la compilation de programmes Windows sur UNIX -.SH SYNOPSIS -.B "winemaker " -[ -.BR "--nobanner " "] [ " "--backup " "| " "--nobackup " "] [ "--nosource-fix " -] -.br - [ -.BR "--lower-none " "| " "--lower-all " "| " "--lower-uppercase " -] -.br - [ -.BR "--lower-include " "| " "--nolower-include " ]\ [ " --mfc " "| " "--nomfc " -] -.br - [ -.BR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " "| " "--lib " -] -.br - [ -.BI "-D" macro "\fR[=\fIdéfn\fR] ] [" "\ " "-I" "rép\fR ]\ [ " "-P" "rép\fR ] [ " "-i" "dll\fR ] [ " "-L" "rép\fR ] [ " "-l" "bibliothèque " -] -.br - [ -.BR "--nodlls " "] [ " "--nomsvcrt " "] [ " "--interactive " "] [ " "--single-target \fInom\fR " -] -.br - [ -.BR "--generated-files " "] [ " "--nogenerated-files " "] -.br - [ -.BR "--wine32 " "] -.br -.IR " répertoire_de_travail" " | " "fichier_projet" " | " "fichier_espace_de_travail" - -.SH DESCRIPTION -.PP -.B winemaker -est un script perl conçu pour vous aider à entamer le -processus de conversion de vos sources Windows en programmes Winelib. -.PP -À cet effet, il peut effectuer les opérations suivantes : -.PP --\ renommer vos fichiers sources et répertoires en minuscules s'ils ont été -convertis en majuscules durant le transfert. -.PP --\ convertir les fins de ligne DOS en fins de ligne UNIX (CRLF vers LF). -.PP --\ parcourir les directives d'inclusion et les références aux fichiers -de ressources pour y remplacer les backslashs par des slashs. -.PP --\ durant l'étape ci-dessus, -.B winemaker -va également effectuer une recherche insensible à la casse du fichier -référencé dans le chemin d'inclusion, et réécrire la directive d'inclusion -avec la casse correcte si nécessaire. -.PP -.RB "-\ " winemaker -recherchera également d'autres problèmes plus exotiques comme l'emploi -de \fI#pragma pack\fR, l'utilisation de \fIafxres.h\fR dans des projets -non MFC, etc. Quand il trouve de tels points nébuleux, il émettra des -avertissements. -.PP -.RB "-\ " winemaker -peut également balayer un arbre de répertoires complet en une seule passe, -deviner quels sont les exécutables et bibliothèques en cours de construction, -les faire correspondre à des fichiers sources, et générer le \fIMakefile\fR -correspondant. -.PP --\ finalement, -.B winemaker -générera un \fIMakefile\fR global pour une utilisation classique. -.PP -.RB "-\ " winemaker -comprend les projets de type MFC, et génère des fichiers appropriés. -.PP -.RB "-\ " winemaker -est capable de lire des fichiers projets existants (dsp, dsw, vcproj et sln). -.PP -.SH OPTIONS -.TP -.B --nobanner -Désactiver l'affichage de la bannière. -.TP -.B --backup -Effectuer une sauvegarde préalable de tous les fichiers modifiés. -Comportement par défaut. -.TP -.B --nobackup -Ne pas effectuer de sauvegarde des fichiers sources modifiés. -.TP -.B --nosource-fix -Ne pas essayer de corriger les fichiers sources (p.ex. la conversion -DOS vers UNIX). Cela évite des messages d'erreur si des fichiers sont -en lecture seule. -.TP -.B --lower-all -Renommer tous les fichiers et répertoires en minuscules. -.TP -.B --lower-uppercase -Ne renommer que les fichiers et répertoires qui ont un nom composé -uniquement de majuscules. -Ainsi, \fIHELLO.C\fR serait renommé, mais pas \fIWorld.c\fR. -.TP -.B --lower-none -Ne pas renommer de fichiers et répertoires en minuscules. Notez que cela -n'empêche pas le renommage d'un fichier si son extension ne peut être traitée -telle quelle, comme par exemple « .Cxx ». Comportement par défaut. -.TP -.B "--lower-include " -Convertir en minuscules les noms de fichiers associés à des directives -d'inclusion (ou à d'autres formes de références de fichiers pour les -fichiers ressources) que -.B winemaker -n'arrive pas à trouver. Comportement par défaut. -.TP -.B "--nolower-include " -Ne pas modifier la directive d'inclusion si le fichier référencé ne peut -être trouvé. -.TP -.BR "--guiexe " "| " "--windows" -Présumer une application graphique quand une cible exécutable ou une cible d'un -type inconnu est rencontrée. -Comportement par défaut. -.TP -.BR "--cuiexe " "| " "--console" -Présumer une application en mode console quand une cible exécutable ou une cible d'un -type inconnu est rencontrée. -.TP -.B --dll -Présumer une DLL quand une cible d'un type inconnu est rencontrée (c.-à-d. si -.B winemaker -ne peut déterminer s'il s'agit d'un exécutable, d'une DLL ou d'une bibliothèque statique). -.TP -.B --lib -Présumer une bibliothèque statique quand une cible d'un type inconnu est rencontrée (c.-à-d. si -.B winemaker -ne peut déterminer s'il s'agit d'un exécutable, d'une DLL ou d'une bibliothèque statique). -.TP -.B --mfc -Spécifier que les cibles utilisent les MFC. Dans ce cas, -.B winemaker -adapte les chemins d'inclusion et des bibliothèques en conséquence, -et lie la cible avec la bibliothèque MFC. -.TP -.B --nomfc -Spécifier que les cibles n'utilisent pas les MFC. Cette option empêche -l'utilisation des bibliothèques MFC même si -.B winemaker -rencontre des fichiers \fIstdafx.cpp\fR ou \fIstdafx.h\fR qui activeraient -les MFC automatiquement en temps normal si ni \fB--nomfc\fR ni \fB--mfc\fR n'était -spécifiée. -.TP -.BI -D macro "\fR[\fB=\fIdéfn\fR]" -Ajouter la définition de macro spécifiée à la liste globale des -définitions de macros. -.TP -.BI -I répertoire -Ajouter le répertoire spécifié au chemin global d'inclusion. -.TP -.BI -P répertoire -Ajouter le répertoire spécifié au chemin global des DLL. -.TP -.BI -i dll -Ajouter la bibliothèque Winelib à la liste global de bibliothèques Winelib -à importer. -.TP -.BI -L répertoire -Ajouter le répertoire spécifié au chemin global des bibliothèques. -.TP -.BI -l bibliothèque -Ajouter la bibliothèque spécifiée à la liste globale de bibliothèques à utiliser lors de l'édition des liens. -.TP -.B --nodlls -Ne pas utiliser l'ensemble standard de bibliothèques Winelib pour les imports, -c.-à-d. que toute DLL utilisée par votre code doit être explicitement spécifiée à l'aide d'options -\fB-i\fR. -L'ensemble standard de bibliothèques est : \fIodbc32.dll\fR, \fIodbccp32.dll\fR, \fIole32.dll\fR, -\fIoleaut32.dll\fR et \fIwinspool.drv\fR. -.TP -.B --nomsvcrt -Définir certaines options afin que \fBwinegcc\fR n'utilise pas -msvcrt durant la compilation. Utilisez cette option si certains fichiers cpp -incluent \fI\fR. -.TP -.B --interactive -Utiliser le mode interactif. Dans ce mode, -.B winemaker -demandera de confirmer la liste de cibles pour chaque répertoire, et ensuite -de fournir des options spécifiques de répertoire et/ou de cible. -.TP -.BI --single-target " nom" -Spécifier qu'il n'y a qu'une seule cible, appelée \fInom\fR. -.TP -.B --generated-files -Générer le \fIMakefile\fR. Comportement par défaut. -.TP -.B --nogenerated-files -Ne pas générer le \fIMakefile\fR. -.TP -.B --wine32 -Générer une cible 32 bits. Utile sur les systèmes wow64. Sans cette option, -l'architecture par défaut est utilisée. - -.SH EXEMPLES -.PP -Voici quelques exemples typiques d'utilisation de -.B winemaker -: -.PP -$ winemaker --lower-uppercase -DSTRICT . -.PP -Recherche des fichiers sources dans le répertoire courant et ses -sous-répertoires. Quand un fichier ou répertoire a un nom composé -uniquement de majuscules, le renomme en minuscules. Ensuite, adapte tous -ces fichiers sources pour une compilation avec Winelib, et génère des -\fIMakefile\fRs. \fB-DSTRICT\fR spécifie que la macro \fBSTRICT\fR doit -être définie lors de la compilation des sources. -Finalement, un \fIMakefile\fR est créé. -.PP -L'étape suivante serait : -.PP -$ make -.PP -Si vous obtenez des erreurs de compilation à ce moment (ce qui est plus que -probable pour un projet d'une taille raisonnable), vous devriez consulter -le guide de l'utilisateur de Winelib pour trouver des moyens de les résoudre. -.PP -Pour un projet utilisant les MFC, vous devriez plutôt exécuter les commandes -suivantes\ : -.PP -$ winemaker --lower-uppercase --mfc . -.br -$ make -.PP -Pour un fichier projet existant, vous devriez exécuter les commandes suivantes : -.PP -$ winemaker monprojet.dsp -.br -$ make -.PP - -.SH LIMITATIONS / PROBLÈMES -.PP -Dans certains cas, vous devrez éditer manuellement le \fIMakefile\fR ou les fichiers -sources. -.PP -En supposant que l'exécutable ou la bibliothèque windows est disponible, on peut -utiliser -.B winedump -pour en déterminer le type (graphique ou en mode console) et les -bibliothèques auxquelles il est lié (pour les exécutables), ou quelles fonctions -elle exporte (pour les bibliothèques). On pourrait ensuite restituer tous ces -réglages pour la cible Winelib correspondante. -.PP -De plus, -.B winemaker -n'est pas très apte à trouver la bibliothèque contenant l'exécutable : elle doit -être soit dans le répertoire courant, soit dans un des répertoires de -.BR LD_LIBRARY_PATH . -.PP -.B winemaker -ne prend pas encore en charge les fichiers de messages, ni le compilateur -de messages. -.PP -Les bugs peuvent être signalés (en anglais) sur le -.UR https://bugs.winehq.org -.B système de suivi des problèmes de Wine -.UE . -.SH AUTEURS -François Gouget pour CodeWeavers -.br -Dimitrie O. Paun -.br -André Hentschel -.SH DISPONIBILITÉ -\fBwinemaker\fR fait partie de la distribution de Wine, qui est disponible sur WineHQ, le -.UR https://www.winehq.org/ -.B quartier général du développement de Wine -.UE . -.SH VOIR AUSSI -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Documentation et support de Wine -.UE . diff --git a/assets/wine/share/man/fr.UTF-8/man1/wineserver.1 b/assets/wine/share/man/fr.UTF-8/man1/wineserver.1 deleted file mode 100644 index 3a7386e..0000000 --- a/assets/wine/share/man/fr.UTF-8/man1/wineserver.1 +++ /dev/null @@ -1,106 +0,0 @@ -.TH WINESERVER 1 "octobre 2005" "Wine 10.17" "Windows sur Unix" -.SH NOM -wineserver \- le serveur Wine -.SH SYNOPSIS -.B wineserver -.RI [ options ] -.SH DESCRIPTION -.B wineserver -est un démon qui fournit à Wine à peu près les mêmes services -que le noyau de Windows fournit sous Windows. -.PP -.B wineserver -est normalement lancé automatiquement lorsque \fBwine\fR(1) démarre, mais -il peut être utile de le démarrer explicitement avec certaines options, -détaillées ci-après. -.SH OPTIONS -.TP -\fB\-d\fR[\fIn\fR], \fB--debug\fR[\fB=\fIn\fR] -Définit le niveau de débogage à -.IR n . -0 signifie aucune information de débogage, 1 est le niveau normal et 2 indique -un débogage plus important. Si -.I n -n'est pas spécifié, la valeur par défaut est 1. La sortie de débogage sera -stderr. \fBwine\fR(1) active automatiquement le débogage au niveau normal lorsqu'il -démarre \fBwineserver\fR si l'option +server est indiquée dans la variable -\fBWINEDEBUG\fR. -.TP -.BR \-f ", " --foreground -Laisse le serveur au premier plan pour un débogage plus aisé, par -exemple lorsqu'il est exécuté dans un débogueur. -.TP -.BR \-h ", " --help -Affiche un message d'aide. -.TP -\fB\-k\fR[\fIn\fR], \fB--kill\fR[\fB=\fIn\fR] -Termine le -.B wineserver -actuellement exécuté en lui envoyant facultativement le signal \fIn\fR. Si -aucun signal n'est spécifié, un signal \fBSIGINT\fR est envoyé en premier, -puis un signal \fBSIGKILL\fR. L'instance de \fBwineserver\fR à arrêter -est déterminée par la variable d'environnement \fBWINEPREFIX\fR. -.TP -\fB\-p\fR[\fIn\fR], \fB--persistent\fR[\fB=\fIn\fR] -Spécifie le délai de persistance de \fBwineserver\fR, c'est-à-dire le -temps pendant lequel le serveur continuera à tourner après que tous les -processus clients se sont terminés. Ceci évite le coût inhérent à l'arrêt -puis au redémarrage du serveur lorsque des programmes sont lancés successivement -à intervalle rapproché. -Le délai d'attente \fIn\fR est exprimé en secondes (3 secondes par défaut). -Si \fIn\fR n'est pas spécifié, le serveur s'exécute indéfiniment. -.TP -.BR \-v ", " --version -Affiche les informations sur la version et se termine. -.TP -.BR \-w ", " --wait -Attend que le -.B wineserver -actuellement exécuté se termine. -.SH ENVIRONNEMENT -.TP -.B WINEPREFIX -Si définie, cette variable indique le nom du répertoire où -.B wineserver -stocke ses données (\fI$HOME/.wine\fR par défaut). Tous les processus -.B wine -utilisant le même -.B wineserver -(c'est-à-dire pour un même utilisateur) partagent certains éléments comme la base de registre, -la mémoire partagée et les objets du noyau. -En donnant à -.B WINEPREFIX -une valeur spécifique pour différents processus Wine, il est possible d'exécuter plusieurs -sessions de Wine totalement indépendantes. -.SH FICHIERS -.TP -.B ~/.wine -Répertoire contenant les données utilisateur gérées par -.BR wine . -.TP -.BI /tmp/.wine- uid -Répertoire contenant le socket de serveur Unix et le fichier de verrouillage. -Ces fichiers sont créés dans un sous-répertoire dont le nom est dérivé -des périphérique et numéros d'inodes du répertoire \fBWINEPREFIX\fR. -.SH AUTEURS -L'auteur originel de -.B wineserver -est Alexandre Julliard. Beaucoup d'autres personnes ont contribué des nouvelles fonctionnalités -et des corrections de bugs. Pour une liste complète, consultez l'historique git. -.SH BUGS -Les bugs peuvent être signalés (en anglais) sur le -.UR https://bugs.winehq.org -.B système de suivi des problèmes de Wine -.UE . -.SH DISPONIBILITÉ -.B wineserver -fait partie de la distribution de Wine, disponible depuis WineHQ, le -.UR https://www.winehq.org/ -.B quartier général des développeurs de Wine -.UE . -.SH "VOIR AUSSI" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Documentation et support de Wine -.UE . diff --git a/assets/wine/share/man/man1/msiexec.1 b/assets/wine/share/man/man1/msiexec.1 deleted file mode 100644 index a174e19..0000000 --- a/assets/wine/share/man/man1/msiexec.1 +++ /dev/null @@ -1,128 +0,0 @@ -.TH MSIEXEC 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -msiexec \- Wine MSI Installer -.SH SYNOPSIS -.B msiexec -.I command -.RI { "required parameter" } -.RI [ "optional parameter" ]... -.SH DESCRIPTION -.B msiexec -is the Wine MSI installer, which is command line -compatible with its Microsoft Windows counterpart. -.SH INSTALL OPTIONS -.IP \fB/i\ \fR{\fIpackage\fR|\fIproductcode\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] -Install {package|productcode} with property=foobar. -.IP \fB/a\ \fR{\fIpackage\fR|\fIproductcode\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] -Install {package|productcode} in administrator (network) mode. -.IP \fB/x\ \fR{\fIpackage\fR|\fIproductcode\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] -Uninstall {package|productcode} with property=foobar. -.IP \fB/uninstall\ \fR{\fIpackage\fR|\fIproductcode\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] -Same as \fB/x\fR. -.SH REPAIR OPTIONS -.IP \fB/f\fR\ \ -\fR[\fBp\fR|\fBo\fR|\fBe\fR|\fBd\fR|\fBc\fR|\fBa\fR|\fBu\fR|\fBm\fR|\fBs\fR|\fBv\fR]\ \ -\fR{\fIpackage\fR|\fIproductcode\fR} -Repair an installation. Default options are \'omus\' -.IP "\fBp\fR" -Reinstall the file if it is missing. -.IP "\fBo\fR" -Reinstall the file if it is missing or if any older version is installed. -.IP "\fBe\fR" -Reinstall the file if it is missing, or if the installed version is equal or older. -.IP "\fBd\fR" -Reinstall the file if it is missing or a different version is installed. -.IP "\fBc\fR" -Reinstall the file if it is missing or the checksum does not match. -.IP "\fBa\fR" -Reinstall all files. -.IP "\fBu\fR" -Rewrite all required user registry entries. -.IP "\fBm\fR" -Rewrite all required machine registry entries. -.IP "\fBs\fR" -Overwrite any conflicting shortcuts. -.IP "\fBv\fR" -Recache the local installation package from the source installation package. -.SH PATCHING -.IP \fB/p\ \fR{\fIpatch\fR}\ \fR[\fIproperty\fR=\fIfoobar\fR] -Apply \fIpatch\fR. This should not be used with any of the above options. -.SH UI CONTROL -.IP \fB/q\fR[\fBn\fR|\fBb\fR|\fBr\fR|\fBf\fR] -These options allow changing the behavior of the UI when installing MSI packages. -.IP \fB/q\fR -Show no UI. -.IP \fB/qn -Same as \fB/q\fR. -.IP \fB/qb -Show a basic UI. -.IP \fB/qr -Shows a reduced user UI. -.IP \fB/qf -Shows a full UI. -.SH LOGGING -.IP \fB/l\fR[\fB*\fR]\ -[\fBi\fR|\fBw\fR|\fBe\fR|\fBa\fR|\fBr\fR|\fBu\fR|\fBc\fR|\fBm\fR|\fBo\fR|\fBp\fR|\fBv\fR]\ -[\fB+\fR|\fB!\fR]\ {\fIlogfile\fR} -Enable logging to \fIlogfile\fR. Defaults are \'iwearmo\'. -.IP "\fB*\fR" -Enable all logging options except \'v\' and \'x\'. -.IP "\fBi\fR" -Log status messages. -.IP "\fBw\fR" -Log nonfatal warnings. -.IP "\fBe\fR" -Log all error messages. -.IP "\fBa\fR" -Log start of actions. -.IP "\fBr\fR" -Log action specific records. -.IP "\fBu\fR" -Log user requests. -.IP "\fBc\fR" -Log initial UI parameters. -.IP "\fBm\fR" -Log out of memory errors. -.IP "\fBo\fR" -Log out of diskspace messages. -.IP "\fBp \fR" -Log terminal properties. -.IP "\fBv \fR" -Verbose logging. -.IP "\fBx \fR" -Log extra debugging messages. -.IP "\fB+ \fR" -Append logging to existing file. -.IP "\fB! \fR" -Flush each line to log. -.SH OTHER OPTIONS -.IP \fB/h -Show help. -.IP "\fB/j\fR[\fBu\fR|\fBm\fR] {\fIpackage\fR|\fIproductcode\fR} \ -[\fB/t \fItransform\fR] [\fB/g \fIlanguageid\fR]" -Advertise \fIpackage\fR optionally with \fB/t \fItransform\fR and \fB/g \fIlanguageid\fR. -.IP \fB/y -Register MSI service. -.IP \fB/z -Unregister MSI service. -.IP \fB/? -Same as \fB/h\fR. - -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B msiexec -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/notepad.1 b/assets/wine/share/man/man1/notepad.1 deleted file mode 100644 index c92a941..0000000 --- a/assets/wine/share/man/man1/notepad.1 +++ /dev/null @@ -1,28 +0,0 @@ -.TH NOTEPAD 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -notepad \- Wine text editor -.SH SYNOPSIS -.B notepad -.RI [ text\ file ] -.SH DESCRIPTION -.B notepad -is the Wine text editor, designed to be compatible with its Microsoft Windows counterpart. -It supports ANSI, UTF-8 and UTF-16 files, and can read (but not write) files with Unix line endings. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B notepad -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/regedit.1 b/assets/wine/share/man/man1/regedit.1 deleted file mode 100644 index 7e87554..0000000 --- a/assets/wine/share/man/man1/regedit.1 +++ /dev/null @@ -1,49 +0,0 @@ -.TH REGEDIT 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -regedit \- Wine registry editor -.SH SYNOPSIS -.B regedit -.RI [ text\ file ] -.SH DESCRIPTION -.B regedit -is the Wine registry editor, designed to be compatible with its Microsoft Windows counterpart. -If called without any options, it will start the full GUI editor. - -The switches are case\-insensitive and can be prefixed either by '\-' or '/'. -.SH "OPTIONS" -.TP -\fB\-E\fR \fIfile\fR [\fIregpath\fR] -Exports the content of the specified registry key to the specified \fIfile\fR. It exports -the whole registry if no key is specified. -.IP \fB\-D\fR\ \fIregpath -Deletes the specified registry key. -.IP \fB\-S\fR -Run regedit silently (ignored, CLI mode is always silent). This exists for compatibility with Windows regedit. -.IP \fB\-V\fR -Run regedit in advanced mode (ignored). This exists for compatibility with Windows regedit. -.IP \fB\-L\fR\ \fIlocation -Specifies the location of the system.dat registry file (ignored). This exists for compatibility with Windows regedit. -.IP \fB\-R\fR\ \fIlocation -Specifies the location of the user.dat registry file (ignored). This exists for compatibility with Windows regedit. -.IP \fB\-?\fR -Prints a help message. Any other options are ignored. -.IP \fB\-C\fR\ \fIfile.reg\fR -Create registry from \fIfile.reg\fR (unimplemented). -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B regedit -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/regsvr32.1 b/assets/wine/share/man/man1/regsvr32.1 deleted file mode 100644 index dd9b9ac..0000000 --- a/assets/wine/share/man/man1/regsvr32.1 +++ /dev/null @@ -1,37 +0,0 @@ -.TH REGSVR32 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -regsvr32 \- Wine DLL Registration Server -.SH SYNOPSIS -.B regsvr32 -.RB [ /u "] [" /s "] [" /n "] [" /i "[\fB:\fIcmdline\fR]] " \fIdllname -.SH DESCRIPTION -.B regsvr32 -is the Wine dll registration server, designed to be compatible with its Microsoft Windows counterpart. -By default, it will register the given dll. -.SH COMMANDS -.IP \fB/u -Unregister the specified dll. -.IP \fB/s -Run regsvr32 silently (will not show any GUI dialogs). -.IP \fB/i -Call DllInstall passing it an optional \fIcmdline\fR. When used with \fB/u\fR calls DllUninstall. -.IP \fB/n -Do not call DllRegisterServer; this option must be used with \fB/i\fR. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B regsvr32 -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/widl.1 b/assets/wine/share/man/man1/widl.1 deleted file mode 100644 index 1353d11..0000000 --- a/assets/wine/share/man/man1/widl.1 +++ /dev/null @@ -1,173 +0,0 @@ -.TH WIDL 1 "October 2007" "Wine 10.17" "Wine Developers Manual" -.SH NAME -widl \- Wine Interface Definition Language (IDL) compiler -.SH SYNOPSIS -.B widl -[\fIoptions\fR] \fIIDL_file\fR -.br -.B widl -[\fIoptions\fR] \fB--dlldata-only\fR \fIname1\fR [\fIname2\fR...] -.SH DESCRIPTION -When no options are used the program will generate a header file, and possibly -client and server stubs, proxy and dlldata files, a typelib, and a UUID file, -depending on the contents of the IDL file. If any of the options \fB-c\fR, -\fB-h\fR, \fB-p\fR, \fB-s\fR, \fB-t\fR, \fB-u\fR or \fB--local-stubs\fR is given, -.B widl -will only generate the requested files, and no others. When run with -\fB--dlldata-only\fR, widl will only generate a dlldata file, and it will -contain a list of the names passed as arguments. Usually the way this file -is updated is that each time -.B widl -is run, it reads any existing dlldata file, and if necessary regenerates it -with the same list of names, but with the present proxy file included. -.PP -When run without any arguments, -.B widl -will print a help message. -.PP -.SH OPTIONS -.PP -.B General options: -.IP "\fB-V\fR" -Print version number and exit. -.IP "\fB-o, --output=\fIname" -Set the name of the output file. When generating multiple output -files, this sets only the base name of the file; the respective output -files are then named \fIname\fR.h, \fIname\fR_p.c, etc. If a full -file name with extension is specified, only that file is generated. -.IP "\fB-b, --target=\fIcpu-manufacturer\fR[\fI-kernel\fR]\fI-os\fR" -Set the target architecture when cross-compiling. The target -specification is in the standard autoconf format as returned by -\fBconfig.sub\fR. -.IP "\fB-m32, -m64, --win32, --win64\fR" -Force the target architecture to 32-bit or 64-bit. -.IP \fB\-\-sysroot=\fIdir\fR -Prefix the standard include paths with \fIdir\fR. -.IP \fB\-\-nostdinc\fR -Do not search standard include paths like /usr/include and -/usr/local/include. -.PP -.B Header options: -.IP "\fB-h\fR" -Generate header files. The default output filename is \fIinfile\fB.h\fR. -.IP "\fB--oldnames\fR" -Use old naming conventions. -.PP -.B Type library options: -.IP \fB-t\fR -Generate a type library. The default output filename is -\fIinfile\fB.tlb\fR. If the output file name ends in \fB.res\fR, a -binary resource file containing the type library is generated instead. -.IP "\fB-L \fIpath\fR" -Add a directory to the library search path for imported typelibs. The -option can be specified multiple times. -.IP \fB--oldtlb\fR -Generate a type library in the old format (SLTG format). -.PP -.B UUID file options: -.IP "\fB-u\fR" -Generate a UUID file. The default output filename is \fIinfile\fB_i.c\fR. -.PP -.B Proxy/stub generation options: -.IP "\fB--align=\fIn\fB, --packing=\fIn\fR" -Set the structure packing to \fIn\fR. Supported values are 2, 4, and 8. -.IP "\fB-c\fR" -Generate a client stub file. The default output filename is \fIinfile\fB_c.c\fR. -.IP "\fB-Os\fR" -Generate inline stubs. -.IP "\fB-Oi\fR" -Generate old-style interpreted stubs. -.IP "\fB-Oif, -Oic, -Oicf\fR" -Generate new-style fully interpreted stubs. This is the default. -.IP "\fB-p\fR" -Generate a proxy. The default output filename is \fIinfile\fB_p.c\fR. -.IP "\fB--prefix-all=\fIprefix\fR" -Prefix to put on the name of both client and server stubs. -.IP "\fB--prefix-client=\fIprefix\fR" -Prefix to put on the name of client stubs. -.IP "\fB--prefix-server=\fIprefix\fR" -Prefix to put on the name of server stubs. -.IP "\fB-s\fR" -Generate a server stub file. The default output filename is -\fIinfile\fB_s.c\fR. -.PP -.IP "\fB--winrt\fR" -Enable Windows Runtime mode. -.IP "\fB--ns_prefix\fR" -Prefix namespaces with ABI namespace. -.PP -.B Registration script options: -.IP "\fB-r\fR" -Generate a registration script. The default output filename is -\fIinfile\fB_r.rgs\fR. If the output file name ends in \fB.res\fR, a -binary resource file containing the script is generated instead. -.PP -.B Dlldata file options: -.IP "\fB--dlldata-only\fI name1 \fR[\fIname2\fR...]" -Regenerate the dlldata file from scratch using the specified proxy -names. The default output filename is \fBdlldata.c\fR. -.PP -.B Metadata file options: -.IP "\fB--winmd\fR" -Generate a Windows Runtime Metadata file. This implies the -\fB--winrt\fR mode. The default output filename is -\fIinfile\fB.winmd\fR. -.PP -.B Preprocessor options: -.IP "\fB-I \fIpath\fR" -Add a directory to the include search path. Multiple include -directories are allowed. -.IP "\fB-D \fIid\fR[\fB=\fIval\fR]" -Define preprocessor macro \fIid\fR with value \fIval\fR. -.IP "\fB-E\fR" -Preprocess only. -.IP "\fB-N\fR" -Do not preprocess input. -.PP -.B Debug options: -.IP "\fB-W\fR" -Enable pedantic warnings. -.IP "\fB-d \fIn\fR" -Set debug level to the non negative integer \fIn\fR. If -prefixed with \fB0x\fR, it will be interpreted as an hexadecimal -number. For the meaning of values, see the \fBDEBUG\fR section. -.PP -.B Miscellaneous options: -.IP "\fB-app_config\fR" -Ignored, present for midl compatibility. -.IP "\fB--acf=\fIfile\fR" -Use specified application configuration file. -.IP "\fB--local-stubs=\fIfile\fR" -Generate empty stubs for call_as/local methods in an object interface and -write them to \fIfile\fR. -.PP -.SH DEBUG -Debug level \fIn\fR is a bitmask with the following meaning: - - 0x01 Tell which resource is parsed (verbose mode) - - 0x02 Dump internal structures - - 0x04 Create a parser trace (yydebug=1) - - 0x08 Preprocessor messages - - 0x10 Preprocessor lex messages - - 0x20 Preprocessor yacc trace -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AUTHORS -.B widl -was originally written by Ove Kåven. It has been improved by Rob Shearman, -Dan Hipschman, and others. For a complete list, see the git commit logs. -This man page was originally written by Hannu Valtonen and then updated by -Dan Hipschman. -.SH AVAILABILITY -.B widl -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wine.1 b/assets/wine/share/man/man1/wine.1 deleted file mode 100644 index 30dec04..0000000 --- a/assets/wine/share/man/man1/wine.1 +++ /dev/null @@ -1,317 +0,0 @@ -.TH WINE 1 "July 2013" "Wine 10.17" "Windows On Unix" -.SH NAME -wine \- run Windows programs on Unix -.SH SYNOPSIS -.B wine -.IR "program " [ arguments ] -.br -.B wine --help -.br -.B wine --version -.PP -For instructions on passing arguments to Windows programs, please see the -.B PROGRAM/ARGUMENTS -section of the man page. -.SH DESCRIPTION -.B wine -loads and runs the given program, which can be a DOS, Windows -3.x, Win32 or Win64 executable (on 64-bit systems). -.PP -For debugging wine, use -.B winedbg -instead. -.PP -For running CUI executables (Windows console programs), use -.B wineconsole -instead of -.BR wine . -This will display the output in a separate window. Not using -.B wineconsole -for CUI programs will only provide very limited console support, and your -program might not function properly. -.PP -When invoked with -.B --help -or -.B --version -as the only argument, -.B wine -will simply print a small help message or its version respectively and exit. -.SH PROGRAM/ARGUMENTS -The program name may be specified in DOS format -.RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE ) -or in Unix format -.RI ( /msdos/windows/sol.exe ). -You may pass arguments to the program being executed by adding them to the -end of the command line invoking -.B wine -(such as: \fIwine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT\fR). -Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via -a shell, e.g. -.PP -wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe -.PP -It can also be one of the Windows executables shipped with Wine, in -which case specifying the full path is not mandatory, e.g. \fIwine -explorer\fR or \fIwine notepad\fR. -.PP -.SH ENVIRONMENT -.B wine -makes the environment variables of the shell from which it -is started accessible to the Windows/DOS processes started. So use the -appropriate syntax for your shell to enter environment variables you need. -.TP -.B WINEPREFIX -If set, the contents of this variable is taken as the name of the directory where -Wine stores its data (the default is -.IR $HOME/.wine ). -This directory is also used to identify the socket which is used to -communicate with the -.BR wineserver . -All -.B wine -processes using the same -.B wineserver -(i.e.: same user) share certain things like registry, shared memory, -and config file. -By setting -.B WINEPREFIX -to different values for different -.B wine -processes, it is possible to run a number of truly independent -.B wine -processes. -.TP -.B WINESERVER -Specifies the path and name of the -.B wineserver -binary. If not set, Wine will look for a file named "wineserver" in -the path and in a few other likely locations. -.TP -.B WINEDEBUG -Turns debugging messages on or off. The syntax of the variable is -of the form -.RI [ class ][\fB+\fR|\fB-\fR] channel [,[ class2 ][\fB+\fR|\fB-\fR] channel2 ] -.RS +7 -.PP -.I class -is optional and can be one of the following: -.BR err , -.BR warn , -.BR fixme , -or -.BR trace . -If -.I class -is not specified, all debugging messages for the specified -channel are turned on. Each channel will print messages about a particular -component of Wine. -The following character can be either \fB+\fR or \fB-\fR to switch the specified -channel on or off respectively. If there is no -.I class -part before it, a leading \fB+\fR\fR can be omitted. Note that spaces are not -allowed anywhere in the string. -.PP -Examples: -.TP -WINEDEBUG=warn+all -will turn on all warning messages (recommended for debugging). -.br -.TP -WINEDEBUG=warn+dll,+heap -will turn on DLL warning messages and all heap messages. -.br -.TP -WINEDEBUG=fixme-all,warn+cursor,+relay -will turn off all FIXME messages, turn on cursor warning messages, and turn -on all relay messages (API calls). -.br -.TP -WINEDEBUG=relay -will turn on all relay messages. For more control on including or excluding -functions and dlls from the relay trace, look into the -.B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug -registry key. -.PP -For more information on debugging messages, see the -.I Running Wine -chapter of the Wine User Guide. -.RE -.TP -.B WINEDLLPATH -Specifies the path(s) in which to search for builtin dlls and Winelib -applications. This is a list of directories separated by ":". In -addition to any directory specified in -.BR WINEDLLPATH , -Wine will also look in the installation directory. -.TP -.B WINEDLLOVERRIDES -Defines the override type and load order of dlls used in the loading -process for any dll. There are currently two types of libraries that can be loaded -into a process address space: native windows dlls -.RI ( native ") and Wine internal dlls (" builtin ). -The type may be abbreviated with the first letter of the type -.RI ( n " or " b ). -The library may also be disabled (''). Each sequence of orders must be separated by commas. -.RS -.PP -Each dll may have its own specific load order. The load order -determines which version of the dll is attempted to be loaded into the -address space. If the first fails, then the next is tried and so -on. Multiple libraries with the same load order can be separated with -commas. It is also possible to use specify different loadorders for -different libraries by separating the entries by ";". -.PP -The load order for a 16-bit dll is always defined by the load order of -the 32-bit dll that contains it (which can be identified by looking at -the symbolic link of the 16-bit .dll.so file). For instance if -\fIole32.dll\fR is configured as builtin, \fIstorage.dll\fR will be loaded as -builtin too, since the 32-bit \fIole32.dll\fR contains the 16-bit -\fIstorage.dll\fR. -.PP -Examples: -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n,b" -.br -Try to load comdlg32 and shell32 as native windows dll first and try -the builtin version if the native load fails. -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b" -.br -Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if -an application request to load \fIc:\(rsfoo\(rsbar\(rsbaz.dll\fR load the builtin library \fIbaz\fR. -.TP -WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32=" -.br -Try to load comdlg32 as builtin first and try the native version if -the builtin load fails; load shell32 always as builtin and comctl32 -always as native; oleaut32 will be disabled. -.RE -.TP -.B WINEPATH -Specifies additional path(s) to be prepended to the default Windows -.B PATH -environment variable. This is a list of Windows-style directories -separated by ";". -.RS -.PP -For a permanent alternative, edit (create if needed) the -.B PATH -value under the -.B HKEY_CURRENT_USER\\\\Environment -registry key. -.RE -.TP -.B WINEARCH -Specifies the Windows architecture to support. It can be set to -.B win32 -(support only 32-bit applications), to -.B win64 -(support both 64-bit applications and 32-bit ones), or to -.B wow64 -(support 64-bit applications and 32-bit ones, using a 64-bit host -process in all cases). -.br -The architecture supported by a given Wine prefix is set at prefix -creation time and cannot be changed afterwards. When running with an -existing prefix, Wine will refuse to start if -.B WINEARCH -doesn't match the prefix architecture. It is possible however to -switch freely between \fBwin64\fR and \fBwow64\fR with an existing -64-bit prefix. -.TP -.B WINE_D3D_CONFIG -Specifies Direct3D configuration options. It can be used instead of -modifying the -.B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Direct3D -registry key. The value is a comma- or semicolon-separated list -of key-value pairs. -.RS -For example: -.TP -WINE_D3D_CONFIG="renderer=vulkan;VideoPciVendorID=0xc0de" -.PP -If an individual setting is specified in both -the environment variable and the registry, the former takes precedence. -.RE -.TP -.B DISPLAY -Specifies the X11 display to use. -.TP -OSS sound driver configuration variables: -.TP -.B AUDIODEV -Set the device for audio input / output. Default -.IR /dev/dsp . -.TP -.B MIXERDEV -Set the device for mixer controls. Default -.IR /dev/mixer . -.TP -.B MIDIDEV -Set the MIDI (sequencer) device. Default -.IR /dev/sequencer . -.SH FILES -.TP -.I wine -The Wine program loader. -.TP -.I wineconsole -The Wine program loader for CUI (console) applications. -.TP -.I wineserver -The Wine server -.TP -.I winedbg -The Wine debugger -.TP -.I $WINEPREFIX/dosdevices -Directory containing the DOS device mappings. Each file in that -directory is a symlink to the Unix device file implementing a given -device. For instance, if COM1 is mapped to \fI/dev/ttyS0\fR you'd have a -symlink of the form \fI$WINEPREFIX/dosdevices/com1\fR -> \fI/dev/ttyS0\fR. -.br -DOS drives are also specified with symlinks; for instance if drive D: -corresponds to the CDROM mounted at \fI/mnt/cdrom\fR, you'd have a symlink -\fI$WINEPREFIX/dosdevices/d:\fR -> \fI/mnt/cdrom\fR. The Unix device corresponding -to a DOS drive can be specified the same way, except with '::' instead -of ':'. So for the previous example, if the CDROM device is mounted -from \fI/dev/hdc\fR, the corresponding symlink would be -\fI$WINEPREFIX/dosdevices/d::\fR -> \fI/dev/hdc\fR. -.SH AUTHORS -Wine is available thanks to the work of many developers. For a listing -of the authors, please see the file -.I AUTHORS -in the top-level directory of the source distribution. -.SH COPYRIGHT -Wine can be distributed under the terms of the LGPL license. A copy of the -license is in the file -.I COPYING.LIB -in the top-level directory of the source distribution. -.SH BUGS -.PP -A status report on many applications is available from the -.UR https://appdb.winehq.org -.B Wine Application Database -.UE . -Please add entries to this list for applications you currently run, if -necessary. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -The most recent public version of -.B wine -is available through WineHQ, the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wineserver (1), -.BR winedbg (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wineboot.1 b/assets/wine/share/man/man1/wineboot.1 deleted file mode 100644 index d7b6d88..0000000 --- a/assets/wine/share/man/man1/wineboot.1 +++ /dev/null @@ -1,45 +0,0 @@ -.TH WINEBOOT 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -wineboot \- perform Wine initialization, startup, and shutdown tasks -.SH SYNOPSIS -.B wineboot -.RI [ options ] -.SH DESCRIPTION -.B wineboot -performs the initial creation and setup of a WINEPREFIX for wine(1). It can also perform a simulated -reboot or shutdown to any applications running within the WINEPREFIX. -.SH "OPTIONS" -.IP \fB\-h\fR,\fB\ \-\-help -Display help message. -.IP \fB\-e\fR,\fB\ \-\-end\-session -End the current session cleanly. -.IP \fB\-f\fR,\fB\ \-\-force -Force exit for processes that don't exit cleanly -.IP \fB\-i\fR,\fB\ \-\-init -Initialize the WINEPREFIX. -.IP \fB\-k\fR,\fB\ \-\-kill -Kill running processes without any cleanup. -.IP \fB\-r\fR,\fB\ \-\-restart -Restart only, don't do normal startup operations. -.IP \fB\-s\fR,\fB\ \-\-shutdown -Shutdown only, don't reboot. -.IP \fB\-u\fR,\fB\ \-\-update -Update the WINEPREFIX. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B wineboot -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winebuild.1 b/assets/wine/share/man/man1/winebuild.1 deleted file mode 100644 index 89f8981..0000000 --- a/assets/wine/share/man/man1/winebuild.1 +++ /dev/null @@ -1,584 +0,0 @@ -.TH WINEBUILD 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -winebuild \- Wine dll builder -.SH SYNOPSIS -.B winebuild -.RI [ options ]\ [ inputfile ...] -.SH DESCRIPTION -.B winebuild -generates the assembly files that are necessary to build a Wine dll, -which is basically a Win32 dll encapsulated inside a Unix library. -.PP -.B winebuild -has different modes, depending on what kind of file it is asked to -generate. The mode is specified by one of the mode options specified -below. In addition to the mode option, various other command-line -option can be specified, as described in the \fBOPTIONS\fR section. -.SH "MODE OPTIONS" -You have to specify exactly one of the following options, depending on -what you want winebuild to generate. -.TP -.BI \--dll -Build an assembly file from a .spec file (see \fBSPEC FILE SYNTAX\fR -for details), or from a standard Windows .def file. The .spec/.def -file is specified via the \fB-E\fR option. The resulting file must be -assembled and linked to the other object files to build a working Wine -dll. In this mode, the -.I input files -should be the list of all object files that will be linked into the -final dll, to allow -.B winebuild -to get the list of all undefined symbols that need to be imported from -other dlls. -.TP -.BI \--exe -Build an assembly file for an executable. This is basically the same as -the \fB--dll\fR mode except that it doesn't require a .spec/.def file as input, -since an executable need not export functions. Some executables however -do export functions, and for those a .spec/.def file can be specified via -the \fB-E\fR option. The executable is named from the .spec/.def file name if -present, or explicitly through the \fB-F\fR option. The resulting file must be -assembled and linked to the other object files to build a working Wine -executable, and all the other object files must be listed as -.I input files. -.TP -.BI \--def -Build a .def file from a spec file. The .spec file is specified via the -\fB-E\fR option. This is used when building dlls with a PE (Win32) compiler. -.TP -.BI \--implib -Build a .a import library from a spec file. The .spec file is -specified via the \fB-E\fR option. If the output library name ends -in .delay.a, a delayed import library is built. -.TP -.BI \--staticlib -Build a .a static library from object files. -.TP -.B \--resources -Generate a .o file containing all the input resources. This is useful -when building with a PE compiler, since the PE binutils cannot handle -multiple resource files as input. For a standard Unix build, the -resource files are automatically included when building the spec file, -so there's no need for an intermediate .o file. -.TP -.BI \--builtin -Mark a PE module as a Wine builtin module, by adding the "Wine builtin -DLL" signature string after the DOS header. -.TP -.BI \--fixup-ctors -Fixup constructors after a module has been built. This should be done -on the final .so module if its code contains constructors, to ensure -that Wine has a chance to initialize the module before the -constructors are executed. -.SH OPTIONS -.TP -.BI \--as-cmd= as-command -Specify the command to use to compile assembly files; the default is -\fBas\fR. -.TP -.BI \-b,\ --target= cpu-manufacturer\fR[\fB-\fIkernel\fR]\fB-\fIos -Specify the target CPU and platform on which the generated code will -be built. The target specification is in the standard autoconf format -as returned by config.sub. -.TP -.BI \-B\ directory -Add the directory to the search path for the various binutils tools -like \fBas\fR, \fBnm\fR and \fBld\fR. -.TP -.BI \--cc-cmd= cc-command -Specify the C compiler to use to compile assembly files; the default -is to instead use the assembler specified with \fB--as-cmd\fR. -.TP -.B \--data-only -Build a module that contains only data and resources, and no -executable code. With this option, \fBwinebuild\fR directly outputs a -PE file, instead of an assembly or object file. -.TP -.BI \-d,\ --delay-lib= name -Set the delayed import mode for the specified library, which must be -one of the libraries imported with the \fB-l\fR option. Delayed mode -means that the library won't be loaded until a function imported from -it is actually called. -.TP -.BI \-D\ symbol -Ignored for compatibility with the C compiler. -.TP -.B \--disable-dynamicbase -Disable 'ASLR' address space layout randomization in executable image. -The default is 'ASLR' enabled. -.TP -.BI \-e,\ --entry= function -Specify the module entry point function; if not specified, the default -is -.B DllMain -for dlls, and -.B main -for executables (if the standard C -.B main -is not defined, -.B WinMain -is used instead). This is only valid for Win32 modules. -.TP -.BI \-E,\ --export= filename -Specify a .spec file (see \fBSPEC FILE SYNTAX\fR for details), -or a standard Windows .def file that defines the exports -of the DLL or executable that is being built. -.TP -.B \--external-symbols -Allow linking to external symbols directly from the spec -file. Normally symbols exported by a dll have to be defined in the dll -itself; this option makes it possible to use symbols defined in -another Unix library (for symbols defined in another dll, a -.I forward -specification must be used instead). -.TP -.BI \-f\ option -Specify a code generation option. Currently \fB\-fPIC\fR and -\fB\-fasynchronous-unwind-tables\fR are supported. Other options are -ignored for compatibility with the C compiler. -.TP -.B \--fake-module -Create a fake PE module for a dll or exe, instead of the normal -assembly or object file. The PE module contains the resources for the -module, but no executable code. -.TP -.BI \-F,\ --filename= filename -Set the file name of the module. The default is to use the base name -of the spec file (without any extension). -.TP -.B \-h, --help -Display a usage message and exit. -.TP -.BI \-H,\ --heap= size -Specify the size of the module local heap in bytes (only valid for -Win16 modules); default is no local heap. -.TP -.BI \-I\ directory -Ignored for compatibility with the C compiler. -.TP -.B \-k, --kill-at -Remove the stdcall decorations from the symbol names in the -generated .def file. Only meaningful in \fB--def\fR mode. -.TP -.BI \-K\ flags -Ignored for compatibility with the C compiler. -.TP -.BI \--large-address-aware -Set a flag in the executable to notify the loader that this -application supports address spaces larger than 2 gigabytes. -.TP -.BI \--ld-cmd= ld-command -Specify the command to use to link the object files; the default is -\fBld\fR. -.TP -.B \-m16, -m32, -m64 -Generate respectively 16-bit, 32-bit or 64-bit code. -.TP -.BI \-march= option ,\ \-mcpu= option ,\ \-mfpu= option -Set code generation options for the assembler. -.TP -.B \-mno-cygwin -Build a library that uses the Windows runtime instead of the Unix C -library. -.TP -.BI \-M,\ --main-module= module -When building a 16-bit dll, set the name of its 32-bit counterpart to -\fImodule\fR. This is used to enforce that the load order for the -16-bit dll matches that of the 32-bit one. -.TP -.BI \-N,\ --dll-name= dllname -Set the internal name of the module. It is only used in Win16 -modules. The default is to use the base name of the spec file (without -any extension). This is used for KERNEL, since it lives in -KRNL386.EXE. It shouldn't be needed otherwise. -.TP -.BI \--nm-cmd= nm-command -Specify the command to use to get the list of undefined symbols; the -default is \fBnm\fR. -.TP -.BI --nxcompat= yes\fR|\fIno -Specify whether the module is compatible with no-exec support. The -default is yes. -.TP -.BI \-o,\ --output= file -Set the name of the output file (default is standard output). If the -output file name ends in .o, the text output is sent to a -temporary file that is then assembled to produce the specified .o -file. -.TP -.B --prefer-native -Specify that the native DLL should be preferred if available at run -time. This can be used on modules that are mostly unimplemented. -.TP -.BI \-r,\ --res= rsrc.res -Load resources from the specified binary resource file. The -\fIrsrc.res\fR file can be produced from a source resource file with -.BR wrc (1) -(or with a Windows resource compiler). -.br -This option is only necessary for Win16 resource files, the Win32 ones -can simply listed as -.I input files -and will automatically be handled correctly (though the -.B \-r -option will also work for Win32 files). -.TP -.B --safeseh -Mark object files as SEH compatible. -.TP -.B --save-temps -Do not delete the various temporary files that \fBwinebuild\fR generates. -.TP -.BI \--strip-cmd= strip-command -Specify the command to use to strip PE modules. Only meaningful in -\fB--builtin\fR mode. -.TP -.BI --subsystem= subsystem\fR[\fB:\fImajor\fR[\fB.\fIminor\fR]] -Set the subsystem of the executable, which can be one of the following: -.br -.B console -for a command line executable, -.br -.B windows -for a graphical executable, -.br -.B native -for a native-mode dll, -.br -.B wince -for a ce dll. -.br -The entry point of a command line executable is a normal C \fBmain\fR -function. A \fBwmain\fR function can be used instead if you need the -argument array to use Unicode strings. A graphical executable has a -\fBWinMain\fR entry point. -.br -Optionally a major and minor subsystem version can also be specified; -the default subsystem version is 4.0. -.TP -.BI \-u,\ --undefined= symbol -Add \fIsymbol\fR to the list of undefined symbols when invoking the -linker. This makes it possible to force a specific module of a static -library to be included when resolving imports. -.TP -.B \-v, --verbose -Display the various subcommands being invoked by -.BR winebuild . -.TP -.B \--version -Display the program version and exit. -.TP -.B \-w, --warnings -Turn on warnings. -.TP -.B \--without-dlltool -Generate import library without using dlltool. -.SH "SPEC FILE SYNTAX" -.SS "General syntax" -A spec file should contain a list of ordinal declarations. The general -syntax is the following: -.PP -.I ordinal functype -.RI [ flags ]\ exportname \ \fB(\fR\ [ args... ] \ \fB) \ [ handler ] -.br -.IB ordinal\ variable -.RI [ flags ]\ exportname \ \fB(\fR\ [ data... ] \ \fB) -.br -.IB ordinal\ extern -.RI [ flags ]\ exportname \ [ symbolname ] -.br -.IB ordinal\ stub -.RI [ flags ]\ exportname \ [\ \fB( args... \fB)\fR\ ] -.br -.IB ordinal\ equate -.RI [ flags ]\ exportname\ data -.br -.BI #\ comments -.PP -Declarations must fit on a single line, except if the end of line is -escaped using a backslash character. The -.B # -character anywhere in a line causes the rest of the line to be ignored -as a comment. -.PP -.I ordinal -specifies the ordinal number corresponding to the entry point, or '@' -for automatic ordinal allocation (Win32 only). -.PP -.I flags -is a series of optional flags, preceded by a '-' character. The -supported flags are: -.RS -.TP -.B -norelay -The entry point is not displayed in relay debugging traces (Win32 -only). -.TP -.B -noname -The entry point will be exported by ordinal instead of by name. The -name is still available for importing. -.TP -.B -ret16 -The function returns a 16-bit value (Win16 only). -.TP -.B -ret64 -The function returns a 64-bit value (Win32 only). -.TP -.B -register -The function uses CPU register to pass arguments. -.TP -.B -private -The function cannot be imported from other dlls, it can only be -accessed through GetProcAddress. -.TP -.B -ordinal -The entry point will be imported by ordinal instead of by name. The -name is still exported. -.TP -.B -thiscall -The function uses the -.I thiscall -calling convention (first parameter in %ecx register on i386). -.TP -.B -fastcall -The function uses the -.I fastcall -calling convention (first two parameters in %ecx/%edx registers on -i386). -.TP -.B -syscall\fR[=\fInumber\fR] -The function is an NT system call. A system call thunk will be -generated, and the actual function will be called by the -\fI__wine_syscall_dispatcher\fR function in ntdll. The system call -number can be specified explicitly; by default it will be assigned -sequentially starting from 0. -.TP -.B -import -The function is imported from another module. This can be used instead -of a -.I forward -specification when an application expects to find the function's -implementation inside the dll. -.TP -.B -arch=\fR[\fB!\fR]\fIcpu\fR[\fB,\fIcpu\fR] -The entry point is only available on the specified CPU -architecture(s). The names \fBwin32\fR and \fBwin64\fR match all -32-bit or 64-bit CPU architectures respectively. In 16-bit dlls, -specifying \fB-arch=win32\fR causes the entry point to be exported -from the 32-bit wrapper module. A CPU name can be prefixed with -\fB!\fR to exclude only that specific architecture. -.RE -.SS "Function ordinals" -Syntax: -.br -.I ordinal functype -.RI [ flags ]\ exportname \ \fB(\fR\ [ args... ] \ \fB) \ [ handler ] -.br - -This declaration defines a function entry point. The prototype defined by -.IR exportname \ \fB(\fR\ [ args... ] \ \fB) -specifies the name available for dynamic linking and the format of the -arguments. '@' can be used instead of -.I exportname -for ordinal-only exports. -.PP -.I functype -should be one of: -.RS -.TP -.B stdcall -for a normal Win32 function -.TP -.B pascal -for a normal Win16 function -.TP -.B cdecl -for a Win16 or Win32 function using the C calling convention -.TP -.B varargs -for a Win16 or Win32 function using the C calling convention with a -variable number of arguments -.RE -.PP -.I args -should be one or several of: -.RS -.TP -.B word -(16-bit unsigned value) -.TP -.B s_word -(16-bit signed word) -.TP -.B long -(pointer-sized integer value) -.TP -.B int64 -(64-bit integer value) -.TP -.B int128 -(128-bit integer value) -.TP -.B float -(32-bit floating point value) -.TP -.B double -(64-bit floating point value) -.TP -.B ptr -(linear pointer) -.TP -.B str -(linear pointer to a null-terminated ASCII string) -.TP -.B wstr -(linear pointer to a null-terminated Unicode string) -.TP -.B segptr -(segmented pointer) -.TP -.B segstr -(segmented pointer to a null-terminated ASCII string). -.HP -Note: The 16-bit and segmented pointer types are only valid for Win16 -functions. -.RE -.PP -.I handler -is the name of the actual C function that will implement that entry -point in 32-bit mode. The handler can also be specified as -.IB dllname . function -to define a forwarded function (one whose implementation is in another -dll). If -.I handler -is not specified, it is assumed to be identical to -.I exportname. -.PP -This first example defines an entry point for the 32-bit GetFocus() -call: -.IP -@ stdcall GetFocus() GetFocus -.PP -This second example defines an entry point for the 16-bit -CreateWindow() call (the ordinal 100 is just an example); it also -shows how long lines can be split using a backslash: -.IP -100 pascal CreateWindow(ptr ptr long s_word s_word s_word \\ - s_word word word word ptr) WIN_CreateWindow -.PP -To declare a function using a variable number of arguments, specify -the function as -.B varargs -and declare it in the C file with a '...' parameter for a Win32 -function, or with an extra VA_LIST16 argument for a Win16 function. -See the wsprintf* functions in user.exe.spec and user32.spec for an -example. -.SS "Variable ordinals" -Syntax: -.br -.IB ordinal\ variable -.RI [ flags ]\ exportname \ \fB(\fR\ [ data... ] \ \fB) -.PP -This declaration defines data storage as 32-bit words at the ordinal -specified. -.I exportname -will be the name available for dynamic -linking. -.I data -can be a decimal number or a hex number preceded by "0x". The -following example defines the variable VariableA at ordinal 2 and -containing 4 ints: -.IP -2 variable VariableA(-1 0xff 0 0) -.PP -This declaration only works in Win16 spec files. In Win32 you should -use -.B extern -instead (see below). -.SS "Extern ordinals" -Syntax: -.br -.IB ordinal\ extern -.RI [ flags ]\ exportname \ [ symbolname ] -.PP -This declaration defines an entry that simply maps to a C symbol -(variable or function). It only works in Win32 spec files. -.I exportname -will point to the symbol -.I symbolname -that must be defined in the C code. Alternatively, it can be of the -form -.IB dllname . symbolname -to define a forwarded symbol (one whose implementation is in another -dll). If -.I symbolname -is not specified, it is assumed to be identical to -.I exportname. -.SS "Stub ordinals" -Syntax: -.br -.IB ordinal\ stub -.RI [ flags ]\ exportname \ [\ \fB( args... \fB)\fR\ ] -.PP -This declaration defines a stub function. It makes the name and -ordinal available for dynamic linking, but will terminate execution -with an error message if the function is ever called. -.SS "Equate ordinals" -Syntax: -.br -.IB ordinal\ equate -.RI [ flags ]\ exportname\ data -.PP -This declaration defines an ordinal as an absolute value. -.I exportname -will be the name available for dynamic linking. -.I data -can be a decimal number or a hex number preceded by "0x". -.SS "Api sets" -Syntax: -.br -.BI apiset\ apiset_dll\ =\ target.dll\ [host.dll:target.dll] -.PP -This declaration defines that the \fIapiset_dll\fR (of the form -api-ms-*) resolves to the \fItarget\fR dll. Optionally other targets -can be specified to resolve differently for specific host dlls. For -example: -.IP -api-ms-win-core-processenvironment-l1-1-0 = kernelbase.dll -.br -api-ms-win-core-processthreads-l1-1-0 = kernel32.dll \\ -.br - kernel32.dll:kernelbase.dll -.PP -If apisets are defined, a corresponding .apiset section will be -generated in the PE binary. This requires building the module with the ---data-only option. -.SH AUTHORS -.B winebuild -has been worked on by many people over the years. The main authors are -Robert J. Amstadt, Alexandre Julliard, Martin von Loewis, Ulrich -Weigand and Eric Youngdale. Many other people have contributed new features -and bug fixes. For a complete list, see the git commit logs. -.SH BUGS -It is not yet possible to use a PE-format dll in an import -specification; only Wine dlls can be imported. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winebuild -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.BR winegcc (1), -.BR wrc (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winecfg.1 b/assets/wine/share/man/man1/winecfg.1 deleted file mode 100644 index 6bca5fe..0000000 --- a/assets/wine/share/man/man1/winecfg.1 +++ /dev/null @@ -1,47 +0,0 @@ -.TH WINECFG 1 "November 2021" "Wine 10.17" "Wine Programs" -.SH NAME -winecfg \- Wine Configuration Editor -.SH SYNOPSIS -.B winecfg -.RI [ options ] -.SH DESCRIPTION -.B winecfg -is the Wine configuration editor. It allows you to change several settings, such as DLL load order -(native versus builtin), enable a virtual desktop, setup disk drives, and change the Wine audio driver, -among others. Many of these settings can be made on a per application basis, for example, preferring native -riched20.dll for wordpad.exe, but not for notepad.exe. - -If no option is given launch the graphical version of -.BR winecfg . -.SH OPTIONS -.TP -\fB\-v \fR[\fIversion\fR], \fB/v \fR[\fIversion\fR] -Set global Windows version to -.I version -and exit. -If -.I version -is not specified, display the current global Windows version and exit. -.TP -.BR \-? ", " /? -Display help, valid versions for -.I version -and exit. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winecfg -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wineconsole.1 b/assets/wine/share/man/man1/wineconsole.1 deleted file mode 100644 index 8d04606..0000000 --- a/assets/wine/share/man/man1/wineconsole.1 +++ /dev/null @@ -1,28 +0,0 @@ -.TH WINECONSOLE 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -wineconsole \- Wine console manager -.SH SYNOPSIS -.B wineconsole -.RI [ command "] " -.SH DESCRIPTION -.B wineconsole -is the Wine console manager, used to run console commands and applications. It allows running the -console in a newly made window. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B wineconsole -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winecpp.1 b/assets/wine/share/man/man1/winecpp.1 deleted file mode 120000 index 98b0f73..0000000 --- a/assets/wine/share/man/man1/winecpp.1 +++ /dev/null @@ -1 +0,0 @@ -winegcc.1 \ No newline at end of file diff --git a/assets/wine/share/man/man1/winedbg.1 b/assets/wine/share/man/man1/winedbg.1 deleted file mode 100644 index f706ac3..0000000 --- a/assets/wine/share/man/man1/winedbg.1 +++ /dev/null @@ -1,457 +0,0 @@ -.TH WINEDBG 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -winedbg \- Wine debugger -.SH SYNOPSIS -.B winedbg -.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " wpid " ]" -.PP -.B winedbg --gdb -.RI "[ " options " ] [ " program_name " [ " program_arguments " ] | " wpid " ]" -.PP -.BI "winedbg --auto " wpid -.PP -.B winedbg --minidump -.RI "[ " file.mdmp " ] " wpid -.PP -.BI "winedbg " file.mdmp -.SH DESCRIPTION -.B winedbg -is a debugger for Wine. It allows: -.RS 4 - -- debugging native Win32 applications -.br -- debugging Winelib applications -.br -- being a drop-in replacement for Dr Watson -.RE -.PP - -.SH MODES -\fBwinedbg\fR can be used in five modes. The first argument to the -program determines the mode winedbg will run in. -.IP \fBdefault\fR -Without any explicit mode, this is standard \fBwinedbg\fR operating -mode. \fBwinedbg\fR will act as the front end for the user. -.IP \fB--gdb\fR -\fBwinedbg\fR will be used as a proxy for \fBgdb\fR. \fBgdb\fR will be -the front end for command handling, and \fBwinedbg\fR will proxy all -debugging requests from \fBgdb\fR to the Win32 APIs. -.IP \fB--auto\fR -This mode is used when \fBwinedbg\fR is set up in \fIAeDebug\fR -registry entry as the default debugger. \fBwinedbg\fR will then -display basic information about a crash. This is useful for users -who don't want to debug a crash, but rather gather relevant -information about the crash to be sent to developers. -.IP \fB--minidump\fR -This mode is similar to the \fB--auto\fR one, except that instead of -printing the information on the screen (as \fB--auto\fR does), it's -saved into a minidump file. The name of the file is either passed on -the command line, or generated by \fBWineDbg\fR when none is given. -This file could later on be reloaded into \fBwinedbg\fR for further -examination. -.IP \fBfile.mdmp\fR -In this mode \fBwinedbg\fR reloads the state of a debuggee which -has been saved into a minidump file. See either the \fBminidump\fR -command below, or the \fB--minidump mode\fR. - -.SH OPTIONS -When in \fBdefault\fR mode, the following options are available: -.PP -.IP \fB--command\ \fIstring\fR -\fBwinedbg\fR will execute the command \fIstring\fR as if it was keyed on -winedbg command line, and then will exit. This can be handy for -getting the pid of running processes (winedbg --command "info proc"). -.IP \fB--exec\ \fIfilename\fR -Sets the executable name, without starting the executable. -.IP \fB--file\ \fIfilename\fR -\fBwinedbg\fR will execute the list of commands contained in file -filename as if they were keyed on winedbg command line, and then -will exit. -.PP -When in \fBgdb\fR proxy mode, the following options are available: -.PP -.IP \fB--no-start\fR -Don't launch \fBgdb\fR directly; instead, print the \fBtarget remote\fR -GDB command to execute and listen for connection from any GDB-compatible -debugger. Normally, \fB--gdb\fR will start both the proxy debugging server -and an instance of \fBgdb\fR for the front end. This option instructs -\fBwinedbg\fR to skip launching of \fBgdb\fR, and instead prints -the GDB command that can be used to manually connect to the server. -This command is in the form -.RS -.IP -target remote localhost:\fI\fR -.PP -where \fI\fR is the TCP port \fBwinedbg\fR's proxy debugging server is bound to. -.RE -.IP -This option allows the user to replace \fBgdb\fR with some other -debugger front end, such as \fBddd\fR, \fBkgdb\fR, \fBgdbgui\fR, or Qt Creator. -Regardless of whether \fB--no-start\fR is specified, \fBwinedbg\fR will quit -after the first connection is hung up (e.g. \fBgdb\fR detaches from the -debuggee). -.IP \fB--port\fR\ \fIport\fR -Start the GDB proxy debugging server on the given port. If this option is not -specified, \fBwinedbg\fR will let the operating system choose any available port. -This option can be used in conjunction with \fB--no-start\fR to specify the port the -server shall be bound to. -.IP \fB--with-xterm\fR -This will run the \fBgdb\fR front end in a new -.BR xterm (1) -window instead of using the current Unix terminal for its interface. -This option is ignored if \fB--no-start\fR is -specified. -.PP -In all modes, the rest of the command line, when passed, is used to -identify which program, if any, is to be debugged: -.IP \fIprogram_name\fR -This is the name of an executable to start for a debugging -session. \fBwinedbg\fR will actually create a process with this -executable. If \fIprogram_arguments\fR are also given, they will be -used as arguments for creating the process to be debugged. -.IP \fIwpid\fR -\fBwinedbg\fR will attach to the process whose Windows pid is \fIwpid\fR. -Use the \fBinfo proc\fR command within \fBwinedbg\fR to list running processes -and their Windows pids. -.IP \fBdefault\fR -If nothing is specified, you will enter the debugger without any run -nor attached process. You'll have to do the job yourself. - -.SH COMMANDS -.SS Default mode, and while reloading a minidump file: -.PP -Most of commands used in \fBwinedbg\fR are similar to the ones from -\fBgdb\fR. Please refer to the \fBgdb\fR documentations for some more -details. See the \fIgdb\ differences\fR section later on to get a list -of variations from \fBgdb\fR commands. -.PP -\fIMisc. commands\fR -.IP \fBabort\fR -Aborts the debugger. -.IP \fBquit\fR -Exits the debugger. -.PP -\fIProcess handling\fR -.IP \fBattach\ \fIN\fR -Attach to a Wine process (\fIN\fR is its Windows ID, numeric or hexadecimal). -IDs can be obtained using the \fBinfo\ process\fR command. Note the -\fBinfo\ process\fR command returns hexadecimal values -.IP \fBattach\ \fIfile.mdmp\fR -Reload the state of a debuggee from the minidump \fIfile.mdmp\fR. -See the \fBminidump\fR command to save such a file. -.IP \fBdetach\fR -Detach the current Wine process. The process is no longer debugged by WineDbg, -but is still running (for a live target). -.IP \fBkill\fR -Kills the current Wine process. The process is no longer debugged by WineDbg, -and is also terminated (for a live target). -.IP \fBminidump\fR\ \fIfile.mdmp\fR -Saves the debugging context of the debuggee into a minidump file called -\fIfile.mdmp\fR. -.IP \fBrun\fR -Re-run the same process with the same arguments. -Note: all breakpoints of precedent process are no longer available. -.IP \fBrun\ \fIarg1\ arg2...\fR -Re-run the same process with arguments \fIarg1\ arg2...\fR. -Note: all breakpoints of precedent process are no longer available. -.IP \fBthread\ \fIN\fR -Change the current thread to \fIN\fR (its Windows TID, numeric or hexadecimal). -.PP -\fIHelp commands\fR -.IP \fBhelp\fR -Prints some help on the commands. -.IP \fBhelp\ info\fR -Prints some help on info commands -.PP -\fIFlow control commands\fR -.IP \fBcont\fR -Continue execution until next breakpoint or exception. -.IP \fBpass\fR -Pass the exception event up to the filter chain. -.IP \fBstep\fR -Continue execution until next C line of code (enters function call) -.IP \fBnext\fR -Continue execution until next C line of code (doesn't enter function -call) -.IP \fBstepi\fR -Execute next assembly instruction (enters function call) -.IP \fBnexti\fR -Execute next assembly instruction (doesn't enter function call) -.IP \fBfinish\fR -Execute until return of current function is reached. -.PP -\fBcont\fR, \fBstep\fR, \fBnext\fR, \fBstepi\fR, \fBnexti\fR can be -postfixed by a number (N), meaning that the command must be executed N -times before control is returned to the user. -.PP -\fIBreakpoints, watchpoints -.IP \fBenable\ \fIN\fR -Enables (break|watch)-point \fIN\fR -.IP \fBdisable\ \fIN\fR -Disables (break|watch)-point \fIN\fR -.IP \fBdelete\ \fIN\fR -Deletes (break|watch)-point \fIN\fR -.IP \fBcond\ \fIN\fR -Removes any existing condition to (break|watch)-point \fIN\fR -.IP \fBcond\ \fIN\ expr\fR -Adds condition \fIexpr\fR to (break|watch)-point -\fIN\fR. \fIexpr\fR will be evaluated each time the -(break|watch)-point is hit. If the result is a zero value, the -breakpoint isn't triggered. -.IP \fBbreak\ *\ \fIN\fR -Adds a breakpoint at address \fIN\fR -.IP \fBbreak\ \fIid\fR -Adds a breakpoint at the address of symbol \fIid\fR -.IP \fBbreak\ \fIid\ N\fR -Adds a breakpoint at the line \fIN\fR inside symbol \fIid\fR. -.IP \fBbreak\ \fIN\fR -Adds a breakpoint at line \fIN\fR of current source file. -.IP \fBbreak\fR -Adds a breakpoint at current \fB$PC\fR address. -.IP \fBwatch\ *\ \fIN\fR -Adds a watch command (on write) at address \fIN\fR (on 4 bytes). -.IP \fBwatch\ \fIid\fR -Adds a watch command (on write) at the address of symbol -\fIid\fR. Size depends on size of \fIid\fR. -.IP \fBrwatch\ *\ \fIN\fR -Adds a watch command (on read) at address \fIN\fR (on 4 bytes). -.IP \fBrwatch\ \fIid\fR -Adds a watch command (on read) at the address of symbol -\fIid\fR. Size depends on size of \fIid\fR. -.IP \fBinfo\ break\fR -Lists all (break|watch)-points (with their state). -.PP -You can use the symbol \fBEntryPoint\fR to stand for the entry point of the Dll. -.PP -When setting a (break|watch)-point by \fIid\fR, if the symbol cannot -be found (for example, the symbol is contained in a not yet loaded -module), \fBwinedbg\fR will recall the name of the symbol and will try -to set the breakpoint each time a new module is loaded (until it succeeds). -.PP -\fIStack manipulation\fR -.IP \fBbt\fR -Print calling stack of current thread. -.IP \fBbt\ \fIN\fR -Print calling stack of thread of ID \fIN\fR. Note: this doesn't change -the position of the current frame as manipulated by the \fBup\fR & -\fBdn\fR commands). -.IP \fBup\fR -Goes up one frame in current thread's stack -.IP \fBup\ \fIN\fR -Goes up \fIN\fR frames in current thread's stack -.IP \fBdn\fR -Goes down one frame in current thread's stack -.IP \fBdn\ \fIN\fR -Goes down \fIN\fR frames in current thread's stack -.IP \fBframe\ \fIN\fR -Sets \fIN\fR as the current frame for current thread's stack. -.IP \fBinfo\ locals\fR -Prints information on local variables for current function frame. -.PP -\fIDirectory & source file manipulation\fR -.IP \fBshow\ dir\fR -Prints the list of dirs where source files are looked for. -.IP \fBdir\ \fIpathname\fR -Adds \fIpathname\fR to the list of dirs where to look for source -files -.IP \fBdir\fR -Deletes the list of dirs where to look for source files -.IP \fBsymbolfile\ \fIpathname\fR -Loads external symbol definition file \fIpathname\fR -.IP \fBsymbolfile\ \fIpathname\ N\fR -Loads external symbol definition file \fIpathname\fR (applying -an offset of \fIN\fR to addresses) -.IP \fBlist\fR -Lists 10 source lines forwards from current position. -.IP \fBlist\ -\fR -Lists 10 source lines backwards from current position -.IP \fBlist\ \fIN\fR -Lists 10 source lines from line \fIN\fR in current file -.IP \fBlist\ \fIpathname\fB:\fIN\fR -Lists 10 source lines from line \fIN\fR in file \fIpathname\fR -.IP \fBlist\ \fIid\fR -Lists 10 source lines of function \fIid\fR -.IP \fBlist\ *\ \fIN\fR -Lists 10 source lines from address \fIN\fR -.PP -You can specify the end target (to change the 10 lines value) using -the ',' separator. For example: -.IP \fBlist\ 123,\ 234\fR -lists source lines from line 123 up to line 234 in current file -.IP \fBlist\ foo.c:1,56\fR -lists source lines from line 1 up to 56 in file foo.c -.PP -\fIDisplaying\fR -.PP -A display is an expression that's evaluated and printed after the -execution of any \fBwinedbg\fR command. -.IP \fBdisplay\fR -.IP \fBinfo\ display\fR -Lists the active displays -.IP \fBdisplay\ \fIexpr\fR -Adds a display for expression \fIexpr\fR -.IP \fBdisplay\ /\fIfmt\ \fIexpr\fR -Adds a display for expression \fIexpr\fR. Printing evaluated -\fIexpr\fR is done using the given format (see \fBprint\ command\fR -for more on formats) -.IP \fBdel\ display\ \fIN\fR -.IP \fBundisplay\ \fIN\fR -Deletes display \fIN\fR -.PP -\fIDisassembly\fR -.IP \fBdisas\fR -Disassemble from current position -.IP \fBdisas\ \fIexpr\fR -Disassemble from address \fIexpr\fR -.IP \fBdisas\ \fIexpr\fB,\fIexpr\fR -Disassembles code between addresses specified by the two expressions -.PP -\fIMemory\ (reading,\ writing,\ typing)\fR -.IP \fBx\ \fIexpr\fR -Examines memory at address \fIexpr\fR -.IP \fBx\ /\fIfmt\ expr\fR -Examines memory at address \fIexpr\fR using format \fIfmt\fR -.IP \fBprint\ \fIexpr\fR -Prints the value of \fIexpr\fR (possibly using its type) -.IP \fBprint\ /\fIfmt\ expr\fR -Prints the value of \fIexpr\fR (possibly using its type) -.IP \fBset\ \fIvar\fB\ =\ \fIexpr\fR -Writes the value of \fIexpr\fR in \fIvar\fR variable -.IP \fBwhatis\ \fIexpr\fR -Prints the C type of expression \fIexpr\fR -.PP -.IP \fIfmt\fR -is either \fIletter\fR or \fIcount letter\fR, where \fIletter\fR -can be: -.RS 4 -.IP \fBs\fR -an ASCII string -.IP \fBu\fR -a UTF16 Unicode string -.IP \fBi\fR -instructions (disassemble) -.IP \fBx\fR -32-bit unsigned hexadecimal integer -.IP \fBd\fR -32-bit signed decimal integer -.IP \fBw\fR -16-bit unsigned hexadecimal integer -.IP \fBc\fR -character (only printable 0x20-0x7f are actually printed) -.IP \fBb\fR -8-bit unsigned hexadecimal integer -.IP \fBg\fR -Win32 GUID -.RE -.PP -\fIExpressions\fR -.PP -Expressions in Wine Debugger are mostly written in a C form. However, -there are a few discrepancies: -.PP -.RS 4 -Identifiers can take a '!' in their names. This allows mainly to -specify a module where to look the ID from, e.g. \fIUSER32!CreateWindowExA\fR. -.PP -In a cast operation, when specifying a structure or a union, you must -use the struct or union keyword (even if your program uses a typedef). -.RE -.PP -When specifying an identifier, if several symbols with -this name exist, the debugger will prompt for the symbol you want to -use. Pick up the one you want from its number. -.PP -\fIInformation on Wine internals\fR -.IP \fBinfo\ class\fR -Lists all Windows classes registered in Wine -.IP \fBinfo\ class\ \fIid\fR -Prints information on Windows class \fIid\fR -.IP \fBinfo\ share\fR -Lists all the dynamic libraries loaded in the debugged program -(including .so files, NE and PE DLLs) -.IP \fBinfo\ share\ \fIN\fR -Prints information on module at address \fIN\fR -.IP \fBinfo\ regs\fR -Prints the value of the CPU registers -.IP \fBinfo\ all-regs\fR -Prints the value of the CPU and Floating Point registers -.IP \fBinfo\ segment\fR -Lists all allocated segments (i386 only) -.IP \fBinfo\ segment\ \fIN\fR -Prints information on segment \fIN\fR (i386 only) -.IP \fBinfo\ stack\fR -Prints the values on top of the stack -.IP \fBinfo\ map\fR -Lists all virtual mappings used by the debugged program -.IP \fBinfo\ map\ \fIN\fR -Lists all virtual mappings used by the program of Windows pid \fIN\fR -.IP \fBinfo\ wnd\fR -Displays the window hierarchy starting from the desktop window -.IP \fBinfo\ wnd\ \fIN\fR -Prints information of Window of handle \fIN\fR -.IP \fBinfo\ process\fR -Lists all w-processes in Wine session -.IP \fBinfo\ thread\fR -Lists all w-threads in Wine session -.IP \fBinfo\ frame\fR -Lists the exception frames (starting from current stack frame). You -can also pass, as optional argument, a thread id (instead of current -thread) to examine its exception frames. -.PP -Debug messages can be turned on and off as you are debugging using -the \fBset\fR command, but only for channels initialized with the -\fIWINEDEBUG\fR environment variable. -.IP \fBset\ warn\ +\ \fIwin\fR -Turns on warn on \fIwin\fR channel -.IP \fBset\ +\ \fIwin\fR -Turns on warn/fixme/err/trace on \fIwin\fR channel -.IP \fBset\ -\ \fIwin\fR -Turns off warn/fixme/err/trace on \fIwin\fR channel -.IP \fBset\ fixme\ -\ all\fR -Turns off fixme class on all channels -.PP -.SS Gdb mode: -.PP -See the \fBgdb\fR documentation for all the \fBgdb\fR commands. -.PP -However, a few Wine extensions are available, through the -\fBmonitor\fR command: -.IP \fBmonitor\ wnd\fR -Lists all windows in the Wine session -.IP \fBmonitor\ proc\fR -Lists all processes in the Wine session -.IP \fBmonitor\ mem\fR -Displays memory mapping of debugged process -.PP -.SS Auto and minidump modes: -.PP -Since no user input is possible, no commands are available. - -.SH ENVIRONMENT -.IP \fBWINE_GDB\fR -When used in \fBgdb\fR proxy mode, \fBWINE_GDB\fR specifies the name -(and the path) of the executable to be used for \fBgdb\fR. "gdb" -is used by default. -.SH AUTHORS -The first version was written by Eric Youngdale. -.PP -See Wine developers list for the rest of contributors. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winedbg -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winedump.1 b/assets/wine/share/man/man1/winedump.1 deleted file mode 100644 index 2c80d91..0000000 --- a/assets/wine/share/man/man1/winedump.1 +++ /dev/null @@ -1,227 +0,0 @@ -.TH WINEDUMP 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -winedump \- Wine DLL tool -.SH SYNOPSIS -.BR "winedump " [ "-h " "| " -.BI "sym " sym -| -.BI "spec " dll -| -.BI "dump " file -.RI "] [" "mode_options" ] -.SH DESCRIPTION -.B winedump -is a Wine tool which aims to help: - -- A: Reimplementing a Win32 DLL for use within Wine, or -.br -- B: Compiling a Win32 application with Winelib that uses x86 DLLs -.PP -For both tasks in order to be able to link to the Win functions some -glue code is needed. This 'glue' comes in the form of a \fI.spec\fR file. -The \fI.spec\fR file, along with some dummy code, is used to create a -Wine \fI.so\fR corresponding to the Windows DLL. The \fBwinebuild\fR program -can then resolve calls made to DLL functions. -.PP -Creating a \fI.spec\fR file is a labour intensive task during which it is -easy to make a mistake. The idea of \fBwinedump\fR is to automate this task -and create the majority of the support code needed for your DLL. In -addition you can have \fBwinedump\fR create code to help you re-implement a -DLL, by providing tracing of calls to the DLL, and (in some cases) -automatically determining the parameters, calling conventions, and -return values of the DLL functions. -.PP -Another use for this tool is to display (dump) information about a 32bit -DLL or PE format image file. When used in this way \fBwinedump\fR functions -similarly to tools such as pedump provided by many Win32 compiler -vendors. -.PP -Finally \fBwinedump\fR can be also used to demangle C++ symbols. -.SH MODES -.B winedump -can be used in several different modes. The first argument to the -program determines the mode \fBwinedump\fR will run in. -.IP \fB-h\fR -Help mode. -Basic usage help is printed. -.IP \fBdump\fR -To dump the contents of a file. -.IP \fBspec\fR -For generating .spec files and stub DLLs. -.IP \fBsym\fR -Symbol mode. -Used to demangle C++ symbols. -.SH OPTIONS -Mode options depend on the mode given as the first argument. -.PP -.SS Help mode -No options are used. -The program prints the help info and then exits. -.SS Dump mode -.IP \fIfile\fR -Dumps the contents of \fIfile\fR. Various file formats are supported -(PE, NE, LE, Minidumps, .lnk). -.IP \fB-C\fR -Turns on symbol demangling. -.IP \fB-f\fR -Dumps file header information. -This option dumps only the standard PE header structures, -along with the COFF sections available in the file. -.IP "\fB-j \fIdir_name\fR" -Dumps only the content of directory \fIdir_name\fR, for files which -header points to directories. For PE files, the \fBimport\fR, -\fBexport\fR, \fBdebug\fR, \fBresource\fR, \fBtls\fR, \fBloadcfg\fR, -\fBclr\fR, \fBreloc\fR and \fBexcept\fR directories, as well as the -\fBapiset\fR section, are implemented. For NE files, the \fBexport\fR -and \fBresource\fR directories are implemented. -.IP \fB-x\fR -Dumps everything. -This command prints all available information (including all -available directories - see \fB-j\fR option) about the file. You may -wish to pipe the output through \fBmore\fR/\fBless\fR or into a file, since -a lot of output will be produced. -.IP \fB-G\fR -Dumps contents of debug section if any (for now, only stabs -information is supported). -.SS Spec mode -.IP \fIdll\fR -Use \fIdll\fR for input file and generate implementation code. -.IP "\fB-I \fIdir\fR" -Look for prototypes in \fIdir\fR (implies \fB-c\fR). In the case of -Windows DLLs, this could be either the standard include -directory from your compiler, or a SDK include directory. -If you have a text document with prototypes (such as -documentation) that can be used also, however you may need -to delete some non-code lines to ensure that prototypes are -parsed correctly. -The \fIdir\fR argument can also be a file specification (e.g. -\fIinclude/*\fR). If it contains wildcards you must quote it to -prevent the shell from expanding it. -If you have no prototypes, specify \fI/dev/null\fR as \fIdir\fR. -\fBwinedump\fR may still be able to generate some working stub -code for you. -.IP \fB-c\fR -Generate skeleton code (requires \fB-I\fR). -This option tells \fBwinedump\fR to create function stubs for each -function in the DLL. As \fBwinedump\fR reads each exported symbol -from the source DLL, it first tries to demangle the name. If -the name is a C++ symbol, the arguments, class and return -value are all encoded into the symbol name. Winedump -converts this information into a C function prototype. If -this fails, the file(s) specified in the \fB-I\fR argument are -scanned for a function prototype. If one is found it is used -for the next step of the process, code generation. -.IP \fB-t\fR -TRACE arguments (implies \fB-c\fR). -This option produces the same code as \fB-c\fR, except that -arguments are printed out when the function is called. -Structs that are passed by value are printed as "struct", -and functions that take variable argument lists print "...". -.IP "\fB-f \fIdll\fR" -Forward calls to \fIdll\fR (implies \fB-t\fR). -This is the most complicated level of code generation. The -same code is generated as \fB-t\fR, however support is added for -forwarding calls to another DLL. The DLL to forward to is -given as \fIdll\fR. -.IP \fB-D\fR -Generate documentation. -By default, \fBwinedump\fR generates a standard comment at the -header of each function it generates. Passing this option -makes \fBwinedump\fR output a full header template for standard -Wine documentation, listing the parameters and return value -of the function. -.IP "\fB-o \fIname\fR" -Set the output dll name (default: \fBdll\fR). -By default, if \fBwinedump\fR is run on DLL \fIfoo\fR, it creates -files \fIfoo.spec\fR, \fIfoo_main.c\fR etc, and prefixes any -functions generated with \fIFOO_\fR. If \fB-o \fIbar\fR is given, -these will become \fIbar.spec\fR, \fIbar_main.c\fR and \fIBAR_\fR -respectively. -This option is mostly useful when generating a forwarding DLL. -.IP \fB-C\fR -Assume __cdecl calls (default: __stdcall). -If winebuild cannot determine the calling convention, -__stdcall is used by default, unless this option has -been given. -Unless \fB-q\fR is given, a warning will be printed for every -function that \fBwinedump\fR determines the calling convention -for and which does not match the assumed calling convention. -.IP "\fB-s \fInum\fR" -Start prototype search after symbol \fInum\fR. -.IP "\fB-e \fInum\fR" -End prototype search after symbol \fInum\fR. -By passing the \fB-s\fR or \fB-e\fR options you can have \fBwinedump\fR try to -generate code for only some functions in your DLL. This may -be used to generate a single function, for example, if you -wanted to add functionality to an existing DLL. -.IP "\fB-S \fIsymfile\fR" -Search only prototype names found in \fIsymfile\fR. -If you want to only generate code for a subset of exported -functions from your source DLL, you can use this option to -provide a text file containing the names of the symbols to -extract, one per line. Only the symbols present in this file -will be used in your output DLL. -.IP \fB-q\fR -Don't show progress (quiet). -No output is printed unless a fatal error is encountered. -.IP \fB-v\fR -Show lots of detail while working (verbose). -There are 3 levels of output while \fBwinedump\fR is running. The -default level, when neither \fB-q\fR or \fB-v\fR are given, prints the -number of exported functions found in the dll, followed by -the name of each function as it is processed, and a status -indication of whether it was processed OK. With \fB-v\fR given, a -lot of information is dumped while \fBwinedump\fR works: this is -intended to help debug any problems. -.SS Sym mode -.IP \fIsym\fR -Demangles C++ symbol \fIsym\fR and then exits. -.SH FILES -.IP function_grep.pl -Perl script used to retrieve a function prototype. -.PP -Files output in -.BR spec " mode" -for -.IR foo.dll : -.IP foo.spec -.RS -This is the \fI.spec\fR file. -.RE -.IP foo_dll.h,\ foo_main.c -.RS -These are the source code files containing the minimum set -of code to build a stub DLL. The C file contains one -function, \fIFOO_Init\fR, which does nothing (but must be -present). -.RE -.IP Makefile.in -.RS -This is a template for \fBconfigure\fR to produce a makefile. It -is designed for a DLL that will be inserted into the Wine -source tree. -.SH BUGS -C++ name demangling is not fully in sync with the implementation in msvcrt. -It might be useful to submit your C++ name to the testsuite for msvcrt. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AUTHORS -Jon P. Griffiths -.br -Michael Stefaniuc -.SH AVAILABILITY -.B winedump -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1) -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winefile.1 b/assets/wine/share/man/man1/winefile.1 deleted file mode 100644 index 29daf6e..0000000 --- a/assets/wine/share/man/man1/winefile.1 +++ /dev/null @@ -1,33 +0,0 @@ -.TH WINEFILE 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -winefile \- Wine File Manager -.SH SYNOPSIS -.BI winefile " path" -.SH DESCRIPTION -.B winefile -is the Wine file manager, with a similar design to early Microsoft Windows explorer. -.SH USAGE -You can pass winefile either a Unix or Win32 path, for example: - -.RB "- Using a Unix path: " "winefile /mnt/hda1" - -.RB "- Using a Win32 path: " "winefile C:\(rs\(rswindows\(rs\(rs\ " - -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winefile -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wineg++.1 b/assets/wine/share/man/man1/wineg++.1 deleted file mode 120000 index 98b0f73..0000000 --- a/assets/wine/share/man/man1/wineg++.1 +++ /dev/null @@ -1 +0,0 @@ -winegcc.1 \ No newline at end of file diff --git a/assets/wine/share/man/man1/winegcc.1 b/assets/wine/share/man/man1/winegcc.1 deleted file mode 100644 index 02aa4fb..0000000 --- a/assets/wine/share/man/man1/winegcc.1 +++ /dev/null @@ -1,114 +0,0 @@ -.TH WINEGCC 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -winegcc \- Wine C and C++ MinGW Compatible Compiler -.SH SYNOPSIS -.B winegcc -.RI [ options "] " infile\fR... -.SH DESCRIPTION -.B winegcc -is a gcc wrapper which tries to provide a MinGW compatible compiler -under Linux. This is most useful to Win32 developers who can simply -take their MinGW code from Windows, and recompile it without -modifications under Winelib on Linux. -wineg++ accepts mostly the same options as winegcc. -.PP -The goal of winegcc is to be able to simply replace gcc/g++/windres -with winegcc/wineg++/wrc in a MinGW Makefile, and just recompile -the application using Winelib under Wine. While typically there are -small adjustments that must be made to the application source code -and/or Makefile, it is quite easy to do them in a fashion that is -compatible between the MinGW and Wine environments. -.PP -This manual will document only the differences from gcc; please consult -the gcc manual for more information on those options. -.PP -.SH OPTIONS -.B gcc options: -All gcc options are supported, and are passed along to the backend -compiler. -.IP "\fB-b,--target \fItarget\fR" -Specify the target architecture triplet for cross-compiling. winegcc -will then invoke \fItarget\fR-gcc instead of gcc. -.IP "\fB--wine-objdir \fIdir\fR" -Specify the Wine object directory. This is used when building Wine -itself, to use the includes and libraries from inside the build tree. -.IP "\fB--winebuild \fIname\fR" -Specifies the path and name of the \fBwinebuild\fR binary that will be -launched automatically by \fBwinegcc\fR. If not set, \fBwinegcc\fR -will look for a file named \fIwinebuild\fR in the path. This takes -precedence over the \fBWINEBUILD\fR environment variable. -.IP \fB-fno-short-wchar\fR -Override the underlying type for wchar_t to be the default for the -target, instead of using short unsigned int, which is the default -for Win32. -.IP \fB-mconsole\fR -This option passes '--subsystem console' to winebuild, to build -console applications. It is the default. -.IP \fB-mno-cygwin\fR -Use Wine implementation of MSVCRT, instead of linking against -the host system libc. This is necessary for the vast majority -of Win32 applications, as they typically depend on various features -of MSVCRT. This switch is also used by the MinGW compiler to link -against MSVCRT on Windows, instead of linking against Cygwin -libc. Sharing the syntax with MinGW makes it very easy to write -Makefiles that work under Wine, MinGW+MSYS, or MinGW+Cygwin. -.IP \fB-municode\fR -Set the default entry point of the application to be the Unicode -\fBwmain()\fR instead of the standard \fBmain()\fR. -.IP \fB-mwindows\fR -This option adds -lgdi32, -lcomdlg32, and -lshell32 to the list of -default libraries, and passes '--subsystem windows' to winebuild -to build graphical applications. -.IP \fB-nodefaultlibs\fR -Do not use the standard system libraries when linking. These -include at a minimum -lkernel32, -luser32, -ladvapi32, and -any default libraries used by the backend compiler. The -mwindows -option augments the list of default libraries as described above. -.IP \fB-nostartfiles\fR -Do not add the winecrt0 library when linking. -.IP \fB-Wb,\fIoption\fR -Pass an option to winebuild. If \fIoption\fR contains -commas, it is split into multiple options at the commas. -.IP \fB-Wl,--out-implib,\fIlib.a\fR -When linking a dll, also create its corresponding import library. -.SH ENVIRONMENT -.TP -.B WINEBUILD -Specifies the path and name of the \fBwinebuild\fR binary that will be -launched automatically by \fBwinegcc\fR. If not set, \fBwinegcc\fR -will look for a file named \fIwinebuild\fR in the path. -.SH DEFINES -winegcc defines __WINE__, for code that needs to know when it is -being compiled under Wine. It also defines WIN32, _WIN32, __WIN32, -__WIN32__, __WINNT, and __WINNT__ for compatibility with MinGW. -.SH BUGS -The dllimport/dllexport attributes are not supported at the moment, -due to lack of support for these features in the ELF version of gcc. -.PP -Static linking is not currently supported against Wine DLLs. As a -result, the -static, --static, and -Wl,-static options will generate -an error. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AUTHORS -.B winegcc -was written by Dimitrie O. Paun. -.SH AVAILABILITY -.B winegcc -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR gcc (1), -.BR winebuild (1), -.BR wrc (1), -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winemaker.1 b/assets/wine/share/man/man1/winemaker.1 deleted file mode 100644 index 5e03a75..0000000 --- a/assets/wine/share/man/man1/winemaker.1 +++ /dev/null @@ -1,249 +0,0 @@ -.TH WINEMAKER 1 "Jan 2012" "Wine 10.17" "Wine Developers Manual" -.SH NAME -winemaker \- generate a build infrastructure for compiling Windows programs on Unix -.SH SYNOPSIS -.B "winemaker " -[ -.BR "--nobanner " "] [ " "--backup " "| " "--nobackup " "] [ "--nosource-fix " -] -.br - [ -.BR "--lower-none " "| " "--lower-all " "| " "--lower-uppercase " -] -.br - [ -.BR "--lower-include " "| " "--nolower-include " ]\ [ " --mfc " "| " "--nomfc " -] -.br - [ -.BR "--guiexe " "| " "--windows " "| " "--cuiexe " "| " "--console " "| " "--dll " "| " "--lib " -] -.br - [ -.BI "-D" macro "\fR[=\fIdefn\fR] ] [" "\ " "-I" "dir\fR ]\ [ " "-P" "dir\fR ] [ " "-i" "dll\fR ] [ " "-L" "dir\fR ] [ " "-l" "library " -] -.br - [ -.BR "--nodlls " "] [ " "--nomsvcrt " "] [ " "--interactive " "] [ " "--single-target \fIname\fR " -] -.br - [ -.BR "--generated-files " "] [ " "--nogenerated-files " "] -.br - [ -.BR "--wine32 " "] -.br -.IR " work_directory" " | " "project_file" " | " "workspace_file" - -.SH DESCRIPTION -.PP -.B winemaker -is a perl script designed to help you bootstrap the -process of converting your Windows sources to Winelib programs. -.PP -In order to do this \fBwinemaker\fR can perform the following operations: -.PP -- rename your source files and directories to lowercase in the event they -got all uppercased during the transfer. -.PP -- perform DOS to Unix (CRLF to LF) conversions. -.PP -- scan the include statements and resource file references to replace the -backslashes with forward slashes. -.PP -- during the above step \fBwinemaker\fR will also perform a case insensitive search -of the referenced file in the include path and rewrite the include statement -with the right case if necessary. -.PP -- \fBwinemaker\fR will also check other more exotic issues like \fI#pragma pack\fR -usage, use of \fIafxres.h\fR in non MFC projects, and more. Whenever it -encounters something out of the ordinary, it will warn you about it. -.PP -- \fBwinemaker\fR can also scan a complete directory tree at once, guess what are -the executables and libraries you are trying to build, match them with -source files, and generate the corresponding \fIMakefile\fR. -.PP -- finally \fBwinemaker\fR will generate a global \fIMakefile\fR for normal use. -.PP -- \fBwinemaker\fR knows about MFC-based project and will generate customized files. -.PP -- \fBwinemaker\fR can read existing project files. It supports dsp, dsw, vcproj and sln files. -.PP -.SH OPTIONS -.TP -.B --nobanner -Disable the printing of the banner. -.TP -.B --backup -Perform a backup of all the modified source files. This is the default. -.TP -.B --nobackup -Do not backup modified source files. -.TP -.B --nosource-fix -Do no try to fix the source files (e.g. DOS to Unix -conversion). This prevents complaints if the files are readonly. -.TP -.B --lower-all -Rename all files and directories to lowercase. -.TP -.B --lower-uppercase -Only rename files and directories that have an all uppercase name. -So \fIHELLO.C\fR would be renamed but not \fIWorld.c\fR. -.TP -.B --lower-none -Do not rename files and directories to lower case. Note -that this does not prevent the renaming of a file if its extension cannot -be handled as is, e.g. ".Cxx". This is the default. -.TP -.B --lower-include -When the file corresponding to an include statement (or other form of file reference -for resource files) cannot be found, convert that filename to lowercase. This is the default. -.TP -.B --nolower-include -Do not modify the include statement if the referenced file cannot be found. -.TP -.BR "--guiexe " "| " "--windows" -Assume a graphical application when an executable target or a target of -unknown type is found. This is the default. -.TP -.BR "--cuiexe " "| " "--console" -Assume a console application when an executable target or a target of -unknown type is found. -.TP -.B --dll -Assume a dll when a target of unknown type is found, i.e. when \fBwinemaker\fR is unable to -determine whether it is an executable, a dll, or a static library, -.TP -.B --lib -Assume a static library when a target of unknown type is found, i.e. when \fBwinemaker\fR is -unable to determine whether it is an executable, a dll, or a static library, -.TP -.B --mfc -Specify that the targets are MFC based. In such a case \fBwinemaker\fR adapts -the include and library paths accordingly, and links the target with the -MFC library. -.TP -.B --nomfc -Specify that targets are not MFC-based. This option disables use of MFC libraries -even if \fBwinemaker\fR encounters files \fIstdafx.cpp\fR or \fIstdafx.h\fR that would cause it -to enable MFC automatically if neither \fB--nomfc\fR nor \fB--mfc\fR was specified. -.TP -.BI -D macro "\fR[\fB=\fIdefn\fR]" -Add the specified macro definition to the global list of macro definitions. -.TP -.BI -I dir -Append the specified directory to the global include path. -.TP -.BI -P dir -Append the specified directory to the global dll path. -.TP -.BI -i dll -Add the Winelib library to the global list of Winelib libraries to import. -.TP -.BI -L dir -Append the specified directory to the global library path. -.TP -.BI -l library -Add the specified library to the global list of libraries to link with. -.TP -.B --nodlls -Do not use the standard set of Winelib libraries for imports. -That is, any DLL your code uses must be explicitly passed with \fB-i\fR options. -The standard set of libraries is: \fIodbc32.dll\fR, \fIodbccp32.dll\fR, \fIole32.dll\fR, -\fIoleaut32.dll\fR and \fIwinspool.drv\fR. -.TP -.B --nomsvcrt -Set some options to tell \fBwinegcc\fR not to compile against msvcrt. -Use this option if you have cpp-files that include \fI\fR. -.TP -.B --interactive -Use interactive mode. In this mode \fBwinemaker\fR will ask you to -confirm the list of targets for each directory, and then to provide directory and -target specific options. -.TP -.BI --single-target " name" -Specify that there is only one target, called \fIname\fR. -.TP -.B --generated-files -Generate the \fIMakefile\fR. This is the default. -.TP -.B --nogenerated-files -Do not generate the \fIMakefile\fR. -.TP -.B --wine32 -Generate a 32-bit target. This is useful on wow64 systems. -Without that option the default architecture is used. - -.SH EXAMPLES -.PP -Here is a typical \fBwinemaker\fR use: -.PP -$ winemaker --lower-uppercase -DSTRICT . -.PP -The above tells \fBwinemaker\fR to scan the current directory and its -subdirectories for source files. Whenever if finds a file or directory which -name is all uppercase, it should rename it to lowercase. It should then fix -all these source files for compilation with Winelib and generate \fIMakefile\fRs. -The \fB-DSTRICT\fR specifies that the \fBSTRICT\fR macro must be set when compiling -these sources. Finally a \fIMakefile\fR will be created. -.PP -The next step would be: -.PP -$ make -.PP -If at this point you get compilation errors (which is quite likely for a -reasonably sized project) then you should consult the Winelib User Guide to -find tips on how to resolve them. -.PP -For an MFC-based project you would have to run the following commands instead: -.PP -$ winemaker --lower-uppercase --mfc . -.br -$ make -.PP -For an existing project-file you would have to run the following commands: -.PP -$ winemaker myproject.dsp -.br -$ make -.PP - -.SH TODO / BUGS -In some cases you will have to edit the \fIMakefile\fR or source files manually. -.PP -Assuming that the windows executable/library is available, we could -use \fBwinedump\fR to determine what kind of executable it is (graphical -or console), which libraries it is linked with, and which functions it -exports (for libraries). We could then restore all these settings for the -corresponding Winelib target. -.PP -Furthermore \fBwinemaker\fR is not very good at finding the library containing the -executable: it must either be in the current directory or in the -.BR LD_LIBRARY_PATH . -.PP -\fBwinemaker\fR does not support message files and the message compiler yet. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AUTHORS -François Gouget for CodeWeavers -.br -Dimitrie O. Paun -.br -André Hentschel -.SH AVAILABILITY -.B winemaker -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH SEE ALSO -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winemine.1 b/assets/wine/share/man/man1/winemine.1 deleted file mode 100644 index b107183..0000000 --- a/assets/wine/share/man/man1/winemine.1 +++ /dev/null @@ -1,27 +0,0 @@ -.TH WINEMINE 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -winemine \- Wine Minesweeper game -.SH SYNOPSIS -.BR winemine -.SH DESCRIPTION -.B winemine -is the Wine Minesweeper game. The object of the game is to try to find all the hidden mines by -uncovering the tiles to see how many mines each tile is adjacent to, without uncovering a mine. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winemine -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/winepath.1 b/assets/wine/share/man/man1/winepath.1 deleted file mode 100644 index b1a701a..0000000 --- a/assets/wine/share/man/man1/winepath.1 +++ /dev/null @@ -1,47 +0,0 @@ -.TH WINEPATH 1 "November 2010" "Wine 10.17" "Wine Programs" -.SH NAME -winepath \- convert Unix paths to/from Win32 paths -.SH SYNOPSIS -.B winepath -.IR "option " { path } -.SH DESCRIPTION -.B winepath -is a tool to convert a Unix path to/from a Win32 (short/long) path -compatible with its Microsoft Windows counterpart. - -If more than one option is given then the input paths are output in -all formats specified, in the order long, short, Unix, Windows. -If no option is given the default output is Unix format. -.SH OPTIONS -.IP \fB\-u\fR,\fB\ \-\-unix -converts a Windows path to a Unix path. -.IP \fB\-w\fR,\fB\ \-\-windows -converts a Unix path to a long Windows path. -.IP \fB\-l\fR,\fB\ \-\-long -converts the short Windows path of an existing file or directory to the long -format. -.IP \fB\-s\fR,\fB\ \-\-short -converts the long Windows path of an existing file or directory to the short -format. -.IP \fB\-0 -separate output with \\0 character, instead of a newline. -.IP \fB\-h\fR,\fB\ \-\-help -shows winepath help message and exit. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B winepath -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wineserver.1 b/assets/wine/share/man/man1/wineserver.1 deleted file mode 100644 index 3c9d00c..0000000 --- a/assets/wine/share/man/man1/wineserver.1 +++ /dev/null @@ -1,107 +0,0 @@ -.TH WINESERVER 1 "October 2005" "Wine 10.17" "Windows on Unix" -.SH NAME -wineserver \- the Wine server -.SH SYNOPSIS -.B wineserver -.RI [ options ] -.SH DESCRIPTION -.B wineserver -is a daemon process that provides to Wine roughly the same services -that the Windows kernel provides on Windows. -.PP -.B wineserver -is normally launched automatically when starting \fBwine\fR(1), so you -shouldn't have to worry about it. In some cases however, it can be -useful to start \fBwineserver\fR explicitly with different options, as -explained below. -.SH OPTIONS -.TP -\fB\-d\fR[\fIn\fR], \fB--debug\fR[\fB=\fIn\fR] -Set the debug level to -.IR n . -0 means no debugging information, 1 is the normal level, and 2 is for -extra verbose debugging. If -.I n -is not specified, the default is 1. The debug output will be sent to -stderr. \fBwine\fR(1) will automatically enable normal level debugging -when starting \fBwineserver\fR if the +server option is set in the -\fBWINEDEBUG\fR variable. -.TP -.BR \-f ", " --foreground -Make the server remain in the foreground for easier debugging, for -instance when running it under a debugger. -.TP -.BR \-h ", " --help -Display a help message. -.TP -\fB\-k\fR[\fIn\fR], \fB--kill\fR[\fB=\fIn\fR] -Kill the currently running -.BR wineserver , -optionally by sending signal \fIn\fR. If no signal is specified, sends -a \fBSIGINT\fR first and then a \fBSIGKILL\fR. The instance of \fBwineserver\fR -that is killed is selected based on the \fBWINEPREFIX\fR environment -variable. -.TP -\fB\-p\fR[\fIn\fR], \fB--persistent\fR[\fB=\fIn\fR] -Specify the \fBwineserver\fR persistence delay, i.e. the amount of -time that the server will keep running when all client processes have -terminated. This avoids the cost of shutting down and starting again -when programs are launched in quick succession. The timeout \fIn\fR is -in seconds, the default value is 3 seconds. If \fIn\fR is not -specified, the server stays around forever. -.TP -.BR \-v ", " --version -Display version information and exit. -.TP -.BR \-w ", " --wait -Wait until the currently running -.B wineserver -terminates. -.SH ENVIRONMENT -.TP -.B WINEPREFIX -If set, the content of this variable is taken as the name of the directory where -.B wineserver -stores its data (the default is \fI$HOME/.wine\fR). All -.B wine -processes using the same -.B wineserver -(i.e.: same user) share certain things like registry, shared memory -and kernel objects. -By setting -.B WINEPREFIX -to different values for different Wine processes, it is possible to -run a number of truly independent Wine sessions. -.SH FILES -.TP -.B ~/.wine -Directory containing user specific data managed by -.BR wine . -.TP -.BI /tmp/.wine- uid -Directory containing the server Unix socket and the lock -file. These files are created in a subdirectory generated from the -\fBWINEPREFIX\fR directory device and inode numbers. -.SH AUTHORS -The original author of -.B wineserver -is Alexandre Julliard. Many other people have contributed new features -and bug fixes. For a complete list, see the git commit logs. -.SH BUGS -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B wineserver -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wmc.1 b/assets/wine/share/man/man1/wmc.1 deleted file mode 100644 index 0069513..0000000 --- a/assets/wine/share/man/man1/wmc.1 +++ /dev/null @@ -1,119 +0,0 @@ -.TH WMC 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -wmc \- Wine Message Compiler -.SH SYNOPSIS -.B wmc -.RI [ options ]\ [ inputfile ] -.SH DESCRIPTION -.B wmc -compiles messages from -.B inputfile -into FormatMessage[AW] compatible format encapsulated in a resourcescript -format. -.B wmc -outputs the data either in a standard \fI.bin\fR formatted binary -file, or can generated inline resource data. -.PP -.B wmc -takes only one \fIinputfile\fR as argument (see \fBBUGS\fR). The -\fIinputfile\fR normally has extension \fI.mc\fR. The messages are read from -standard input if no inputfile is given. If the outputfile is not specified -with \fB-o\fR, then \fBwmc\fR will write the output to \fIinputfile.{rc,h}\fR. -The outputfile is named \fIwmc.tab.{rc,h}\fR if no inputfile was given. -.SH OPTIONS -.TP -.B \-c -Set 'custom-bit' in message-code values. -.TP -.B \-d -NON-FUNCTIONAL; Use decimal values in output -.TP -.B \-D -Set debug flag. This results is a parser trace and a lot of extra messages. -.TP -.BR \-h ,\ \-\-help -Print an informative usage message and exits. -.TP -.BI \-H\ file -Write headerfile to \fIfile\fR. Default is \fIinputfile.h\fR. -.TP -.B \-i -Inline messagetable(s). This option skips the generation of all \fI.bin\fR files -and writes all output into the \fI.rc\fR file. This encoding is parsable with -wrc(1). -.TP -.BI \-\-nls-dir= directory -Specify the directory to search for the NLS files containing the -codepage mapping tables. -.TP -.BR \-o ,\ \-\-output =\fIfile -Output to \fIfile\fR. Default is \fIinputfile.rc\fR. -.TP -.BR \-O ,\ \-\-output\-format =\fIformat -Set the output format. Supported formats are \fBrc\fR (the default), -\fBres\fR, and \fBpot\fR. -.TP -.BR \-P ,\ \-\-po-dir =\fIdirectory -Enable the generation of resource translations based on po files -loaded from the specified directory. That directory must follow the -gettext convention, in particular in must contain one \fI.po\fR file for -each language, and a LINGUAS file listing the available languages. -.TP -.B \-u -Assume that the input file is in Unicode or UTF-8 format and skip -codepage conversions. -.TP -.B \-v -Show all supported codepages and languages. -.TP -.BR \-V ,\ \-\-version -Print version end exit. -.TP -.BR \-W ,\ \-\-pedantic -Enable pedantic warnings. -.SH EXTENSIONS -The original syntax is extended to support codepages more smoothly. Normally, -codepages are based on the DOS codepage from the language setting. The -original syntax only allows the destination codepage to be set. However, this -is not enough for non\-DOS systems which do not use unicode source-files. -.PP -A new keyword \fBCodepages\fR is introduced to set both input and output -codepages to anything one wants for each language. The syntax is similar to -the other constructs: -.PP -Codepages '=' '(' language '=' cpin ':' cpout ... ')' -.PP -The \fIlanguage\fR is the numerical language\-ID or the alias set with -LanguageNames. The input codepage \fIcpin\fR and output codepage -\fIcpout\fR are the numerical codepage IDs. There can be multiple mappings -within the definition and the definition may occur more than once. -.SH AUTHORS -.B wmc -was written by Bertho A. Stultiens. -.SH BUGS -The message compiler should be able to have multiple input files and combine -them into one output file. This would enable the splitting of languages into -separate files. -.PP -Decimal output is completely lacking. Don't know whether it should be -implemented because it is a, well, non-informative format change. It is -recognized on the commandline for some form of compatibility. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B wmc -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.BR wrc (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/man1/wrc.1 b/assets/wine/share/man/man1/wrc.1 deleted file mode 100644 index 8c4c519..0000000 --- a/assets/wine/share/man/man1/wrc.1 +++ /dev/null @@ -1,221 +0,0 @@ -.TH WRC 1 "October 2005" "Wine 10.17" "Wine Developers Manual" -.SH NAME -wrc \- Wine Resource Compiler -.SH SYNOPSIS -.B wrc -.RI [ options ]\ [ inputfile ...] -.SH DESCRIPTION -.B wrc -compiles resources from \fIinputfile\fR -into win16 and win32 compatible binary format. -.PP -The source file is preprocessed with a builtin ANSI\-C compatible -preprocessor before the resources are compiled. See \fBPREPROCESSOR\fR -below. -.PP -.B wrc -takes a series of \fIinputfile\fR as argument. The resources are read from -standard input if no inputfile is given. If the output file is not -specified with \fB-o\fR, then \fBwrc\fR will write the output to -\fIinputfile.res\fR with \fI.rc\fR stripped, or to \fIwrc.tab.res\fR if -no inputfile was given. -.SH OPTIONS -.TP -.I \fB\-D\fR, \fB\-\-define\fR=\fIid\fR[\fB=\fIval\fR] -Define preprocessor identifier \fIid\fR to (optionally) value \fIval\fR. -See also -.B PREPROCESSOR -below. -.TP -.I \fB\-\-debug\fR=\fInn\fR -Set debug level to \fInn\fR. The value is a bitmask consisting of -1=verbose, 2=dump internals, 4=resource parser trace, 8=preprocessor -messages, 16=preprocessor scanner and 32=preprocessor parser trace. -.TP -.I \fB\-E\fR -Preprocess only. The output is written to standard output if no -outputfile was selected. The output is compatible with what gcc would -generate. -.TP -.I \fB\-h\fR, \fB\-\-help\fR -Prints a summary message and exits. -.TP -.I \fB\-i\fR, \fB\-\-input\fR=\fIfile\fR -The name of the input file. If this option is not used, then \fBwrc\fR -will use the first non-option argument as the input file name. If there -are no non-option arguments, then \fBwrc\fR will read from standard input. -.TP -.I \fB\-I\fR, \fB\-\-include\-dir\fR=\fIpath\fR -Add \fIpath\fR to the list of directories to search for includes. It -is allowed to specify \fB\-I\fR multiple times. Include files are -searched in the order in which the \fB\-I\fR options were specified. -.br -The search is compatible with gcc, in which '<>' quoted filenames are -searched exclusively via the \fB\-I\fR set path, whereas the '""' quoted -filenames are first tried to be opened in the current directory. Also -resource statements with file references are located in the same way. -.TP -.I \fB\-J\fR, \fB\-\-input\-format\fR=\fIformat\fR -Sets the input format. Valid options are 'rc' or 'rc16'. Setting the -input to 'rc16' disables the recognition of win32 keywords. -.TP -.I \fB\-l\fR, \fB\-\-language\fR=\fIlang\fR -Set default language to \fIlang\fR. Default is the neutral language 0 -(i.e. "LANGUAGE 0, 0"). -.TP -.B \-m16, -m32, -m64 -Generate resources for 16-bit, 32-bit or 64-bit platforms respectively. -The only difference between 32-bit and 64-bit is whether -the _WIN64 preprocessor symbol is defined. -.TP -.I \fB\-\-nls-dir=\fIdir\fR -Specify the directory to search for the NLS files containing the -codepage mapping tables. -.TP -.I \fB\-\-nostdinc\fR -Do not search the standard include path, look for include files only -in the directories explicitly specified with the \fB\-I\fR option. -.TP -.I \fB\-\-no\-use\-temp\-file\fR -Ignored for compatibility with \fIwindres\fR. -.TP -.I \fB\-o\fR, \fB\-fo\fR, \fB\-\-output\fR=\fIfile\fR -Write output to \fIfile\fR. Default is \fBinputfile.res\fR -with \fB.rc\fR stripped or \fBwrc.tab.res\fR if input is read -from standard input. -.TP -.I \fB\-O\fR, \fB\-\-output\-format\fR=\fIformat\fR -Sets the output format. The supported formats are \fBpo\fR, \fBpot\fR, -\fBres\fR, and \fBres16\fR. If this option is not specified, the -format defaults to \fBres\fR. -.br -In \fBpo\fR mode, if an output file name is specified it must match a -known language name, like \fBen_US.po\fR; only resources for the -specified language are output. If no output file name is specified, a -separate \fI.po\fR file is created for every language encountered in the -input. -.TP -.I \fB\-\-pedantic\fR -Enable pedantic warnings. Notably redefinition of #define statements can -be discovered with this option. -.TP -.I \fB\-\-po-dir=\fIdir\fR -Enable the generation of resource translations based on mo files -loaded from the specified directory. That directory must follow the -gettext convention, in particular it must contain one \fI.mo\fR file for -each language, and a LINGUAS file listing the available languages. -.TP -.I \fB\-r\fR -Ignored for compatibility with \fIrc\fR. -.TP -.I \fB\-\-preprocessor\fR=\fIprogram\fR -This option may be used to specify the preprocessor to use, including any -leading arguments. If not specified, \fBwrc\fR uses its builtin processor. -To disable preprocessing, use \fB--preprocessor=cat\fR. -.TP -.I \fB\-\-sysroot=\fIdir\fR -Prefix the standard include paths with \fIdir\fR. -.TP -.I \fB\-\-utf8\fR, \fB\-u\fR -Set the default codepage of the input file to UTF-8. -.TP -.I \fB\-U\fR, \fB\-\-undefine\fR=\fIid\fR -Undefine preprocessor identifier \fIid\fR. Please note that only macros -defined up to this point are undefined by this command. However, these -include the special macros defined automatically by \fIwrc\fR. -See also -.B PREPROCESSOR -below. -.TP -.I \fB\-\-use\-temp\-file\fR -Ignored for compatibility with \fIwindres\fR. -.TP -.I \fB\-v\fR, \fB\-\-verbose\fR -Turns on verbose mode (equivalent to \fB-d 1\fR). -.TP -.I \fB\-\-version\fR -Print version and exit. -.SH PREPROCESSOR -The preprocessor is ANSI\-C compatible with some of the extensions of -the gcc preprocessor. -.PP -The preprocessor recognizes these directives: #include, #define (both -simple and macro), #undef, #if, #ifdef, #ifndef, #elif, #else, #endif, -#error, #warning, #line, # (both null\- and line\-directive), #pragma -(ignored), #ident (ignored). -.PP -The preprocessor sets by default several defines: -.br -- RC_INVOKED set to 1 -.br -- __WRC__ Major version of wrc -.br -- __WRC_MINOR__ Minor version of wrc -.br -- __WRC_PATCHLEVEL__ Patch level -.PP -Win32 compilation mode also sets _WIN32 to 1. -.PP -Special macros __FILE__, __LINE__, __TIME__ and __DATE__ are also -recognized and expand to their respective equivalent. -.SH "LANGUAGE SUPPORT" -Language, version and characteristics can be bound to all resource types that -have inline data, such as RCDATA. This is an extension to Microsoft's resource -compiler, which lacks this support completely. Only VERSIONINFO cannot have -version and characteristics attached, but languages are propagated properly if -you declare it correctly before the VERSIONINFO resource starts. -.PP -Example: -.PP -.nf -1 RCDATA DISCARDABLE -LANGUAGE 1, 0 -VERSION 312 -CHARACTERISTICS 876 -{ - 1, 2, 3, 4, 5, "and whatever more data you want" - '00 01 02 03 04 05 06 07 08' -} -.SH AUTHORS -.B wrc -was written by Bertho A. Stultiens and is a nearly complete rewrite of -the first wine resource compiler (1994) by Martin von Loewis. -Additional resource types were contributed by Ulrich Czekalla and Albert -den Haan. Many cleanups by Dimitrie O. Paun in 2002-2003. -Bugfixes have been contributed by many Wine developers. -.SH BUGS -\- The preprocessor recognizes variable argument macros, but does not -expand them correctly. -.br -\- Error reporting should be more precise, as currently the column and -line number reported are those of the next token. -.br -\- Default memory options should differ between win16 and win32. -.PP -There is no support for: -.br -\- RT_DLGINCLUDE, RT_VXD, RT_PLUGPLAY and RT_HTML (unknown format) -.br -\- PUSHBOX control is unsupported due to lack of original functionality. -.PP -Fonts are parsed and generated, but there is no support for the -generation of the FONTDIR yet. The user must supply the FONTDIR -resource in the source to match the FONT resources. -.PP -Bugs can be reported on the -.UR https://bugs.winehq.org -.B Wine bug tracker -.UE . -.SH AVAILABILITY -.B wrc -is part of the Wine distribution, which is available through WineHQ, -the -.UR https://www.winehq.org/ -.B Wine development headquarters -.UE . -.SH "SEE ALSO" -.BR wine (1), -.br -.UR https://www.winehq.org/help -.B Wine documentation and support -.UE . diff --git a/assets/wine/share/man/pl.UTF-8/man1/wine.1 b/assets/wine/share/man/pl.UTF-8/man1/wine.1 deleted file mode 100644 index 154ca35..0000000 --- a/assets/wine/share/man/pl.UTF-8/man1/wine.1 +++ /dev/null @@ -1,281 +0,0 @@ -.\" -*- nroff -*- -.TH WINE 1 "October 2005" "Wine 10.17" "Windows On Unix" -.SH NAZWA -wine \- uruchamiaj programy Windowsowe na Uniksie -.SH SKŁADNIA -.B wine -.IR program " [" opcje ] -.br -.B wine --help -.br -.B wine --version -.PP -Informacji na temat przekazywania opcji programom Windowsowym szukaj w rozdziale -.B OPCJE -tej instrukcji. -.SH OPIS -.B wine -ładuje i wykonuje dany program, gdzie program to plik wykonywalny DOSa, Windowsa -3.x lub Win32 (tylko binarne x86). -.PP -Do debugowania wine lepiej jednak użyć -.B winedbg -.PP -Do uruchamiania plików wykonywalnych CUI (programy konsolowe Windowsa) używaj -.B wineconsole -zamiast -.BR wine . -Spowoduje to, że całe wyjście zostanie pokazane w osobnym oknie (wymaganiem jest uruchomiony X11). -Przez nie użycie -.B wineconsole -do programów CUI otrzymasz ograniczone wsparcie dla konsoli -,a twój program może nie zadziałać prawidłowo. -.PP -Gdy wywołasz wine z -.B --help -lub -.B --version -jako jedyną opcją, -.B wine -pokaże małą informację pomocy lub odpowiednio wyświetli swoją wersję i zakończy działanie. -.SH OPCJE -Nazwa programu może być określona w formacie DOS -.RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE ) -lub w formacie Unix -.RI ( /msdos/windows/sol.exe ). -Możesz dodać opcje do wykonywanego programu przez dodanie ich do -końca wywołania linii wiersza poleceń -.B wine -(tak jak np.: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT). -Zauważ, że musisz '\(rs' poradzić sobie ze znakami specjalnymi (i spacjami) podczas wywoływania Wine przez -powłokę, np. -.PP -wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe -.PP -.SH ZMIENNE ŚRODOWISKOWE -.B wine -udostępnia zmienne środowiskowe z powłoki, z której wystartował -.B wine -programom windowsowym/dosowym, więc używaj odpowiedniej składni -twojej powłoki, aby wpisać zmienne środowiskowe, których potrzebujesz. -.TP -.B WINEPREFIX -Jeżeli ta zmienna jest ustawiona, to jej zawartość jest brana jako nazwa katalogu gdzie -.B wine -przechowuje swoje dane (domyślny katalog to -.IR $HOME/.wine ). -Katalog ten jest także wykorzystywany do identyfikacji gniazda używanego do -porozumiewania się z -.IR wineserver . -Wszystkie procesy -.B wine -używające tego samego -.B wineserver -(np.: ten sam użytkownik) dzielą pewne elementy takie jak rejrestr, współdzielona pamięć, -i plik konfiguracyjny. -Poprzez ustawianie -.I WINEPREFIX -na inne wartości dla różnych procesów -.B wine -jest możliwe uruchamianie kilka prawdziwie niezależnych procesów -.BR wine . -.TP -.B WINESERVER -Określa ścieżkę i nazwę programu binarnego -.B wineserver -Jeżeli nie ustawione, Wine będzie szukał pliku o nazwie "wineserver" w -podanej ścieżce i kilku innych miejscach prawdopodobnego występowania. -.TP -.B WINEDEBUG -Włącza lub wyłącza wiadomości debuggera. Składnia zmiennej -wygląda następująco -.RI [ klasa ][+/-] kanał [,[ klasa2 ][+/-] kanał2 ]. -.RS +7 -.PP -.I klasa -jest opcjonalna i może być jedną z następujących: -.BR err , -.BR warn , -.BR fixme , -lub -.BR trace . -Jeżeli -.I klasa -nie jest określona, to wszystkie wiadomości debuggera dla określonego -kanału są wyłączone. Każdy kanał będzie wyświetlał wiadomości o poszczególnym -komponencie -.BR wine . -Następny znak może być albo + albo - i służy odpowiednio do włączenia albo wyłączenia -określonego kanału. Jeżeli nie ma części -.I klasa -przed nim, to znak znaczący + może być pominięty. Zauważ, że spacje są niedozwolone -w żadnym miejscu łańcucha znaków. -.PP -Przykłady: -.TP -WINEDEBUG=warn+all -włączy wszystkie ostrzeżenia (zalecane przy debugowaniu). -.br -.TP -WINEDEBUG=warn+dll,+heap -włączy wszystkie ostrzeżenia bibliotek DLL i wszystkie wiadomości stosu. -.br -.TP -WINEDEBUG=fixme-all,warn+cursor,+relay -wyłączy wszystkie wiadomości FIXME, włączy ostrzeżenia kursora i -wszystkie wiadomości relay (wywołania API). -.br -.TP -WINEDEBUG=relay -włączy wszystkie wiadomości relay. Aby mieć większą kontrolę przy uwzględnianiu i wykluczaniu -funkcji i bibliotek dll ze śladu relay, zapoznaj się z kluczem rejestru -.B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug -.PP -Informacji na temat wiadomości debugera szukaj w rozdziale -.I Running Wine -z Przewodnika użytkownika Wine. -.RE -.TP -.B WINEDLLPATH -Określa ścieżkę/ki, w których należy szukać wbudowanych bibliotek dll i programów -Winelib. To lista katalogów oddzielonych znakiem ":". W dodatku do -każdego katalogu określonego w -.IR WINEDLLPATH , -Wine będzie także szukał w katalogu instalacyjnym. -.TP -.B WINEDLLOVERRIDES -Definiuje typ nadpisania i kolejność ładowania bibliotek dll użytych do ładowania -procesu dla jakiejkolwiek biblioteki dll. Obecnie istnieją dwa typy bibliotek, które można załadować -do przestrzeni adresowej procesu: natywne biblioteki Windowsa -.RI ( native ), -.B wine -wewnętrzne biblioteki dll -.RI ( builtin ). -Typ może być skrócony przez pierwszą literkę typu -.RI ( n ", " b ). -Biblioteka może być także całkowicie wyłączona (''). Każda sekwencja rozkazów musi być oddzielona przecinkami. -.RS -.PP -Każda biblioteka dll może mieć swoją własną kolejność ładowania. Kolejność ładowania -określa, którą wersję biblioteki dll będzie się próbowało załadować do -przestrzeni adresowej. Jeżeli pierwsza zawiedzie, to próbowana jest następna i tak dalej. -Wiele bibliotek z tą samą kolejnością ładowania może być oddzielona przecinkami. -Istnieje także możliwość określenia różnych kolejności ładowania dla różnych bibliotek -przez oddzielanie wpisów znakiem ";". -.PP -Kolejność ładowania dla 16-bitowej biblioteki dll jest zawsze określona przez kolejność ładowania -32-bitowej biblioteki dll, która ją zawiera (co może być rozpoznane przez podgląd -symbolicznych dowiązań 16-bitowego pliku .dll.so). Dla przykładu jeżeli biblioteka -ole32.dll jest skonfigurowana jako wbudowana, to biblioteka storage.dll będzie również zładowana jako -wbudowana, ponieważ 32-bitowa biblioteka ole32.dll zawiera 16-bitową bibliotekę -storage.dll. -.PP -Przykłady: -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n,b" -.br -Spróbuj załadować comdlg32 i shell32 jako natywne biblioteki windowsowe i powróć -do wersji wbudowanych jeżeli natywne zawiodą. -.TP -WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b" -.br -Spróbuj załadować comdlg32 i shell32 jako natywne biblioteki windowsowe. Dodatkowo, jeżeli -program zażąda załadowania c:\(rsfoo\(rsbar\(rsbaz.dll to załaduj wbudowaną bibliotekę rsbaz. -.TP -WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32=" -.br -Najpierw spróbuj załadować comdlg32 jako wbudowaną i skorzystaj z wersji natywnej jeżeli -wbudowane zawiodą; zawsze ładuj shell32 jako wbudowaną i comctl32 -jako natywną. Oleaut32 pozostaw wyłączone. -.RE -.TP -.B WINEARCH -Określa jaką architekturę Windowsa wspierać. Może to być zarówno -.B win32 -(wsparcie tylko 32-bitowych programów), lub -.B win64 -(wsparcie dla programów 64-bitowych jak i 32-bitowych w trybie WoW64). -.br -Architektura wspierana przez dany prefiks Wine jest ustawiana już w momencie tworzenia prefiksa -i nie może być później zmieniona. Gdy opcja zostanie uruchomiona z istniejącym -prefiksem, Wine odmówi uruchomienie jeżeli -.I WINEARCH -nie zgadza się z architekturą prefiksu. -.TP -.B DISPLAY -Określa, którego wyświetlacza X11 użyć. -.TP -Zmienne konfiguracyjne sterownika dźwięku OSS -.TP -.B AUDIODEV -Ustaw urządzenie dla wejścia / wyjścia dźwięku. Domyślnie -.BR /dev/dsp . -.TP -.B MIXERDEV -Ustaw urządzenie dla suwaków miksera. Domyślnie -.BR /dev/mixer . -.TP -.B MIDIDEV -Ustaw urządzanie MIDI (sekwencer). Domyślnie -.BR /dev/sequencer . -.SH FILES -.TP -.I wine -Ładowarka programów -.B wine -.TP -.I wineconsole -Ładowarka programów -.B wine -dla aplikacji CUI (konsolowych). -.TP -.I wineserver -Serwer -.B wine -.TP -.I winedbg -Debugger -.B wine -.TP -.I $WINEPREFIX/dosdevices -Katalog zawierający mapowania urządzeń DOS. Każdy plik w tym -katalogu jest dowiązaniem symbolicznym do pliku urządzenia Uniksowego implementującego -dane urządzenie. Dla przykładu, jeżeli COM1 byłoby zmapowane do /dev/ttyS0 to miałbyś -symboliczene dowiązanie w formie $WINEPREFIX/dosdevices/com1 -> /dev/ttyS0. -.br -Napędy DOS również są określone przez dowiązania symboliczne; Dla przykładu jeżeli napęd D: -odpowiadałby napędowi CDROM zamontowanemu w /mnt/cdrom, miałbyś dowiązanie symboliczne -$WINEPREFIX/dosdevices/d: -> /mnt/cdrom. Urządzenia Uniksowe odpowiadające -napędom DOS mogą być określone w ten sam sposób, z użyciem '::' zamiast ':'. -Tak więc dla poprzedniego przykładu, jeżeli urządzenie CDROM byłoby zamontowane -z /dev/hdc, to odpowiadające dowiązanie symboliczne wyglądałoby następująco -$WINEPREFIX/dosdevices/d:: -> /dev/hdc. -.SH AUTORZY -.B wine -jest dostępne dzięki pracy wielu programistów. Lista autorów -jest dostępna w pliku -.B AUTOHORS -w głównym katalogu dystrybucyjnym źródła. -.SH PRAWA AUTORSKIE -.B wine -może być rozpowszechniane pod warunkami licencji LGPL. Kopia -licencji jest dostępna w pliku -.B COPYING.LIB -w głównym katalogu dystrybucyjnym źródła. -.SH BŁĘDY -.PP -Raporty stanu działania programów są dostępne na stronie -.IR https://appdb.winehq.org . -Jeżeli brakuje na liście aplikacji, której używasz, to nie wahaj się -dodać jej samodzielnie. -.PP -Raporty błędów mogą być wysyłane do Wine Bugzilla -.I https://bugs.winehq.org -.SH DOSTĘPNOŚĆ -Najaktualniejszą publiczną wersję -.B wine -można pobrać ze strony -.I https://www.winehq.org -.SH "ZOBACZ TAKŻE" -.BR wineserver (1), -.BR winedbg (1)