Re: [Harbour] Building Harbour on Windows.

2010-03-02 Thread Viktor Szakáts
Hi Xavi, >> I don't see any need for a make-level solution. All macros can >> be defined from source. Why is it better to define them on >> make level? > > Because if someone tries to compile Harbour with a version of SDK not > supported, he don't have compile-time error. > If in the example of

Re: [Harbour] Building Harbour on Windows.

2010-03-01 Thread Xavi
Hi Viktor, [ Sorry for my bad English :'( ] I don't see any need for a make-level solution. All macros can be defined from source. Why is it better to define them on make level? Because if someone tries to compile Harbour with a version of SDK not supported, he don't have compile-time error.

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Xavi
Viktor, I think it's not that hard, I may be wrong but to respond quickly. I can call dynamically to GetAdaptersAddresses and in a nice Win7 is OK. But you can compile in your Win7 with MSVC++ 6.0 (it not say that _WIN32_WINNT is 0x0500 for compiler Harbour) and have compile-time errors. I can

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Viktor Szakáts
>> NTDDI_VERSION = maximum OS version supported by SDK/Windows-headers >> _WIN32_WINNT = OS version we want to target > > Okay, but if you remember my thread starting post .- > " > IMHO the best solution is to define the version of Windows that supports the > C compiler before compilation. > For ex

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Xavi
Hi Viktor, _WIN32_WINNT is nice, but it has other purpose. NTDDI_VERSION = maximum OS version supported by SDK/Windows-headers _WIN32_WINNT = OS version we want to target Okay, but if you remember my thread starting post .- " IMHO the best solution is to define the version of Windows that sup

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Viktor Szakáts
On 2010 Feb 28, at 18:02, Xavi wrote: > Hi Viktor, > >> Yes, NTDDI_VERSION is the (best? only?) way to detect >> platform SDK version. > > The only problem is that MinGW does not use NTDDI_VERSION, it uses > _WIN32_WINNT. > At least in my versions of MinGW. :) Yes, unfortunately the problem w

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Xavi
Hi Viktor, Yes, NTDDI_VERSION is the (best? only?) way to detect platform SDK version. The only problem is that MinGW does not use NTDDI_VERSION, it uses _WIN32_WINNT. At least in my versions of MinGW. :) Best regards, -- Xavi El 28/02/2010 17:18, Viktor Szakáts escribió: In the beginning o

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Viktor Szakáts
> In the beginning of hbsocket.c you can see .- > ... > #elif defined( HB_OS_WIN ) > #  if defined( __WATCOMC__ ) > #     if ( NTDDI_VERSION >= 0x0600 ) > #        define HB_HAS_INET_PTON > #        define HB_HAS_INET_NTOP > #     endif > #     define HB_HAS_SOCKADDR_STORAGE > /* #     define H

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Xavi
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 >= 0x0600 ) #define HB_HAS_INET_PTON #define HB_HAS_

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Viktor Szakáts
Hi, On Sun, Feb 28, 2010 at 3:00 PM, Xavi 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. > > h

Re: [Harbour] Building Harbour on Windows.

2010-02-28 Thread Xavi
Hi Viktor and all, Well. Some questions. If this is do it an implementation for MinGW. 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? Can I protect the c

Re: [Harbour] Building Harbour on Windows.

2010-02-26 Thread Viktor Szakáts
Hi, If there is a way to dynamically find out the version of the structure returned by function in question, so that we can be sure that required fields are present, we may force 0x0600 version in source, just to get the structure definitions from official headers. Plus we also need to add support