[Bug 51795] New: Document usage of winelib manually without relying for it on higher-level tools like winegcc and winemaker
WineHQ Bugzilla
wine-bugs at winehq.org
Fri Sep 24 15:18:35 CDT 2021
https://bugs.winehq.org/show_bug.cgi?id=51795
Bug ID: 51795
Summary: Document usage of winelib manually without relying for
it on higher-level tools like winegcc and winemaker
Product: Wine
Version: 6.17
Hardware: x86-64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: winelib
Assignee: wine-bugs at winehq.org
Reporter: kolan_n at mail.ru
Distribution: ---
I am building some software (I don't think I should give a link, because I have
left it in completely broken state currently). The build system used is CMake.
Currently I rely on winegcc (without much success, the build with CMake fails,
but if I fix the generated scripts manually, it succeeds, though the app still
refuses to start, it may be that I do something wrong). I'd like to use any
compiler supported by CMake for it. It'd be nice to have a doc that is not
focused on the high-level tools, but that is focused on what is going on and
what steps are advised to be made to get a working app in ELF format, that can
be debugged using regular gdb/lldb.
Also it'd he nice to know if I can link libraries in PE format to it. My main
motivation for using winelib is debugging of software using Qt Creator, , which
currently cannot interface winedbg (even in gdb mode), while running the
software being dehugged upon Linux (and not involving real Windows anyhow).
--
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.
More information about the wine-bugs
mailing list