[Bug 46676] Serial port enumeration (get device description) on Mac OS/ X 10.9, 10.13

[wine-bugs at winehq.org]

https://bugs.winehq.org/show_bug.cgi?id=46676

--- Comment #4 from Alexandre Julliard <julliard at winehq.org> ---
(In reply to Martin Hinner from comment #2)
> Re https://www.winehq.org/pipermail/wine-devel/2009-February/073133.html 
> 
> Recompilation using libwine is not feasible as our code is quite MSVC
> specific, also including some assembly language. We should also consider MFC
> recompilation legality. Simply Linux/Mac userbase is so small that we cannot
> spend time on this.
> 
> On the other hand, modifying single class that does serial port enumeration
> and communication is VERY simple.
> 
> I understand we can make "serial driver DLL" and very simple .dll.so  that
> would do the same job on Unix/Wine, however this is not very practical as we
> would have to maintain library dependencies, develop different versions (one
> for BSD, one for Linux, one for Mac). On the other hand detecting host OS
> type is fairly simple by trying to dlopen a few libraries/functions (if they
> fail we can always fallback to Windows serial ports and trust Wine it is
> completely supported like it is now on Linux). It is all POSIX, so Unix part
> would be simply just a simple library with a few system dependent tweaks.
> 
> It would also make bluetooth connection possible, which is AFAIK totally
> impossible with wine (We would simply let user connect rfcomm device from
> the host system and then use it using open()/read()/write()/select()
> acquired from wine_dlopen).

You should be able to configure the device as a serial port in the registry,
even if it's not enumerated by setupapi, cf.
https://wiki.winehq.org/Wine_User%27s_Guide#Serial_and_Parallel_Ports

Providing a generic way to call host functions doesn't make much sense, because
the calling conventions are usually not compatible, and in general the
functions wouldn't be compatible across Unix platforms either. It would only
work for very simple hacks, it's not the general mechanism that it looks like.

-- 
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.