Re: [Hamlib-developer] Yaesu FTX-1--target for 4.7.0?

[G0GJV <g0...@go...>]

I'm not suggesting getting rid of threading - just that I don't think it is 
needed in rig.h, where it makes compilation of user code with MSVC 
difficult. Hamlib itself can use it with the mingw libraries; if rig.h 
facilities need it then provide a separate interface into it.

Mike

> It might be possible but a lot of things won't work - some by design 
> (multicast, async data like IC-7300 spectrum, etc.), and some by bit 
> rot(CW keying, multiple connections to rigctld, maybe multithreaded 
> applications).  I'm not sure it's worth the effort since any app with a 
> GUI nowadays will probably be using threads.
> 
> The #ifdef/#endif usage by the thread code is very suspect - it would 
> require vetting each one, and fixing the '#include "config.h"' usage in 
> each file.  It's easier to just use it as required.
> 
> 73 n3gb
> 
> On 6/19/25 3:24 PM, G0GJV wrote:
> > Could we get rid of threads entirely from rig.h? I've never understood
> > why Mike wanted it there.
> >
> > Mike G0GJV
> >
> >> 4.6.x won't compile without P_THREADS - make that an overt requirement.
> >