Header files for the Windows packages

Hi, I am using PHP on Windows (IIS), and currently creating a PHP extension via SWIG <http://www.swig.org/>. In order to do that, i need the header files that were used when my PHP package got produced. I've looked all over the PHP site but i can only find binary or source downloads, not header / library packages. On Linux, it's easy: there is a package called "php-dev" or "php-devel" which contains those header files; for example on <http://rpmfind.net//linux/RPM/fedora/updates/13/x86_64/php-devel-5.3.3-1.fc13.x86_64.html> (scroll to the bottom to see the file list). But for Windows, i can't find any such package. There is actually a library file being distributed, under dev/php5.lib. However i can't find any header (.h) file that i could use in order to link with that library! Therefore, my only solution has been to download the source code and run a full compilation using the config flags visible in a phpinfo. There are some generated header files (like acconfig.h) so i can't just download the code and grab all the .h files - i have to fully compile it. At that point, of course, i also get another php5.lib library and new binary files, which render the official binary distro that i downloaded from <http://windows.php.net/> useless. When i'm done compiling, i run the following command to keep only header files: find . -not -name '*.h' -delete And there we go, i have my own php-devel package for Windows! This is fine for me, but i can't ask the people who are going to compile my program to fully compile PHP just to get these files. I could distribute them, but what if my files differ from the binary distro that they are using? At that point, i would also have to distribute my own binary files, which is getting way too obnoxious and hard to maintain. So here is my request: when generating a Windows distro, could you pack all header files using a command similar to the one above and make them available, either as a separate link, or directly under the "dev" directory? That dir already contains a library so it would make sense to put the headers that have to be used to compile against that library in the same place. Thanks, Zouzou