Re: [reSIProcate-users] resiprocate-1.4

[Byron Campen <bcampen@xxxxxxxxxxxx>]

Those preprocessor flags are no longer present in any of the header-files; that way any program including the headers will see the same API as the build-system did when the libs were built. In other words, the headers are exactly the same whether USE_IPV6 or USE_SSL are set. The exception is headers for classes that only make sense if SSL is enabled; OpenSSLInit, Security, TlsTransport, etc. If USE_SSL is disabled in the build, these headers are not installed at all, so there is no way to cause API/ABI mismatch by including them. If you are working with a source tree, you'll get linker errors, but not core dumps.

Best regards,

Byron Campen

Hi Byron, I saw the release note:

Working with installed resip headers/libs no longer requires setting the USE_SSL and USE_IPV6 preprocessor macros to avoid API/ABI mismatch issues.

 

What's meaning of this point? I saw the resiprocate project still using USE_SSL and USE_IPV6 marcros.

Does there has a way to switch the SSL and no-SSL libs dynamically?

Thanks.

 

On Fri, Oct 24, 2008 at 1:44 PM, Byron Campen <bcampen@xxxxxxxxxxxx> wrote:

       resiprocate-1.4 is now available. Details at http://www.resiprocate.org/ReSIProcate_1.4_Release

Best regards,
Byron Campen


_______________________________________________
resiprocate-users mailing list
resiprocate-users@xxxxxxxxxxxxxxx
List Archive: http://list.resiprocate.org/archive/resiprocate-users/

Attachment: smime.p7s
Description: S/MIME cryptographic signature