Sapero's Windows include files

[sapero]

Thanks for reporting. I never got this error until I read your reply and installed fresh copy of Aurora and the headers into virtual machine. I'll check my binaries.

Links updated.

[KrYpT]

thank you, its working now 

[Ficko]

Hi Sapero!

This may be very stupid but I have a notion I am missing some direction here.

I see this monumental work from you but I do not really find any comprehensive description to it.
How you supposed to use this efficiently and how this actually works and how this effect the “regular “ ebasic includes what exactly got installed etc.

May this belongs to “everybody knows” section but I certainly have the feeling to miss something.

These are my guesses but I would be happy to get some advice from the Master themselves.
1. You have to include “WINDOWSSDK.inc” which somehow translate the MS header files or/and loads some common headers like”WINDOWS.inc”
but if you need any other header you have to include it in your source as well after “WINDOWSSDK.inc”

2. “Windows.inc” alone will not work correctly after the Header installation.

I do not now that I am correct but these are my guesses.

I do have lots of questions like:

When you should include “WINDOWSSDK.inc” exactly?
Sometimes it seems to work correctly sometimes I am getting “duplicate declaration” like by “GetLogicalDrives()”.
What is the exact rule?

How can you speed up the compilation for smaller files?
-Apparently “WINDOWSSDK.inc” loads a lot of stuff which you may not always need.-
How can you tailor made it for your needs?

Appreciate your work,
Ficko

[Paul Turley]

Ficko,
Sapero's includes are the equivalent of the current Windows SDK.  Instructions then would be from whatever windows API function you are trying to use, if you search MSDN for a particular API call you will see a block at the bottom that tells what include file the API call is declared in.

For example here is the MSDN listing for the winsock 'accept' function:

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

At the bottom you have the requirements:
Minimum supported client   Windows 2000 Professional
Minimum supported server   Windows 2000 Server
Header   Winsock2.h
Library   Ws2_32.lib
DLL   Ws2_32.dll

Which tells you the DLL the function is in, and the include file which would be Winsock2.h, or Winsock2.inc in the case of Emergerce/aurora.

If you read the documentation that comes with the Windows SDK you will learn that you need to create a couple of definitions when including windowssdk.inc (windows.h).  For 95% of the programs you'll write using the API directlry (for Emergence) the top of your source file would look like this:

Code:

$ifndef WIN32
$define WIN32
$endif

$ifdef WIN32
$define WIN32_LEAN_AND_MEAN
$endif
 
$include "windowssdk.inc"

For Aurora it would look almost identical substituting # for $

WIN32_LEAN_AND_MEAN excludes rarely used headers from the base includes, so rarely used that I don't think I have ever run across a program that has used them.  The purpose is to speed up compile time.

$define WIN32 is because you are compiling for a 32 bit windows program.  The headers also contain definitions for other platforms, such as the Mac.

After the $include "windowssdk.inc" you would add other include files that contain the API definitions you are interested in, such as the aforementioned Winsock2.inc

Hope that clears some stuff up for you.

Paul.

 

[Ficko]

Thanks Paul that really helps!

[sapero]

Updated again. The sdkincludes library is refreshed, I've removed all unused modules with floats, strings and duplicate guids. Fixed also some bugs in various headers that gave errors while compiling test programs. At least shlwapi.inc is new, from server 2008 sdk.
There is a new QISearch function. It was present in shlwapi.dll (win2000) but exported by ordinal only. Now this function is accesible even on win95, and makes a bit easier to write COM classes:

Code:

#include "shlwapi.inc"
#include "shobjidl.inc"

#asm
extern _IID_IQueryContinue

qitabQueryContinue:
dd _IID_IQueryContinue, 0
dd 0,0
#endasm

declare qitabQueryContinue(); // struct QITAB[2]

class CQueryContinue
{
declare virtual QueryInterface(REFIID *riid, void *ppvObject),HRESULT {
return QISearch(this, &qitabQueryContinue, riid, ppvObject);
}

Aurora http://www.sendspace.com/file/wli16d
Ebasic http://www.sendspace.com/file/au1cby

[Barney]

As usual, an excellent addition. Thanks for sharing, Sapero.

Barney

[sapero]

The POINTTOPOINTS bug has been removed, and if you have noticed an additional asterix from shlwapi too.
Links updated.

[sapero]

With the vew version 2.0.4.5 you can create ribbon user interface. It is a bit complicated, but looks promissing.
I have added two custom macros - ListView_GetItemData and ListView_SetItemData, extended the shlwapi library with IUnknown_AtomicRelease and IUnknown_Set.

IUnknown_Set is usefull if you need to copy an object (class or interface) into second variable and add a reference to it.
AtomicRelease is safer than directly calling Release method, it checks if the pointer is NULL, optionally releases the object and sets the pointer to NULL.

Code:

IUnknown *unk = get_me_unknown();
// if (unk) unk->Release();
// unk = 0;
IUnknown_AtomicRelease(&unk);

Aurora http://www.sendspace.com/file/m8bou3
Ebasic http://www.sendspace.com/file/42h57b

[sapero]

Just a small note.
In the latest installer is a new propvarutil header which references to propsys.lib import library. Propsys.dll is included with Vista, so this is why I have included propsys.lib file in the installer.
Propsys.dll for Windows XP is available in Windows Search 3.0.

In the next upload i'll update all the missing propsys macros/wrappers, and include base classes for the ribbon interface.

[sapero]

As promised, here is the updated pak which includes all the wrappers for "propsys inline functions" and macros for the ribbon.
ListView_*etItemData bug fixed.
The uiribbon include has additional set of base classes required in applications hosting the ribbon. For examples how to use them, please see here (first reply)
CUICommandHandlerImpl, CUIApplicationImpl, CUISimplePropertySetImpl and CUICollectionChangedEventImpl. Only IUnknown part is implemented, other methods return E_FAIL or E_NOTIMPL.

Added Windows Azure headers in /include/azure. Sorry for the .opts file, you can delete it.

Aurora
http://rapidshare.com/files/242935338/AuroraHeaders10june2009.zip
http://www.sendspace.com/file/ktqzw0

Ebasic
http://rapidshare.com/files/242933983/EBasicHeaders10june2009.zip
http://www.sendspace.com/file/x64p7u

[Paul Turley]

Sapero.

You probably don't here it enough.  Thank you!  Without your hard work there wouldn't be such a complete set of include files for both compilers.  I have been using them myself for the Emergence Audio Engine and I can't tell you how much time they have saved me with DX interfaces.

I can't afford alot right now, but will be sending something your way.

Paul.

[sapero]

Thanks Paul.
I have updated math, xact, fftw3 (and more) and added a small set with new headers. The _cabs function from math.inc was not properly defined, three complex number structures missing from fftw3. Added signed versions of LOWORD and HIWORD macros to the custom sdkincludes library - SLOWORD and SHIWORD. There is no direct declaration, but they are used as an alias (see GET_WHEEL_DELTA_WPARAM macro in winuser.inc).

Aurora
http://rapidshare.com/files/254509343/AuroraHeaders11july2009.zip
http://www.sendspace.com/file/kaam4h // reupload january 2010

Ebasic
http://rapidshare.com/files/254517437/EBasicHeaders11july2009.zip
http://www.sendspace.com/file/a7d7ui

Please notice a small change in fftw3 includes: the import libraries are moved to the root /libs directory. I think so will be easier for most users - just pick create import library, instead creating separate /libs/fftw directory.

Code:

$ifndef __FFTW3_NOLIB__
$use "libfftw3-3.lib"
$use "libfftw3f-3.lib"
$use "libfftw3l-3.lib"
$endif

[Barney]

Thank you for sharing your excellent work with us, Sapero. It makes life so much easier for everyone, or at least some of us.

Barney

[fasecero]

Hi. Some of the headers included in GdiPlus.inc are commented ( disabled: Metafile, MetaHeader, Pen and Graphics).
Can I uncomment this headers?