Hello all!
I am trying to port a Windows C++ application (service) to Linux.
The desire is to be Linux native as much as possible.
While the service has a thin layer of OS abstraction (i.e. I can just plug 'eventfd' instead CreateSemaphoreA and etc), it becomes more complex when talking about replacing winHttp.
I was hoping to use the Wine winhttp implementation to replace the native windows version, instead of switching to libcurl or other.
However, from my readings (and experiments), it seems I can't cherry pick out of the blue a Wine .so and link on it, my project need to be more Wine aware, build with wineg++ and etc.
Question :
Is there a way that could work in a relatively native way? (linking on winhttp and others with standard g++, and without spawning a wineserver).
It does not have to match the Windows ABI, and can recompile everything that needs to be.
Worst case, I could spawn on my side a new LGPL library 're-using' wine dlls code from (git submodule), and worst-worst case fork/modify it, but I would really like to avoid it.
Thx for the help,
Julien
Using wine libs in standard Linux server application.
-
- Newbie
- Posts: 1
- Joined: Tue Apr 29, 2025 9:59 am