[zeromq-dev] Any progress on 64-bit Windows build

Mikael Helbo Kjær mhk at designtech.dk
Mon Oct 4 08:53:23 CEST 2010


Hi Steven

 

Well it is good news about the CRT stuff. 

 

About the MIB_IFROW::wszName field isn't it just a question of how the WCHAR define ends up. If you expect a MBCS value and a string is UNICODE a conversion function (mbstowcs_s) is available AFAIK even with the /Zc:wchar_t- value set in the compiler no matter if the compiler treats wchar_t as a native type or a define to unsigned short (which is what is does with the above option set). 

 

I bet you knew this so what am I misunderstanding? I would very much like to help.

 

Regards,

Mikael

 

Security enhanced CRT usage is now configurable with  CONFIG_HAVE_SECURITY_ENHANCED_CRT.

 

Native wide character support is complicated, MSVC forwards on _NATIVE_WCHAR_T_DEFINED but without the conversion APIs data structures that have defined WCHAR member variables are unusable?

 

I need a multi-byte string value of MIB_IFROW::wszName.

 

http://msdn.microsoft.com/en-us/library/aa366836(VS.85).aspx

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101004/426bfd72/attachment.htm>


More information about the zeromq-dev mailing list