https://bugs.winehq.org/show_bug.cgi?id=51793
Bug ID: 51793 Summary: winegcc doesn't work with CMake well Product: Wine Version: 6.17 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winelib Assignee: wine-bugs@winehq.org Reporter: kolan_n@mail.ru Distribution: ---
I know, it is not quite a bug in wine, but a bug in CMake, but probably should also be tracked here.
When I set `winegcc` and `wineg++` as compilers for CMake, I have issues with the software. When cmake generates the file for the low-level build system (I use `ninja`), it (correctly, as it matches the convention in Linux) generates the path without `.so` in the end and with soversion in the file name (`lib*.so.<soversion>`) for the libraries to be linked against. But the built libs files themselves ... have both soversion and so extension in the end (`lib*.so.<soversion>.so)`, in addition to the one before soversion.
It disrupts building process.
Also, the libraries with WinAPI are not linked automatically and have to be manually specified, so one has to detect if `winegcc` was used as a compiler and add the libs manually.