< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Compile warnings under Visual Studio 10


I’ve committed another update.  Starting with VS2010 the EXXX Berkeley style codes are defined in errno.h and are different than WSAXXX codes.  Resip has to force the definitions the same to allow comparing getErrno() returns to EXXX error codes.  The warnings for these macro redefinitions have been disabled.  Normalizing the socket error codes to RESIP_XXX would be one way to solve this if the current re-definition becomes a problem. 

 

-justin

 

From: resiprocate-users-bounces@xxxxxxxxxxxxxxx [mailto:resiprocate-users-bounces@xxxxxxxxxxxxxxx] On Behalf Of Scott Godin
Sent: Friday, July 23, 2010 2:44 PM
To: Paul Fisher
Cc: resiprocate-users@xxxxxxxxxxxxxxx
Subject: Re: [reSIProcate-users] Compile warnings under Visual Studio 10

 

Hi Paul,

 

 

Thanks,

Scott

 

On Thu, Jul 22, 2010 at 7:51 PM, Paul Fisher <paul.fisher@xxxxxxxxxxxxx> wrote:

I just compiled version 1.6 of the stack using Visual Studio 10 and received many compile warnings for redefined macros.

“POSIX SUPPLEMENT” defines have been added at the end of VS 10 errno.h with macro definitions that conflict with

Names in reSIProcate Socket.hxx (e.g., EWOULDBLOCK). I got it to compile without warnings by undefining the macros

First in Socket.hxx, but there must be a better long-term solution.

 

Paul Fisher | Software Engineer | inContact
____________________________________________________________________
p. +1.801.320.3456 | e. paul.fisher@xxxxxxxxxxxxx  | w. http://www.inContact.com

 http://www.facebook.com/inContact

 http://www.twitter.com/inContact

 

 

 


Email Confidentiality Notice: The information contained in this transmission is confidential, proprietary or privileged and may be subject to protection under the law.  The message is intended for the sole use of the individual or entity to whom it is addressed. If you are not the intended recipient, you are notified that any use, distribution or copying of the message is strictly prohibited and may subject you to criminal or civil penalties. If you received this transmission in error, please contact the sender immediately by replying to this email and delete the material from any computer.


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