wosclib-users — Mailing list for WOscLib Users

Re: [Wosclib-users] Errors in latest version

[Angelo F. <new...@sm...>]

I have made a fix for this. It now builds without errors or warnings

https://github.com/angelofraietta/WOscLib.git


On Fri, Jul 6, 2018 at 5:03 PM, Angelo Fraietta <
new...@sm...> wrote:

> I get these errors trying to make library.
>
> ./WOscTcpHandler.h:105:37: error: cannot initialize return object of type
> 'int'
> with an lvalue of type 'const pthread_t' (aka '_opaque_pthread_t
>
>
>
> *const')int GetRxThreadID() const { return m_receptionThreadID;
> }^~~~~~~~~~~~~~~~~~~WOscTcpHandler.cpp:169:27: error: ordered comparison
> between pointer and zero('pthread_t' (aka '_opaque_pthread_t *') and
> 'int')
> if ( m_receptionThreadID > 0 )
>
> also a warning
> WOscTimeTag.cpp:290:12: warning: use of unary operator that may be
> intended as
> compound assignment (+=)
> m_timeTag =+ rhs.m_timeTag;
>
>
> Is anyone currently supporting this or is there a working branch?
>
> If not, does anyone know if there is a branch we should upload fixes to?
>

[Wosclib-users] Errors in latest version

[Angelo F. <new...@sm...>]

I get these errors trying to make library.

./WOscTcpHandler.h:105:37: error: cannot initialize return object of type
'int'
with an lvalue of type 'const pthread_t' (aka '_opaque_pthread_t



*const')int GetRxThreadID() const { return m_receptionThreadID;
}^~~~~~~~~~~~~~~~~~~WOscTcpHandler.cpp:169:27: error: ordered comparison
between pointer and zero('pthread_t' (aka '_opaque_pthread_t *') and 'int')
if ( m_receptionThreadID > 0 )

also a warning
WOscTimeTag.cpp:290:12: warning: use of unary operator that may be intended
as
compound assignment (+=)
m_timeTag =+ rhs.m_timeTag;


Is anyone currently supporting this or is there a working branch?

If not, does anyone know if there is a branch we should upload fixes to?

[Wosclib-users] New build system, library redesign

[Uli F. <cl...@ne...>]

Hi everybody

There's a new release available (wosclib-0.20-pre00.zip)

Note that this is a pre-release and gives a preview what is to expect with the
next release. Note that some refactoring is required in projects which make use
of previous releases.

* New library design. No copy operation or memory allocation on heap during
message reception which results in heavy speed improvements
* More TCP support
* Testbench (any volunteers for writing more tests?)
* The build system now uses autotools from A to Z
* Support for pkg-config, make install and alike

Regards
Uli