Hi Viktor,
I can't see any reason why this have to be compiler specific, please elaborate.
In the beginning of hbsocket.c you can see .- ... #elif defined( HB_OS_WIN ) # if defined( __WATCOMC__ ) # if ( NTDDI_VERSION >= 0x06000000 ) # define HB_HAS_INET_PTON # define HB_HAS_INET_NTOP # endif # define HB_HAS_SOCKADDR_STORAGE /* # define HB_HAS_INET6 */ # elif defined( __MINGW32__ ) # define HB_HAS_SOCKADDR_STORAGE # elif defined( __POCC__ ) && !defined( __XCC__ ) # define HB_HAS_SOCKADDR_STORAGE # endif # define HB_IS_INET_NTOA_MT_SAFE ... Please, see the use of NTDDI_VERSION.
this platform. I'd guess ipv6 isn't supported by WinCE by I may be wrong.
I think that yes .- http://msdn.microsoft.com/en-us/library/aa450087.aspx
__MINGW32__ and __MINGW64__ they are both compiler 's built-in macros. Is defined in mingwce?IMO this is not relevant, there is no reason to be compiler specific here. This is general HB_OS_WIN issue. If you want to guard against WinCE, us HB_OS_WIN_CE Harbour macro.
Sorry, I meant that if defined __MINGW64__ also is defined __MINGW32__ I don't know in wingwce. [ Viktor Please could you send plain text posts, are much easier to read. ] Best regards, -- Xavi El 28/02/2010 16:01, Viktor Szakáts escribió:
Hi, On Sun, Feb 28, 2010 at 3:00 PM, Xavi <jara...@gmail.com <mailto:jara...@gmail.com>> wrote: Hi Viktor and all, Well. Some questions. If this is do it an implementation for MinGW. I can't see any reason why this have to be compiler specific, please elaborate. MinGW need to define _WIN32_WINNT before using the headers. http://oldwiki.mingw.org/index.php/header-w32api_h Should I force the code _WIN32_WINNT or use WINVER? Is this true for mingwce? Or rather WinCE in general. You have to check Windows API documentation if the features you need are available or not in this platform. I'd guess ipv6 isn't supported by WinCE by I may be wrong. Can I protect the code as standard headers? ... #if _WIN32_WINNT >= 0x0501 IMO, no. (as described in prev answer) __MINGW32__ and __MINGW64__ they are both compiler 's built-in macros. Is defined in mingwce? IMO this is not relevant, there is no reason to be compiler specific here. This is general HB_OS_WIN issue. If you want to guard against WinCE, us HB_OS_WIN_CE Harbour macro. Brgds, Viktor
_______________________________________________ Harbour mailing list (attachment size limit: 40KB) Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour
