Re: [Hamlib-developer] (no subject)

[Black M. <mdb...@ya...>]

That should be fixed in the github repository now -- package will be available 20220904 later tonight.
Mike W9MDB

 

    On Saturday, September 3, 2022 at 10:49:28 AM CDT, G0GJV <g0...@go...> wrote:  
 
 Mike

It's showing promise; I have to define HAVE_STRUCT_TIMESPEC or timespec gets defined 
twice

More testing needed.

Mike G0GJV

> I may have another solution.
> There is a NUGet pthread package.
> Can you add that to your project and then change rig.hFrom#if defined(_MSC_VER)#include
> <hamlib/winpthreads.h>#else#include <pthread.h>#endif
> To just#include <pthread.h>
> And see if that compiles cleanly for you.  I would prefer not to
> reinvent the wheel -- especially if there's a working pthread package
> for MSVC.
> Mike W9MDB
> 
> 
> 
>  
> 
>    On Wednesday, August 31, 2022 at 10:15:38 AM CDT, G0GJV <g0...@go...>
> wrote:  
>  
>  I've gone back to basics, and regenerated everything.
> 
> I can now build and run with MSVC. My main Qt build now has it's own 
> compilation issues - none of you concern!
> 
> BUT if I add e.g.
> 
> #include <io.h>
> 
> after
> 
> #include <hamlib/rig.h>
> 
> the #defines of /* Wrap cancellation points */
> 
> after l1381 in winpthreads.h causes all sorts of problems.
> 
> I note that in the original pthreads.h these get skipped unless 
> __WINPTRHEAD_ENABLE_WRAP_API is defined.
> 
> Maybe this should be included in your winpthreads.h?
> 
> Also, if you include rig.h in multiple compilation units, I get linker 
> complaints that the winpthreads functions are defined multiple times.
> 
> Mike G0GJV
> 
> > I still cannot compile and run with MSVC
> > 
> > What are you compiling, with which compiler?
> > 
> > Mike G0GJV
> > 
> > > So what's your status on this?  My compile worked.
> > > 
> > > Mike W9MDB





_______________________________________________
Hamlib-developer mailing list
Ham...@li...
https://lists.sourceforge.net/lists/listinfo/hamlib-developer